A problem while validating the state of active directory submission dating
The following error appeared in the Exchange Server 2016 log file (C:\Exchange Setup Logs\Exchange Setup.txt): “[REQUIRED] Setup encountered a problem while validating the state of Active Directory: Couldn’t find the Enterprise Organization container.” I found a solution… but I do not think Microsoft officially supports it. The forest preparation continued without problems but the active directory preparation failed. Delete the following CNs completely, including all content: CN=Microsoft Exchange, CN=Services, CN=Configuration, DC=Lab, DC=local CN=CN=Microsoft Exchange Autodiscover, CN=Services, CN=Configuration, DC=Lab, DC=local 5. The virtual machines related to the problems: * DC1 – Windows Server 2012 R2 – Domain Controller running all FSMO roles * EXH01 – Windows Server 2016 – A new server that will become an Exchange 2016 server. After this operation, you will not be able to install any Exchange 2007 servers.[11/12/2014 .0223]  [RECOMENDED] Setup will prepare the organization for Exchange 2013 by using ‘Setup /Prepare AD'.In my testing none of these actions helps to resolve the issue, and in some cases make things worse.However, re-running Exchange 2007 (SP3) setup as mentioned earlier to prepare Active Directory resolves the issue and allows Exchange Server 2013 setup to proceed as normal.
The Microsoft Exchange Security Groups container is also still visible in Active Directory Users & Computers, with the Exchange Trusted Subsystem group the only group left behind (all other groups normally seen here have been removed by the uninstall process). The simplest execution of Exchange Server 2013 setup is to prepare the schema.
The command line is: This fails with the error message.
If you search the internet for information on this error “Couldn't find the Enterprise Organization container” you will encounter some advice about manually deleting certain containers and objects from Active Directory.
I have reproduced this error condition in a test lab environment after encountering it at a customer site: Under these conditions setup of Exchange Server 2013 CU6 will fail.
The problem may also occur with pre-existing Exchange Server 2010 organizations, or with other builds of Exchange 2013, but I have not tested all of those scenarios.