Feature Integration Across Microsoft Office Server Products

SharePoint Server, Exchange Server, Lync Server, and Office Web Apps

Illustrations for cross-server features

This multi-tab Visio file (or multi-page PDF file) includes descriptions and
architecture illustrations for features that work across Microsoft Office
server products.

Send feedback or additional requests to [email protected]. The Microsoft

Office Division is investing in content for cross-server solutions. We welcome your
feedback and requests.

Tips for printing

The page size of each tab is 22 x 17 inches (about a quarter of the size of an ANSI
Engineering diagram). This page size can be printed on two Tabloid size sheets (17 x 11)
inches) or four Letter size sheets (11 x 8.5 inches). If you have a plotter, you can print
these posters in their full size. If you don't have plotter, use the following steps to print
on smaller paper. Office Web Apps Server
Print posters on smaller paper
1. Open the poster in Visio. Office Web Apps Server is an Office server product that provides browser-based file
viewing and editing services for Office files. Office Web Apps Server works with products
2. On the File menu, click Page Setup. and services that support WOPI, the Web app Open Platform Interface protocol. These
products, known as hosts, include SharePoint 2013, Lync Server 2013, and Exchange
3. On the Print Setup tab, in the Printer paper section, select the size of paper you Server 2013.
want to print on.
To learn more about Office Web Apps Server, download the Office Web Apps Server:
4. On the Print Setup tab, in the Print zoom section, click Fit to, and then enter 1 Office Web Apps deployment simplified poster.
sheet across by 1 sheet down.
http://aka.ms/OfficeWebAppsPoster
5. On the Page Size tab, click Size to fit drawing contents, and then click OK.

6. On the File menu, click Print.

Microsoft tags and QR codes

Use your Windows phone or download a QR
Code reader to get more information about
implementing these features.

© 2013 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
Server-to-Server Authentication
Servicing resource requests between servers
Configuration
Server-to-server authentication is a new feature of Exchange Server 2013, Lync Server 2013, and SharePoint Server To configure a server-to-server authentication trust, you must add a new trusted security
2013 that allows a server to request resources of another server on behalf of a user. This feature uses the industry token issuer that corresponds to each server that will send resource requests on behalf
standard Open Authorization (OAuth) 2.0 protocol. Server-to-server authentication enables many new scenarios such of users. Each type of server has a JavaScript Object Notation (JSON) metadata endpoint
as eDiscovery, high resolution user photos, and site mailboxes. containing configuration information and a public portion of the access token signing
certificate. Part of configuring a server-to-server authentication trust is specifying the
JSON metadata endpoint of the other server.
The following table lists the JSON metadata endpoint for each server.
Server products
 Exchange Server 2013 Server JSON metadata endpoint
 SharePoint Server 2013
 Lync Server 2013
https://<server name>/autodiscover/metadata/json/1

https://<server name>/metadata/json/1

Server-to-server trust relationships

In order for a server to service an incoming resource request, it must trust the server making the request. To https://<web app name>/_layouts/15/metadata/json/1
establish this trust, you must configure server-to-server trust relationships.
A server-to-server trust relationship is one way. When you configure a server that runs SharePoint 2013 to trust
an Exchange 2013 server, the server that runs SharePoint Server trusts resource requests from the Exchange
server but the Exchange server does not trust resource requests from the server that runs SharePoint Server. For Example — How server-to-server authentication works for
seamless integration, you should establish two-way trusts.
eDiscovery between SharePoint and Exchange
In this example, the Exchange 2013 server has been configured to trust the server that runs
SharePoint Server with a server-to-server trust. An eDiscovery center on the server that runs
SharePoint Server has been configured to include data in mailboxes on the Exchange server.
Requests for resources on another server take the form of access tokens that are sent to the
web server service on the destination server.

1 An eDiscovery administrator sends a query to the server

