I am currently trying to install our first Exchange 2013 mailbox in a child domain. This will coexist with Exchange 2010. I have run the prepare schema/AD and /preparealldomains in the root domain. I have checked the various ADSI attributes to check that the updates have completed and I can see no replication issues.

All of the existing Exchange 2010 servers have SP3 and update roll up 5 installed apart from 1 mailbox server that is just SP3.

I am trying to install Exchange 2013 on Server 2012 r2 with all available updates.

The problem i am having is every time i run the Exchange 2013 setup choosing the mailbox role to install the prerequisite analysis fails stating "Local domain needs to be prepared" and points to an article on how to run the setup /preparedomain that i have already done.

Can anyone offer any insight in to what setup is checking for, what might be causing this and how to get past it?

Thanks

1. I would recommend you force AD replication, and confirm no replication issue.
2. Make sure the account you are using during the setup have the proper permissions.
3. Deploy the latest updates on 2010 server, a lot of issues was fixed related to co-existence.
   

 I have run the prepare schema/AD and /preparealldomains in the root domain.

Hi,

Have you ran Setup.exe /PrepareSchema and Setup.exe /PrepareAD in the child domain that you are going to install Exchange 2013 in?

https://technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx

Best Regards.

You don"t need to prepare schema on a child domain (actually you can't), however you can try a preparedomain on the child domain and check you can see "Microsoft Exchange System Objects" in DSA (you'll need to check Advanced Features).

Hi all, I had already tried to force replication and not seen any problems, The accounts I am using have the correct permissions, as Bruce says you can't /prepareschema on a child domain this has to be done in the domain where the Schema Master is.

I have also already run the /preparedomain in the child Domain and it has made no difference. 

I have checked and confirmed the ADSI attributes in this Technet article

https://technet.microsoft.com/en-us/library/bb125224%28v=exchg.150%29.aspx

The exchange setup logs are not really giving me anything to work with. Each time i run the setup i see an error on in the event viewer of the server i run in on as follows :

View Entire Forest: 'True', Configuration Domain Controller: 'Domain Controller', Preferred Global Catalog: 'Domain Controller', Preferred Domain Controllers: '{ Domain Controller }'
Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'Server' couldn't be found on 'Domain Controller'

Not sure if this is points to anything? I can obviously find the server object in the referenced Domain Controller.

I am also seeing this in the application log each time i run the setup.

• Edited by _CRK_ 21 hours 56 minutes ago

Hi all, I had already tried to force replication and not seen any problems, The accounts I am using have the correct permissions, as Bruce says you can't /prepareschema on a child domain this has to be done in the domain where the Schema Master is.

I have also already run the /preparedomain in the child Domain and it has made no difference. 

I have checked and confirmed the ADSI attributes in this Technet article

https://technet.microsoft.com/en-us/library/bb125224%28v=exchg.150%29.aspx

The exchange setup logs are not really giving me anything to work with. Each time i run the setup i see an error on in the event viewer of the server i run in on as follows :

View Entire Forest: 'True', Configuration Domain Controller: 'Domain Controller', Preferred Global Catalog: 'Domain Controller', Preferred Domain Controllers: '{ Domain Controller }'
Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'Server' couldn't be found on 'Domain Controller'

Not sure if this is points to anything? I can obviously find the server object in the referenced Domain Controller.

I am also seeing this in the application log each time i run the setup.

• Edited by _CRK_ Wednesday, April 22, 2015 9:30 AM

Hi all, I had already tried to force replication and not seen any problems, The accounts I am using have the correct permissions, as Bruce says you can't /prepareschema on a child domain this has to be done in the domain where the Schema Master is.

I have also already run the /preparedomain in the child Domain and it has made no difference. 

I have checked and confirmed the ADSI attributes in this Technet article

https://technet.microsoft.com/en-us/library/bb125224%28v=exchg.150%29.aspx

The exchange setup logs are not really giving me anything to work with. Each time i run the setup i see an error on in the event viewer of the server i run in on as follows :

View Entire Forest: 'True', Configuration Domain Controller: 'Domain Controller', Preferred Global Catalog: 'Domain Controller', Preferred Domain Controllers: '{ Domain Controller }'
Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'Server' couldn't be found on 'Domain Controller'

Not sure if this is points to anything? I can obviously find the server object in the referenced Domain Controller.

I am also seeing this in the application log each time i run the setup.

• Edited by _CRK_ Wednesday, April 22, 2015 9:30 AM

• Edited by _CRK_ 18 hours 55 minutes ago

• Edited by _CRK_ Thursday, April 23, 2015 12:33 PM

I have the same setup and same problem!!!

Created a user at the root lever and added to domain, enterprise, and schema admin groups

Ran these commands on the schema master server at the root

setup /prepareschema /iacceptexchangeserverlicenseterms

Setup /PrepareAllDomains /IAcceptExchangeServerLicenseTerms

Still get b.s. errors about the schema not being up to date and user doesnt have permissions!!!!

Does anyone else have any idea on what might be going on here and how to resolve?

Thanks

Hi, Thanks i am not seeing any replication problems (doesn't mean there aren't any!). But i might try the same thing and move the schema master to the child domain and try again.

Thanks

• Marked as answer by _CRK_ 18 hours 42 minutes ago

• Marked as answer by _CRK_ Friday, July 31, 2015 12:46 PM