Installing Exchange 2013 into child domains only

Hi Guys,

I have the following senario, We have two clients who are part of the same parent. We have built a new forest:

Forestroot.com

With two child domains 

Child1.forestroot.com

Child2.forestroot.com

The Forestroot does not need exchange but both child roots do require exchange.

I have extended the Schema, preped the root AD and preped all other domains.

To install exchange I have logged onto the exchange box in the child domain as the forestroot admin:

When I install exchange in the first child domain I get errors to do with the the arbitration mailboxes not being created, the accounts in the root domain are not mailbox users. I figure this is due to no exchange being created in the forestroot. 

Exchange actually is installed and running. 

From the child exchange server when I log into ECP as the forestroot admin I get the following error:



I can add the child domain administrator to organisation management group in the root forest and then manage the exchange server but was wondering if there was away to manage these as the forestroot admin without installing the management tools in the forestroot domain?

Also should I worry about the system mailboxes that where not created, I don't believe they are critical to the functioning of exchange. 

In the forestroot domain I currently have the following mailboxes only:

  • Administrator
  • DiscoverySearchMailbox

July 16th, 2015 5:50am

The initial installation of Exchange requires certain objects to be created in the root domain.  The server itself can be in the child domain, but Exchange organization objects will go in the root domain, so you must have root domain rights.

The ECP logon might be caused by the account you're using having a mailbox in a downlevel version of Exchange.  Try a URL like:

https://Ex_2013_Server/ecp?ExchClientVer=15

Free Windows Admin Tool Kit Click here and download it now
July 16th, 2015 12:04pm

The install in both child domains was done using the root forest. Exchange objects where created in both the root and the child domains. 

The issues I have is after the exchange install. The following is what I find:

  1. I get errors about system mailboxes. But exchange actually starts. 
  2. EWS does not work, I have rebuilt it multiple times (Interestingly on the second exchange server EWS does work.)
  3. ECP login works for any child domain account but not using the root administrator account

July 16th, 2015 7:37pm

Hi,

For your question, it seems that arbitration mailbox not created when perpare AD. We can refer to below link to recreate it: http://social.technet.microsoft.com/wiki/contents/articles/5317.recreate-and-enable-missing-arbitration-user-accounts-and-mailboxes-in-exchange-server-2010.aspxFor other question, ensure all Exchange service and Exchange component works well.

We can run Get-ServerComponentstate -Identity servername to check. If the state is Inactive, please run below command to active relevant component: Set-ServerComponentState <Identity> -Component component name -Requester HealthAPI -State Active
More details about Server Component States in Exchange 2013, please refer to:
http://blogs.technet.com/b/exchange/archive/2013/09/26/server-component-states-in-exchange-2013.aspx

Besides, ensure you are using an account with the correct permissions: Schema Admins and Enterprise Admins.

Thanks

Free Windows Admin Tool Kit Click here and download it now
July 17th, 2015 4:53am

Just to clarify, did you run setup /PrepareAllDomains?
July 17th, 2015 6:56pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics