

I have seen some strange events in my lab as I test these kinds of things.Īs an admin, you need to take care and read carefully what is recommended by Microsoft as they know better and you shouldn’t have to go through the pain of trying to recover an environment. If you do go and introduce new domain controllers, you might end up with Exchange services stopping or not servicing requests or losing access to Exchange. If you head over to the documentation, you will notice that Active Directory 2019 servers are not supported because you need to be on rollup 12 and higher to support them. Let’s say you have an Exchange 2016 environment on RU11. In this case, the version is Exchange 2016 RU11 or Exchange 2010 SP3 RU23. Before we jump into what is and isn’t supported, it is recommended that you refer to Microsoft’s documentation of which Active Directory servers will work with your version. Sometimes, new Exchange is not betterĪs Microsoft releases new versions of its operating systems, it is very tempting for an IT admin to have the latest and greatest installed, but they don’t realize that Exchange (your version) will only work with what is supported. It can happen that the domain controller that is virtualized does not want to start because of resources or another problem, but at least you will have a physical server to handle the login requests as well as servicing Exchange or if the physical machine does not want to start, you have the virtual machine to handle requests and Exchange. If your environment is virtualized, it might be better to have one physical domain controller and the other one virtualized. I advise having two or more domain controllers. In smaller environments this can lead to issues when only one domain controller has been set up - when any maintenance happens, it basically makes Exchange unavailable during the maintenance. Active Directory and Exchange work very closely with each other and if the domain controller becomes unavailable, Exchange will stop working because of its dependencies. Active Directory plays a big role in how Microsoft Exchange functions.
