Update 11/27/2018: Few more updates to the article.
This post explains the configuration steps needed to get rich document collaboration working between Exchange Server 2016, SharePoint Server 2016, and Office Online Server, in your On-Premises environment.
Please use this link if you’re looking for configuration steps for Exchange Server 2016 On-Premises and SharePoint Online
When used together, Exchange Server 2016, SharePoint Server 2016, and Office Online Server provide a rich set of document collaboration features. For example, rather than directly attaching a document to an e-mail message you may now send a link to the document stored in OneDrive for Business (ODB). Outlook and Outlook on the Web (new name for OWA) will still display the file as if it was directly attached to the message like a classic attachment would be, as well as allow people to work with the file like they would with a classic attachment. Additionally, many people will be able to read and edit the same file at the same time while it is stored in OneDrive for Business (ODB). You can see a short demo of how this collaboration can look like right here.
The solution requires you have the following set up On-Premises:
The basic setup for these rich document collaboration features involves configuring OneDrive for Business (ODB) in the SharePoint 2016 farm, establishing a server-to-server trust (also referred to as S2S or OAuth) between SharePoint Server 2016 and Exchange Server 2016. Once completed, users will have the ability to attach ODB-based documents to email messages. Installing and configuring Office Online Server will introduce the additional capability of device-independent side-by-side viewing as well as edit & reply functionality in Outlook on the Web.
Note that editing documents is a premium feature of OOS and requires appropriate licenses!
Install OOS and create a new OOS farm. Make sure the farm URL is accessible from Internet if you want users to be able to view and possibly edit documents via Outlook on the Web from outside of the corporate network: Example: For an OOS farm that is going to use same internal and external FQDN, with editing enabled:
For an OOS farm that is going to use different internal and external FQDNs, with editing enabled:
In order to leverage the OneDrive for Business-based attachments on-premises, users must have a OneDrive for Business site hosted by SharePoint Server 2016 on-premises.
Follow steps from here, if the MySite Host (which gives you OneDrive for Business) is not already configured.
Additionally, to enable integration of Office Online Server for document previewing and online editing, WOPI bindings must be created in the SharePoint farm.
The commands can be put together in a script to make life easy. A sample script for performing this configuration is provided as an attachment to this blog post. Usage:
.\Config-SPSOAuth.ps1 -ExchangeServer mail.contoso.com -MySiteHostUrl https://sp01.contoso.com/
The user’s mailbox must be hosted on an Exchange Server 2016 server on-premises to enable the document collaboration functionality. There are a few settings to configure on Exchange Server to enable the full experience.
If you have Exchange 2013 servers in your organization, do not configure an OOS endpoint at the organization level. Doing so will direct Exchange 2013 servers to use OOS, which is not supported.
Example 1: Creating new policy for My Site host access:
Finally, assign the policy to mailboxes:
Set-CASMailboxPolicy JohnR@contoso.com -OWAMailboxPolicy ODBPolicy
Example 2: In this example, only users connecting to the server ‘Exch’ need to be enabled for document collaboration:
This configuration is useful in scenarios where only specific servers are going to frontend the Outlook on the Web traffic
& $ExScripts\Configure-EnterprisePartnerApplication.ps1 -ApplicationType Sharepoint -AuthMetadataUrl https://sp01.contoso.com/_layouts/15/metadata/json/1
For On-Premises deployments, only internal recipients (mailboxes) that are present in same organization as that of sender can be granted permissions on the OneDrive for Business document. The sender is informed via separate email if the automatic permission process fails. This means you cannot send ODB attachments to users outside of your on-premises organization. OneDrive for Business must be provisioned and initialized (the user has logged in at least once) for both the sender and the recipient. Without both the sender and recipient being provisioned and initialized the side-by-side documents preview will not work for the recipient. I wanted to thank Neil Hodgkinson, Jon Frick, Brian Day and Jason Haak for their help in putting this together! Bhalchandra Atre
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.