Home » Microsoft

Category: Microsoft

Microsoft Exchange 2016 Installation “Couldn’t find the Enterprise Organization container”

Today I continued installing Microsoft Exchange 2016 on Windows Server 2016 in my Home Lab. The forest preparation continued without problems but the active directory preparation failed.


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.
In the past the domain controller had a Microsoft Exchange 2013 server joined but that was removed. I guess that there are still registrations in the Active Directory schema.


The following error appeared in the Exchange Server 2016 log file (C:\ExchangeSetupLogs\ExchangeSetup.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. Keep in mind: if you are still running an Exchange Server infrastructure you will probably destroy it!


1. Start a RDP session with the domain controller.
2. Open the following tool “ADSI Edit”.
3. Connect to the “default-naming context”.
4. 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. Restart the Exchange Server.
6. Start the Exchange Server 2016 installation.
7. Follow the installation wizard.

After these steps, the problems were gone and the Exchange Server 2016 is running without problems.

Installation Microsoft Exhange 2016 on Windows Server 2016

Today I was installing Microsoft Exchange 2016 on a new Windows Server 2016 purely for lab and education purposes.
After starting the setup wizard and the Readiness Checks the following error appeared:
Error: The Windows component Server-Gui-Mgmt-Infra isn’t installed on this computer and needs to be installed before Exchange Setup can begin.

Installation Microsoft Exhange 2016 on Windows Server 2016 - Readiness Checks Fail

So I tried installing the required components with the following PowerShell command:
Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell -Restart

Apparently “Server-Gui-Mgmt-Infra” isn’t something you can install on Windows Server 2016…
Installation Microsoft Exhange 2016 on Windows Server 2016 - PowerShell Fault

So after some thinking I realized that the Exchange 2016 application was released much earlier than the Windows Server 2016 operating system…
After some searching I found the latest “Exchange 2016 CU6 release” on the Microsoft.com website.

It appears that every CU is released in the form of a new ISO which is also the installation media. After downloading and running the installation everything was fine.

Upgrade MDT 2012 Update 2 to MDT 8443

In my Home Lab environment virtual machines with a Microsoft Operating System are deployed with Microsoft MDT / WDS. To support the latest Windows operating systems (Windows 10 and Server 2016) an upgrade was required from MDT 2012 Update 2 to MDT 8443.

After a successful upgrade to MDT 8443 and a Deployment Share upgrade everything looked fine… but when I started deploying Windows Machines an error occurred.
The following error was displayed at the end of the Deployment Wizard (Invalid DeploymentType=””).

After some searching on the internet, I came across the following Microsoft TechNet post.

To resolve my problems, the following steps were required:
1. Create a backup from the following file (%DeploymentShare%\Scripts\DeployWiz_ProductKeyVista.vbs).
2. Open the following configuration file (%DeploymentShare%\Scripts\DeployWiz_ProductKeyVista.vbs).
3. In the configuration file locate line 52
4. Change the line from (if oProperties(“DeploymentType”) = “UPGRADE” then) to (if Property(“DeploymentType”) = “UPGRADE” then).
5. Save configuration file
6. Start a new deployment

After changing this file everything should be fine :).