If you have been working with an Office 365 deployment, then you are probably already accustomed to the headaches that accompany Active Directory synchronization. Sure, you have the Directory Synchronization (DirSync), Azure Active Directory Sync (AADSync) or Azure AD Connect but there are complications that can occur while synchronizing users and passwords with your on-premises Active Directory.
Your employees get locked out of their accounts and are unable to log in to their mailboxes, SharePoint online sites, or OneDrive files. If you have new employees, they will also not be able to use their account on the cloud.
When this happens, you lose time and money over something as silly as not having the proper login credentials. You waste a ton of time trying to troubleshoot the issue. Instead of being able to proactively seek out the source of these unsuccessful logins, you become forced to deal with the issue on a case by case basis. This means that employees must call the help desk and must be dealt with one by one as the problem arises. This clogs up your IT helpdesk and, in the aftermath of employees being unable to complete their work, user satisfaction drops.
This in turn can impact user adoption after a recent migration to Office 365.
When you have hundreds or thousands of employees a small interruption can turn into a nightmare for the help desk and then to the IT Admin who needs to find and troubleshoots the issue as fast as possible. The first step is in realizing that the issue lies with DirSync/AADSync, and then identifying and confirming this by looking at the event log for specific event ID’s or by using the DirSync Troubleshooter from the Office 365 console. But, again, this can take up a lot of time and does not always solve the improper credentials issue.
In most Office 365 enterprise deployments, using a third party monitoring application like GSX Monitor can be the solution. GSX Monitor is able to look regularly at the DirSync/AADSync status in order to verify that the last synchronization occurred in a reasonable timeframe (this is something that you can configure to best meet the needs of your business) and that it was a successful sync. If any issues arise with the sync, the admin is alerted immediately with the last synchronization time and status, including a detailed message of the issue.
Don’t focus on the issue, with GSX Monitor you can focus on the resolution.
Below the 3 steps to monitor DirSync wiith GSX Monitor
Step 1: check both the system level and the synchronization status of the server responsible for the directory synchronization
Step 2: Always ensure that the last sync was successful
GSX Monitor will always ensure that the last synchronization was successful and alert you with the details otherwise. On top of this alert you can make certain that the synchronization runs on its schedule by verifying the last synchronization date.
Step 3: Troubleshoot parformance issue
It is also possible to troubleshoot any performance issue thanks to the GSX Graphs and keep track of the evolution of the availability, server performance and SQL performance.
No more guessing and trying to troubleshoot the issue after it arises and after your employees become frustrated—know exactly where the issue is and how to fix it. You, the administrator, become as proactive as possible on the DirSync/AADSync issues and save a ton of valuable time.
The number of user complaints are limited, as admins might be able to solve that issue before end users actually experience any issues, or before new employees use their account.