We do this all the time - and no issues. If you want to manually update the staging server , then make it "production" and update the other server, you can of course do that, but we do this in real time automatically, (patching the server and the SQL server) and have never encountered issues. the AADConnect Server may lose temporary contact with the SQL server but it regains it.
If not, restart the AADConnect service afterwards.
Best practices to patch an Active Ad Connect Server with its 2019 SQL server

Hello,
I have a setup of Active - Staging AD connect servers both AD connect servers running latest AD connect versions on windows server 2019 and they have there dedicated 2019 SQL server for database.
Now one pair (adconnect + SQL) is Active and other pair in staging mode working fine.
When it comes to monthly windows patches what is the best practices to patch AdConnect and SQL server.
Will be an issue with servers got patched automatically via WSUS and rebooted as per there schedule, But keeping in mind they are active servers will be an issue in terms of any data loss or possible DB corruption?
Can someone help me with MS best practices to patch Adconnect and SQL servers in such scenario.
-
Andy David - MVP 114.7K Reputation points MVP
2022-08-23T14:48:58.533+00:00 0 additional answers
Sort by: Most helpful
I have never seen any corruption issues and we have been doing this for years (updating automatically).
If the sync stops while syncing for any reason ( SQL server not avail, networking , server reboot, etc...)
AADConnect will start over at the next interval. In the event it doesnt, a service restart on the AADConnect server gets things going again. Its very resilient.