Exchange 2016 – Tried to create new default OAB but the object already exists

Reading Time: 2 minutes

To play arround with some NTLM/Kerberos authentication over NetScaler I needed to install a new Exchange 2016 server in my lab environment.

The  Exchange setup (CU5) was crashing with the following error message. All prerequisites like AD prep and UCMA installation have been done.

Why the OAB can not be created?

Some old exchange server information was orphaned in the Active Directory.


Important: The following steps can damage your running Exchange configuration. Never try to kill all the mentioned keys in a production environment!

1.) Open ADSI Edit and connect with the “Configuration” context.


2.) Delete the following tables.

  • “CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lab,DC=local”
  • “CN=Microsoft Exchange Autodiscover,CN=Services,CN=Configuration,DC=lab,DC=local”


3.) Clean up your Active Directory from previous Exchange installations.

  • Delete “Managed Service Accounts”
  • Delete “Microsoft Exchange Security Groups”


4.) Delete the created Exchange users accounts.

  • MsExchDiscoveryMailbox.xxxxx
  • Exchange Online-ApplicationAccount
  • FederatedEmail.xxxxx
  • Migration.xxxxx
  • SystemMailbox.xxxxx


5.) Now prepare your AD schema again and complete the Exchange installation successful.


Leave a Reply

Your email address will not be published. Required fields are marked *