Interested in the new Server Side Sync in 2013? Want to get it configured? Here’s how!
1. Generate an IIS self-signed certificate
Before we start configuring CRM 2013, we need to get HTTPS in place. To generate a certificate, open IIS, highlight the server name and double click Server Certificates:
Click on “Create Self-Signed Certificate” which is found in the menu on the right-hand side. Give it a name, leave the certificate store as Personal and click OK:
Your certificate will now be listed.
Now we can bind the Dynamics CRM web site to HTTPS, by highlighting the Dynamics CRM web site (under the Sites section) and then clicking on Bindings on the right-hand side.
The following window will open, from which you select HTTPS and then the SSL certificate that we have just created:
2. Exchange Account Impersonation
We now need to ensure that the CRM Service Account has impersonation rights on the Exchange side.
We use Powershell for this:
New-ManagementRoleAssignment -Name “” -Role:ApplicationImpersonation -User “”
For example: New-ManagementRoleAssignment -Name “CRM ExServiceAcc” -Role:ApplicationImpersonation -User crm13.service
Get-MailboxServer “” | Add-AdPermission -User “” -AccessRights ExtendedRight -ExtendedRights ms-Exch-EPI-May-Impersonate, ms-Exch-EPI-Impersonation
The second PowerShell command requires the Distinguished Name (DN) of the Microsoft Client Access Server (CAS).
To enable impersonation rights on a single Microsoft CAS server use the following command:
Get-ClientAccessServer -Identity “” | Add-AdPermission -User “” -ExtendedRights ms-Exch-EPI-Impersonation
3. Configure the CRM Exchange Profile
Now navigate to https://server/organization (replace as required), settings and Email Configuration:
Click on Email Server Profiles and New Exchange Profile:
Fill in the details as per the screenshot below.
NOTE: If you have users across different countries and exchange servers located on these sites you should create multiple profiles with the corresponding Exchange servers:
You should leave the Advanced settings as they are:
Now navigate to Mailboxes and choose Add Existing Mailbox. You should see all existing User accounts here; simply select the ones you wish to set up.
4. Configure the Mailboxes
Now that we’ve set up the Profile and some Mailboxes, we configure them to use the Server Side Sync.
Server Profile: UK Mailboxes (the profile we just created)
Incoming Email: Server-Side Synchronization or Email Router
Outgoing Email: Server-Side Synchronization or Email Router
Then Approve the Email and the click on Test & Enable Mailbox:
You will then get an Alert on the mailbox profile:
Click on Alerts and you will see the following messages:
5. CRM Global Email Settings
Navigate to Settings > Administration > Settings and click on the Email tab. There are a few settings here to consider:
Configure email processing:
Change this setting to server-side, otherwise CRM will look to use the Email Router instead.
Configure Default Synchronization Method:
This sets defaults for User accounts – ensure they are set to Server-side or Email Router (so you can use either if required):
Email processing for unapproved user and queues
You can configure this so that each new email address must be approved by the Administrator before it can be used.
Configure email correlation
By default both the tracking token and smart matching are enabled; select whichever options suit your needs.
6. Test the Synchronization
We are now ready to test the sync!!
In CRM, create an appointment and ensure that you are a required attendee and invite another user. Enter the other mandatory details and click on Save.
If all has gone to plan, you and your invitee will see the meeting request in Outlook!
That’s it!! You’re now fully configured and using server-side sync!!
A few thoughts …
Multiple Exchange Servers
If you have multiple Exchange Servers in your organization, create an Exchange Profile for each Server and link them to CRM:
In the above diagram there is a main office in Lisbon and all other 3 branch offices have CRM users, yet out of the 3 only 2 offices use their own Exchange server. In CRM you would define 3 Email Exchange Server Profiles:
– Default Exchange Profile configured with Lisbon Exchange server
– New-York CRM Profile configured with New-York Exchange Server
– London CRM Profile configured with a London Exchange server
The Default Exchange server profile is applied to all users mailboxes so you only have to apply manual Exchange profiles on users mailboxes in London and New-York. Toquio and Lisbon will both default to the default Exchange profile which points at Lisbon.
Many thanks to James OConnor for an excellently well laid out blog detailing this: