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(230.39999999999998, 81%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGH%3C/text%3E%3C/svg%3E)
Good morning, all!
I'm looking to migrate and upgrade a customer AAD Connect installation to Server 2019 and AAD Connect 2.x. This would be on a domain member server, not a domain controller.
Another consultant has recommended installing to a domain controller, saying that he has observed multiple service disconnects due to not being on a DC. I want to move away from installing various applications on my DCs, preferring a clean installation with various identity management solutions on a separate server.
Polling the hive mind for consensus on experience with AAD Connect - on the domain controller or separate server?
Thanks to all for looking!
Gregg
Separate. Have never installed on a DC and do not see any issues. Installing on a DC seems like a bad idea :...
The key, I think, is to treat the AADConnect server like a DC, not install it on one. :P
I second NOT on a DC. While it is supported to install on a DC, would definitely recommend against it whenever possible as it greatly reduces complexity if there's an issue that needs troubleshooting steps (i.e.: restarting the server OS) to resolve.