Site Mailboxes in SharePoint & Exchange 2013
In this multi-part post, I will be exploring and configuring a new and very promising feature that comes with the Wave15 release of the 2013 suite of collaboration products which are Site Mailboxes. Site Mailboxes bring together email and SharePoint document libraries / team sites to enhance collaboration of documents and communications in the enterprise. Traditionally, users in the enterprise collaborate via two mediums, documents and email. While both SharePoint and Exchange/Outlook are great products on their own, this approach requires the user to leverage multiple client connectivity methods such as the browser and/or Outlook/OWA, or even a combination of the two. Site Mailboxes attempt to change how users collaborate by bringing these two back end systems together in the same client interface, Outlook. For more information on how Site Mailboxes are used in the new Office, please see an excellent overview here.
In this post we’ll explore the requirements to bring this new feature to use for users and the requirements associated with both Exchange and SharePoint 2013. To start, lets take a look at the requirements on the SharePoint side of things. I will be following the official documentation on TechNet which can be found here. We will step through each one of the requirements in more detail as we progress through the series of posts.
SharePoint 2013 Requirements Overview:
- Must be a member of the SharePoint administrators group.
- Site Mailboxes require Exchange 2013.
- EWS API installed on SharePoint WFE should be version 15.0.516.25 or above. More information on how to confirm is located here.
- User Profile Synchronization must be configured in the SharePoint 2013 farm.
- App Management Service Application be configured in the SharePoint 2013 farm.
- SSL configured for the Default Zone in web applications that are setup in a server to server authentication scenario.
Site Mailboxes require Exchange 2013
This should be a very obvious prerequisite and does not require any more detail. Exchange 2013 is required for this integration to work.
Install EWS API on SharePoint 2013 WFE server(s)
The first step in configuring integration between SharePoint 2013 and Exchange 2013 is to install Exchange Web Services API on the SharePoint 2013 web front end server. To do this, navigate to the following url and download the EWSManagedAPI.msi.
Once downloaded, open a command prompt with elevated privileges and execute the following command after navigating to the directory where the EWSManagedAPI.msi file was saved. In my example, it is saved to C:\installs\
msiexec /i EwsManagedApi.msi addlocal=”ExchangeWebServicesApi_Feature,ExchangeWebServicesApi_Gac”
The installer will launch and present the below welcome screen, click “Next” to proceed.
Select the “I Accept the terms in the License Agreement” radio button and click next to continue.
Modify the installation folder if necessary and click “Next” to proceed.
Finally, click “Next” to confirm the installation and to begin the install process.
After the installation is complete (should be very quick), click “Close” to complete the installation process.
In Part 2. We will take a look at how to configure the User Profile Synchronization service in SharePoint 2013 to synchronize with Active Directory Domain Services as its source directory.