that runs SharePoint Server that includes resources on an
Server-to-server Exchange server.
trusts 2 The server that runs SharePoint Server generates an access
token, identifying the user and the requested resource.
3 The server that runs SharePoint Server sends the access
token to the Exchange server.
4 The Exchange server validates the access token and sends
the query results. 4
5 The server that runs SharePoint Server sends the Server-to-
eDiscovery query results to the eDiscovery administrator s server trust
3
computer.

1
2
Claim 1
Claim 1
Claim 1
Claim n
Signature

5 Access

© 2013 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 High-Resolution User Photos
Larger profile picture used across all Office applications
Exchange Exchange
Client Access Server Mailbox Server

High-resolution user photos enables photos up to 648x648 Http: 443 Hi- res
pixels to be stored in Exchange 2013 that can be accessed by client Internal Exchange User Photo

applications, including Outlook, Outlook Web App, SharePoint 2013, communication

Lync 2013, and mobile email clients. A low-resolution photo is also User updates photo Outlook client Exchange 2013 pushes
the photo to Active
stored in Active Directory. in either Outlook, or OWA Directory
SharePoint, or Lync. (LDAP:389)
Once updated, the
updated photo is
Server products used across all Office
applications.
 Exchange Server 2013
 SharePoint Server 2013
 Lync Server 2013
Https:443 using external
Http or https URLs set in Exchange
Configuration SharePoint caches the
user photo in the MySite
Configure server-to-server authentication database (Https:443)
My Site
 Between Exchange 2013 and SharePoint 2013. SharePoint
Server
 Between Exchange 2013 and Lync 2013.

On Exchange Server 2013

 Start and configure the Exchange 2013 Autodiscover service.
 Set external URLs for SharePoint. These are the URLs Lync 2013 client maintains a hanging GetConnection
SharePoint will use when accessing photos in Exchange. with the Exchange server to get photo updates.
(HTTPS Get request = 443) The photo is synced from AD DS
to the Lync Address Book Service
On SharePoint Server 2013 (ABS) so legacy clients can get
the same photo. (LDAP:389)
 Install the Exchange Web Services Managed API. Use GacUtil to
load the Microsoft.Exchange.WebServices.dll into the Global Lync
Assembly Cache (GAC).
 Use Windows PowerShell to configure photo sync with Exchange.

How it works Legacy Lync client Lync Server

 Users upload a photo using the My Account page in Outlook Web
App or using account settings in Outlook 2013.
 Exchange automatically resizes the image for use by Active
Directory (48 x 48 pixels) or by other Office applications, including
Users can upload pictures with pixel ranges from 48×48 to 648×648. For example configuration scripts, see Jens Trier Rasmussen s blog
OWA and the Outlook 2013 client (96 x 96 pixels).
The photos are resized: articles:
 64×64 is used for the AD thumbnail.  Using Exchange 2013 high-resolution photos from
 96×96 is used for Outlook Web Access, Outlook, Lync Web Access, SharePoint Server 2013
