This article is part of an Essential Guide, our editor-selected collection of our best articles, videos and other content on this topic. Explore more in this guide:
1. - SharePoint 2013 Administration : Read more in this section
- A SharePoint upgrade takes planning
- Evaluating SharePoint 2013 upgrade issues
- SharePoint 2013 sports feature changes and deletions
- Synchronize SharePoint 2013 lists with Outlook 2013
- Create Exchange 2013 site mailboxes with SharePoint
- How to configure Exchange 2013 mailboxes with SharePoint
- PowerShell cmdlets for SharePoint 2013 backup
Explore other sections in this guide:
There are several new features available in Exchange Server 2013, but one that's getting plenty of early interest is site mailboxes. A site mailbox combines the messaging features of a shared mailbox with the document storage capabilities available through SharePoint 2013. This tip lays out the steps necessary to configure a site mailbox in a lab environment.
Installing and configuring Exchange 2013 site mailboxes
If you want to use Exchange 2013 site mailboxes, the first thing you must do is ensure that you have a SharePoint 2013 environment that will serve as the document library and enabler.
Assuming you don't have SharePoint 2013 installed, let's get started by building a small SharePoint farm. In our lab environment, we'll perform the following tasks:
- Install SQL Server 2012 Standard Edition with Service Pack 1.
- Install SharePoint Server 2013 Enterprise Edition into a new farm.
- Set up the basic configuration for SharePoint 2013 (defaults).
- Create a new HTTPS Web application and site collection, then assign a trusted certificate to it.
- Set up the User Profile Synchronization service.
- Install the Exchange Web Services Managed application programming interface (API).
- Run scripts on both the SharePoint 2013 server and Exchange 2013 server to configure and enable site mailboxes.
- Create a new site mailbox.
This seems easy, doesn't it? It is, but there are plenty of steps required to actually get there. Let's start with prerequisites.
As with any Exchange installation, first make sure that it's in a working state. Specifically, make certain that you've configured and tested the Exchange Autodiscover service and that you're using a valid third-party certificate (or an internal certificate authority).
You'll also need a valid certificate for the SharePoint 2013 farm that will help host your site mailboxes. If you're using a Subject Alternative Name (SAN) certificate for Exchange 2013, consider adding your SharePoint 2013 HTTPS site name to the certificate.
In my own lab environment, I have Exchange 2013 up and running under the domain stevieg.org. I also have an SSL certificate with SANs mail.stevieg.org and autodiscover.stevieg.org for Exchange. "Sharepoint.stevieg.org" is ready for the SharePoint 2013 installation.
I'm using a new server named SG-SP01 running Windows Server 2012, with SQL Server 2012 Standard edition joined to the same domain as the Exchange infrastructure. Now that media is ready for SQL Server 2012 and SharePoint 2013, we're ready to proceed.
Installing SQL Server
In our lab, we must install SQL Server 2012 Standard Edition on the same server on which we'll install SharePoint. Specifically, make sure that the following features are selected for the SQL Server installation:
- Database Engine Services
- Client Tools Connectivity
Installing SharePoint 2013
Since this is a lab environment, let's go with the SharePoint 2013 installation basics. After fulfilling the prerequisites, run a complete installation.
Once the install has completed, run the SharePoint Products Configuration Wizard. During configuration, choose Create a New Server Farm, then specify which SharePoint user will access the database, along with the database server itself. Leave the remainder of the settings at their defaults and wait for SharePoint 2013 to configure the base settings.
Set up SharePoint 2013 base configuration
After the configuration wizard completes, begin the initial farm configuration by accessing the SharePoint Central Administration website, which launches automatically from the Configuration wizard. Click Start the Wizard (Figure 1).
Select Use existing managed account to leave the default managed account as is, then click Next to begin the farm configuration.
After the default farm is successfully configured, click to Skip over creating a new site collection for now.
Create a new HTTPS Web application and site collection
Our site mailbox base is built upon a HTTPS-enabled Web application and site collection, so navigate to Central Administration, then click Application Management. On the Application Management page, click Manage web applications (Figure 2).
Next, click New. This tells the wizard to create a new Web application.
On the Create New Application page, choose the following options:
- Create a new IIS Web Site.
- Port 443
- "Yes" for the radio option next to "Use Secure Sockets Layer (SSL)."
Now that we've created our Web application, we can see the Application Created page. Click Create Site Collection to begin creating our initial site collection.
You'll now see the Create Site Collection wizard. Choose a suitable name for your base site collection and grant permissions to a suitable account (Administrator) that can access the SharePoint 2013 site. Click OK.
We now have an available Intranet Information Services (IIS) website to apply our SSL certificate to. In our lab environment, we've added the SharePoint site name to our Exchange SAN certificate, so we'll import it into IIS via the IIS Manager console (Figure 3).
We must now assign the imported SSL certificate to our new SharePoint site. To do so, select it from the tree view on the left-hand side, then right-click on it and select Edit Bindings.
Choose the single HTTPS binding on port 443, then click Edit. Next, select the SAN/UCC certificate from the SSL certificate drop-down (Figure 4).
The base HTTPS site collection is now available to access in our lab environment at SharePoint.stevieg.org.
Set up the User Profile Synchronization Service
The final task within the SharePoint Central Administration is to configure User Profile Synchronization. This ensures that user properties are kept up to date within SharePoint 2013; these properties include email addresses and other important information that Exchange 2013 site mailboxes rely on.
To begin, activate the User Profile Synchronization Service. On the SharePoint 2013 Central Administration page, click Manage services on server (Figure 5).
On the Services on Server page, scroll down to User Profile Synchronization Service and click Start.
When prompted, enter credentials for the account that will run the User Profile Synchronization Service. Next, refresh the Services on the Server page to monitor that the service has in fact started successfully.
Figure 6. Click "Manage service applications" in the SharePoint 2013 Central Administration console.
Now, return to the SharePoint 2013 Central Administration homepage and begin configuring the service. To do so, navigate to Manage service applications, which is listed under Application Management (Figure 6).
Next, scroll down and select User Profile Service Application (Figure 7).
We now need to perform the following tasks from the User Profile Service Application:
- Configure a connection to the Active Directory forest.
- Initiate synchronization and automatically create a schedule for incremental updates.
Figure 8. Configure synchronization connections via the SharePoint 2013 Central Administration console.
To begin, navigate to the Manage Profile Service page and click Configure Synchronization Connections (Figure 8).
On the Synchronization Settings page, click Create New Connection. You will now see the Add New Synchronization Connection page. Enter the following details:
- Connection Name. A friendly name for this connection
- Type. Active Directory
- Forest Name. The fully qualified domain name of the root forest.
- Auto Discover Domain Controller. In a simple domain structure, it's fine to allow the domain controller to be auto-discovered.
- Authentication Provider Type. Windows authentication
- Account Name and Password. An account with Directory Sync Rights, as detailed on Microsoft TechNet. Within the lab environment, I've entered Administrator credentials, which -- although not suitable for a production environment -- will allow you to get up and running.
- Port. Leave at the default LDAP port of 389.
- Containers. Click Populate containers to retrieve domain and organizational unit information from Active Directory. Scroll down and click Select all to include the entire forest.
Save your connection. Return to the Manage Profile Service page and click Start Profile Synchronization to begin the initial directory sync.
Note: This also sets up a basic schedule for subsequent synchronization jobs (seen on the right-hand side).
Install the Exchange Web Services Managed API
Now that the SharePoint-specific components are configured, we just have to configure Exchange integration before we're ready to use site mailboxes.
The core technology used for communication between SharePoint and Exchange is Exchange Web Services, so we must download and install the Exchange Web Services Managed API on the SharePoint server. It is available via the Microsoft Download site.
Install the Managed API from an elevated command prompt using the following syntax:
msiexec /i EwsManagedApi.msi addlocal="ExchangeWebServicesApi_Feature,ExchangeWebServicesApi_Gac"
Run scripts on SharePoint and Exchange 2013 to configure and enable site mailboxes
The final task is to tie both Exchange 2013 and SharePoint 2013 together to enable site mailboxes. To start, we must configure SharePoint so that site mailboxes are first enabled within SharePoint itself. Then, we must provide SharePoint with information about our Exchange 2013 organization.
To facilitate this process, download the Set-SiteMailboxConfig.ps1 script from the "Configuring site mailboxes in Exchange 2013"TechNet article and execute it from the SharePoint 2013 Management Shell:
.\Set-SiteMailboxConfig.ps1 -ExchangeSiteMailboxDomain <Your Domain> -ExchangeAutoDiscoverDomain <Your AutoDiscover URL> -WebApplicationURL <Your HTTPS SharePoint Application>
Next, navigate to one of your Exchange 2013 servers and launch the Exchange Management Shell. Change to the Exchange Scripts directory using cd $exscripts and execute the following script:
.\Configure-EnterprisePartnerApplication.ps1 -ApplicationType Sharepoint -AuthMetadataUrl https://<Your HTTPS SharePoint Site>/_layouts/15/metadata/json/1
Creating and using a new site mailbox
Now that all the configuration steps are complete, we're ready to provision our first site mailbox.
To begin, we must create a subsite within the Site Collection. To do so, navigate to Site Contents in SharePoint 2013, then click New Subsite and enter the title as "Project1" (Figure 9).
Within the new SharePoint site, navigate to Add an app, which is located within the configuration drop-down (Figure 10).
Now, from the Your Apps page, choose Site Mailbox from the list.
You will now see the mailbox available on the SharePoint site's homepage. Select it to begin provisioning the site mailbox in Exchange 2013 (Figure 11).
After the mailbox has been provisioned, you can finally access the site mailbox (Figure 12).
If you're viewing mail via Outlook Web App (look back to Figure 12), you'll see that mail associated with the site mailbox is integrated within the SharePoint site itself and that documents are shown within SharePoint.
If you're on the desktop using Outlook 2013, the view is slightly different; Documents and Mail are combined within Outlook (Figure 13).
About the author
Steve Goodman is an Exchange MVP and works as a technical architect for one of the UK's leading Microsoft Gold partners, Phoenix IT Group. Goodman has worked in the IT industry for 14 years and has worked extensively with Microsoft Exchange since version 5.5.