of the
Last week at the Hitachi Solutions Customer Conference, I lead a session about Server-Side Synchronization. One attendee asked me about an issue he was seeing where mailboxes would not stay enabled.
The following process has helped improve stability in other environments I’ve worked in, and it might help you as well if you face a similar situation.
- Set all mailbox records to Outlook synchronization.
- Set a small number of mailboxes to server-side synchronization and test and enable them.
- Wait a day or two and make sure that the mailboxes you enabled are working correctly.
- Set a few more mailboxes to server-side synchronization, and test and enable them.
- Continue this process until all of the active user mailboxes are enabled and working.
Be sure that all disabled users are not set to server-side synchronization. if there are any users who don’t need to be on server-side synchronization (such as users who are only ever working from the same computer, users who don’t need to track or sync, etc), either set them to Outlook synchronization or disable synchronization.
By following this process you can remove complexity from your sync deployment and improve performance by limiting server-side synchronization to only the mailboxes that need to synchronize.
If on premises you could also address any under capacity in the Asynchronous processing service by scaling out the deployment to a dedicated Email Integration server role. I have found SSS to be very resource hungry for any CRM larger than 20 active mailboxes.
Dedicated server for SSS with that Email Integration role might be the way to go.
Also check the Sync Dashboard that ships with CRM 2016. Not all disabled mailboxes will be caused by capacity issues. There are many small record level issues that trip into Error state, then disabling the mailbox
See https://download.microsoft.com/download/7/1/D/71D44C6E-CB78-4573-BDFF-77A6E137BA5C/serversidesyncwithDynamicsCRM.pdf