(http://aka.ms/Bhr4d2)
and Lync 2013.
 648×648 is used for Lync Web Access and Lync 2013.  Integrating Exchange 2013 and Lync Server 2013
(http://aka.ms/Pn08dw)

© 2013 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 Unified Contact Store
Exchange 2013 is the contact store for all Office applications
Exchange
Unified contact store (UCS) provides a consistent contact Client Access Server
experience across Microsoft Office products. Users store all
contact information in their Exchange 2013 mailbox. The same Exchange
contact information is available globally across Lync, 1 HTTPS/443 Mailbox Server
Exchange, Outlook and Outlook Web App.
Internal Exchange
communication
Server products: Outlook client
or OWA
 Exchange Server 2013
 Lync Server 2013 4

Configuration Lync Server

 Configure server-to-server authentication between Lync 2013
Exchange Server 2013 and Lync Server 2013. SIP/5061 HTTPS/443
2
 In Lync 2013, enable the unified contact store policy SIP/5061
3
(default is enabled).
6 HTTPS/443

For example configuration scripts, see Jens Trier Rasmussen s

blog article:
Integrating Exchange 2013 and Lync Server 2013 1 User logs into their Exchange 2013 mailbox.
(http://aka.ms/Oyg7fh)
2 User logs into Lync 2013.
3
The Lync client tells the Lync server that the user is enabled for
How it works:
Unified Contact Store.
 Lync contacts for a user are migrated to Exchange 2013 4 Lync Server uses the Lync Storage Service to migrate the user s
automatically when the user logs in with Lync 2013. contacts to Exchange 2013.
 Users can access and manage their Lync contacts from Lync
2013, Outlook 2013, or Outlook Web Access. 5 The user must sign out and sign in to Lync 2013 to pick up the
change (not shown).
A user's contacts are automatically migrated to the Exchange
2013 server when the user: 6 After the migration is finished, the Lync client uses Exchange Web
 Has been assigned a user services policy that has Services (EWS) to read and maintain the Lync contacts.
UcsAllowed set to True.
 Has been provisioned with an Exchange 2013 mailbox and
has signed into the mailbox at least once.
 Logs in to Lync by using a Lync 2013 rich client.

© 2013 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 Site mailboxes
A central filing cabinet for emails and documents http://aka.ms/SiteMailboxes

Site mailboxes improve collaboration and user

productivity by allowing access to both documents stored in
SharePoint and email messages stored in Exchange, using
Provisioning & Management
the same client interface. Site Mailboxes are provisioned and managed through
Users SharePoint 2013.
Server products
 Exchange Server 2013 1 2
 SharePoint Server 2013

Configuration
 Configure user profile synchronization in the
SharePoint farm
 Configure app management service application
Team Site Membership Team Site
in the SharePoint farm Site Mailbox App
SharePoint

Outlook SharePoint Team Site Members/Owners Lifecycle Policy

 Configure SSL for the default zone to support
server-to-server authentication
In order to provision a new Site Mailbox, you need to install
 Install EWS API on servers that run SharePoint
the Site Mailbox app on your team site, and access the app
2013
at least once.
 Establish OAuth trust and service permissions on
servers that run SharePoint 2013
The SharePoint site membership determines who has
Emails access to the Site Mailbox.
 Establish OAuth trust and service permissions on Documents
Exchange

Exchange servers Site mailbox retention follows the same lifecycle policy
 Create site mailbox provisioning policy Site Mailbox
configured for the SharePoint site with which it is
 Configure site mailbox name prefix (optional) associated.

How it works 3 4
A site mailbox is functionally comprised of SharePoint 2013
site membership (owners and members), shared storage
through an Exchange 2013 mailbox for email messages and a
SharePoint 2013 site for documents, and a management
interface that addresses provisioning and lifecycle needs.
Site Mailbox
1 Users can access SharePoint team site documents Provisioning Policy
through the site mailboxes in Outlook 2013 Pro Plus.
On the Exchange side you can define Site Mailbox
2 Users can also read emails in the Site Mailbox Inbox
Provisioning Policies. These policies govern the email
from the SharePoint team site.
characteristics sent to and received from the site mailbox,
3 Emails are stored on Exchange servers. the size of the site mailbox on the Exchange Server and let
you define a prefix for Site Mailbox email addresses.
4 Documents are stored on SharePoint servers.

5 The metadata of the content on the SharePoint site is 5 For on-premises Exchange deployments, you also need to
synchronized to Exchange using the Representation periodically search for and delete Site Mailboxes that have
State Transfer (REST) API over HTTPS. been marked for deletion through the SharePoint lifecycle
policy.

© 2013 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 Exchange Task Synchronization
Synchronizing tasks between SharePoint Server 2013, Project Server 2013 and
Exchange Server 2013 Exchange Server 2013

Exchange Task Synchronization allows users to synchronize

tasks in SharePoint Server 2013 and Project Server 2013 with
Exchange Server 2013. Users may view and manage their tasks in
Outlook 2013, or on their My Site.
Tasks
Server products SharePoint Server 2013

 Exchange Server 2013

 SharePoint Server 2013 Exchange Sync
Outlook 2013
Timer Job Work Management Service application
 Project Server 2013 (optional)
 Aggregates tasks from SharePoint lists and
Project task lists (Does not synchronize tasks
User Profile Service
Prerequisites application with Exchange Server).
 Performs synchronization when a user views
On Exchange 2013. Search Service Work Management Users opt-in their My Site.
application Service application
 Configure OAuth trust and service permission.  Maintains the list of opted-in users
User may view and
On SharePoint Server 2013. edit tasks in Outlook  Synchronizes the next batch of users
Search Index
 User Profile Service application.
Exchange Sync Timer Job
 Work Management Service application.
Project Server 2013  Determines the next batch of users.
 Search (this is required for tasks in SharePoint Server 2013). Other Sites Tasks
Configure with continuous crawls and incremental crawls.  Ensures all users are constantly
synchronized.
 Secure Sockets Layer (SSL) is required.
 Initiates call to Work Management Service
 Users have existing My Sites. My Site application to perform synchronization of
Tasks
 Project Service application (to aggregate Project Server tasks). tasks with Exchange Server for opted-in
users only.
 Exchange Web Services API on each web front end server (this is
a separate downloadable .exe file that must be installed).
Opt-in
Project Web
Access sites  Users must opt-in to synchronize their
with tasks
Exchange tasks with their My Site, or their
On Project Server 2013 Users may view tasks
on My Tasks on their SharePoint Server 2013 and Project Server
 Create Project Web Application sites. My Site 2013 tasks with Exchange Server 2013.

How it works
When the My Tasks view on the My Sites is opened or refreshed
 The Work Management Service application performs a synchronization between SharePoint Server and
Project Server
 Exchange Sync Timer Job calls the Work Management Service application to synchronize tasks with
Exchange Server 2013
 The My Tasks page on the My Sites is refreshed

When the Exchange Sync Timer Job runs

 The Work Management Service application performs a synchronization between SharePoint Server,
Project Server and Exchange Server

© 2013 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
Lync Presence in Office 2013, Outlook Web App
and SharePoint Server
Lync Server as the authoritative source of presence information
Exchange
Outlook Web Client Access
App Server
Lync presence information allows a consistent view of
presence information across Microsoft Office products HTTPS/443
1
between Lync, Outlook, and SharePoint. Outlook queries Internal Exchange
presence information directly from Lync installed locally on communication
the same computer as Outlook. When users view presence
Exchange
information in SharePoint Server, presence information is 2 Mailbox Server
queried by Lync on the local computer.
SIP/MTLS:5061
1 User logs into Outlook Web App.
Client products:
 Outlook 2013 2 Exchange CAS queries Lync Server for presence
 Lync 2013 information.
Server products:
 Exchange Server 2013 More information:
 Lync Server 2013 http://technet.microsoft.com/en-us/library/jj688055.aspx Lync Server
 SharePoint Server 2013

How it works:
As long as Lync 2013 is installed on the user's local computer,
Outlook and SharePoint Server automatically display presence Exchange
information of users. Client Access
Office 2013
For Outlook Web App users, Exchange CAS queries presence Server
on behalf of the user.
HTTPS/443
2A
Internal Exchange
communication

Exchange
Mailbox Server
1 User logs into Lync 2013. 3A

2A User logs into his or her Exchange 2013 mailbox

3A Outlook calls Lync installed on the same computer
SIP/TLS:5061
as Outlook to retrieve presence information. 1

Lync Lync Server

2B User connects to SharePoint MySite. 2013
3B Internet Explorer calls Lync installed on the same
computer as browser to retrieve presence 3B
information.

HTTP or HTTPS
2B

My Site SharePoint
Server

© 2013 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 Voicemail
Exchange UM is the voicemail system for Lync Server
Voicemail allows a caller to leave a voicemail to Lync users Exchange
using Exchange UM. Mailbox Server
(Unified Messaging)
Client products:
 Lync 2013
Internal Exchange
 PSTN device (PBX, cellular, POTS) communication

Server products:
 Exchange Server 2013
 Lync Server 2013 4
Exchange
How it works: Client Access
Server
When a call is not answered by the callee on any of the (Call Router) caller B
callee s active endpoints, Lync Server routes the call to
voicemail on Exchange UM (i.e. Exchange Mailbox Server)
Call initiated
1 Lync Server
1
caller A Lync 2013
5
2

Call routing PSTN

3 4 Call ringing 3 2

callee Lync 2013 Lync Server Mediation Server IP gateway

1 Caller A initiates call to callee. 1 Caller B dials callee s phone number.

2 Call is routed to callee s Lync home server. 2 PSTN call is routed from IP gateway to Mediation
3 Lync Server rings callee s active endpoints. Server.
4 When call is not answered, call is routed to
3 Mediation Server routes call to callee s Lync home
voicemail (Exchange UM). server.
4 Lync Server rings callee s active endpoints.
5 When call is not answered, call is routed to
voicemail (Exchange UM).

© 2013 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
Meeting Recordings
Publish your meeting recordings on your SharePoint team site
1
Meeting recordings are a core component of SharePoint Server 2013
unified communications. A good way to share
your meeting recordings is to use SharePoint asset 2
libraries on your team sites to store your meeting
recordings.
Team Site
3
Client products:
 Lync 2013 Team Member 1
1
Asset Library
app
Server products:
 Lync 2013 4 4a
 SharePoint 2013

Meetings asset Team Member 2 5

Pre-requisites: library
Lync 2013
 The meeting recording is a client-side feature Meetings asset
in Lync 2013 that is available out of the box. library
Central Administration IIS Server
SharePoint 2013
 You have the team site you want to store the 6 6 6
meeting recordings already up and running. web
2
application
general 3
What is recorded? settings
The following are recorded into an MP4 file during
the meeting: IIS settings Wiki Page Blog

all audio Recording and publishing a meeting using the Lync client
Preparing for publishing meeting recordings 1 Join a Lync meeting.
active speaker s video (if used)
1 On your SharePoint team site, add the Asset Library app. 2 Start recording the meeting using the Lync client.
panorama video (if used) 3 The meeting content is recorded into an MP4 file during the meeting.
Optional steps
If you are unable to upload meeting recordings due to size restrictions 4 After the meeting concludes, the MP4 recording appears in the recording folder on
all content that is presented
or connection timeouts, perform the additional steps 3 & 4. your computer (C:\Users\<username>\Videos\Lync Recordings).
instant messages* 2 In the SharePoint Central Administration, change the maximum upload 4a Optional: Customize the meeting recording using the Lync Recording Manager
size setting for the web application that contains your team site app which gets installed with Lync client.
collection. 5 Drag and drop the meeting recording into your SharePoint asset library.
* Only the instant messages within the meeting
are included. Any peer-to-peer messaging that 3 In the IIS Server settings, increase the IIS connection timeout for the 6 Optional : Once the recording is in your asset library, you can insert it in any
occurs between meeting participants is not part of web site that contains your team site collection. SharePoint page. For more information about this step, see the Office 365 blog entry:
the meeting and therefore is not captured. Create and Publish Training Videos with SharePoint and Lync Online
http://aka.ms/R61q35

Digital asset libraries Video thumbnails

Asset libraries that contain videos have certain capacity and Improve the look and feel of your asset library. See this article to learn about
performance implications. See this article for more information. creating thumbnails for your meeting recordings.

Plan digital asset libraries in SharePoint Server 2013 Capture or change a video thumbnail
http://aka.ms/O1vq5w http://aka.ms/Kupj85

© 2013 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].