This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
AADS Shows a health warning but when you hit refresh the errors go away but my users cant sign in to AADS joined Virtual machines as it complains the username or password is wrong due it clearly not syncing correctly. how can i resove ? for clarity I've tried the following:
Stop and start AD Sync Services
Force a full Initial policy Sync
Sync Connector upgraded to latest release
Forced another intial sync
Manually changed password in 365 to update password hash
rebuilt VM's and domain joined them again.
still problem persists and i really dont want to have to delete my AADS domain and start again as that is alot of leg work.
I should add this has and was working historically and no changes had been made to the environment.
thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 82%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMW%3C/text%3E%3C/svg%3E)
It sounds like AADS is out of sync despite successful sync indicators. Try restarting the AADS domain controllers, check Azure AD Connect sync status and event logs for errors, and ensure time sync (NTP) is correct across all systems. Also, verify account lockout policies and replication health.
Thanks Mary,
but the AADS services use Microsoft controlled Domain controllers which i have no access too. how do you go about achieving this as Microsoft don't allow me to log a ticket about such things they want me to post it here instead.
For reference Account policies are all good, account confirmed as not locked out. NTP is all good across the systems