Syncing of tasks, appointments, and contacts
As one of the key features of Server-Side Sync, the automatic syncing of tasks, appointments, and contacts can eliminate the need for using the CRM Outlook client for organizations that use it for only this purpose. When properly configured, any task/appointment/contact created in CRM will be synced to the user’s Exchange mailbox. Once synced with Exchange, those same items can then be edited directly in the Exchange side (Outlook), and changes will reflect back in CRM. It will not sync a Task, Appointment, or Contact created directly from Exchange, since the majority of them are personal and do not need to be in CRM.
With the CRM email router, in order to view error messages, one would need to go into the server, and open the event viewer. While the messages are usually descriptive and useful, there are often times you will run into error messages such as these:
While descriptive, if the email router is hosting multiple deployments, messages such as these do not give all the information required to troubleshoot the issue.
In addition, you may have one incorrectly set up deployment, or one mailbox setup for incoming incorrectly, which will cause the event viewer to be bombarded with error messages, thus making it much more difficult to properly read the event viewer for non-related issues. Imagine a scenario where you have the email router installed in the CRM server, and when looking for a specific error message related to a CRM issue from the previous night, you are not able to see it, because the email router is creating several entries per second in the event viewer.
With server-side sync, one great feature is how errors, warnings, and alerts are shown, which is directly on the user interface.
In other words, if there is a problem related to a specific mailbox, you can restrict the listing of errors or warnings pertaining to only that mailbox, instead of the entire server.
Connecting to a deployment
Many times, it can be a challenge to establish a connection to a deployment using the email router.
Problems related to this include but are not limited to:
- Incorrect password
- Disabled service account
- Incorrect privileges
- URL/DNS issues
- Service account is not in PrivReportingGroup
- AD vs. Claims authentication issues
- Discovery service issues
When using server-side sync, the connection to the deployment is automatically established, and none of the mentioned issues are of a concern to connecting to the deployment.