we are still seeing this on some clients with version 2.3.6 run the diagnostic is troubleshoot and everything checks out. perhaps a issue with this version of the sync client?
Password Hash Synchronization heartbeat was skipped in last 120 minutes
Keep receiving the following error:
Password Hash Synchronization heartbeat was skipped in last 120 minutes
Password Hash Synchronization has not connected with Microsoft Entra ID in the last 120 minutes. As a result passwords will not be synchronized with Microsoft Entra ID. Please refer to: Troubleshoot Password Has Synchronization.
I have referred to the troubleshoot menu - the diagnostics all returned that everything was running fine. I have tried restarting the service, and tried unticking password sync in the Azure AD Connect wizard and then going back and ticking it again and that seems to have worked for a few hours, but we are now receiving the message again. Any ideas on how to fix this?
14 answers
Sort by: Most helpful
-
-
Noffie-Leer 0 Reputation points
2024-04-16T14:54:48.3866667+00:00 It seems we were able to resolve this by removing a preferred domain controller from that list which was a server that had been decommissioned during a domain upgrade process.
-
ArnoV 0 Reputation points
2024-04-18T15:20:23.05+00:00 We're encountering a similar issue in one of our environments. I've upgraded to version 2.3.8 in hopes that it will resolve the problem. Fingers crossed for a successful fix!
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more