Deploy Exchange 2013 in multiple domain scenario
I currently have an AD forest abc.com under which there are 2 domains def.abc.com and ghi.abc.com. Exchange 2013 is deployed in domain ghi.abc.com. Now I want to add a third domain jkl.abc.com and use exchange 2013 for it. I want to use the same exchange which is currently deployed in ghi.abc.com by adding  new servers and use the same namespace etc. Do I need to do anything special for it or just add servers and start creating mailboxes.
April 3rd, 2015 2:39am

Hi Gaurav,

You need to prepare the domain to accept the exchange organization into it. (Note you can't have a seperate exchange org, it will be conencted to the existing org, but with different user scope)

Make sure to follow the full preparation steps as in for the first exchange deployment.

Prepare Active Directory domains

Free Windows Admin Tool Kit Click here and download it now
April 3rd, 2015 8:50am

Hi gaurav,

Thank you for your question.

I agree with Satyajit321.

In addition, if we install Exchange 2013 with same version as former Exchange, we couldnt update AD schema. Because we have update it when we install Exchange 2013 in ghi.abc.com domain.

If there are any issue when we install new Exchange 2013, welcome to our forum to ask for help, we will give a better solution for you as soon as possible.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

April 5th, 2015 10:43pm

Thanks Satyajit for the Reply. Can you please elaborate what you mean by " it will be connected to the existing org, but with different user scope"
Free Windows Admin Tool Kit Click here and download it now
April 6th, 2015 12:59am

Hi Gaurav,

I agree that "but with different user scope" sentence doesn't make much sense. What I was trying to describe is when you install the Exchange Server in the Child domain it will be similar to installing it in the root domain and the Exchange Organization remains same.

Even though you might be able to create mailboxes for the Child domain users in the parent domain mailbox servers.I feel its better to create mailboxes on the child domain itself if you have the option, just to minimize the complexity involved.

Changing Recipient Scope:

Recipient scope is the specified portion of Active Directory hierarchy that the Exchange Management Console (EMC) and the Exchange Management Shell uses for recipient management.

The EMC and Shell always start with the recipient scope at the domain-level of the computer that is running the management interface. Neither the user account that's being used nor the Exchange servers being managed has bearing on the default value of the recipient scope.

This example sets the scope of the current session to the entire forest and designates gc1.contoso.com as the preferred global catalog server.

Set-AdServerSettings -ViewEntireForest $true -PreferredGlobalCatalog gc1.contoso.com
or Set it on a cmdlet level:
Get-Mailbox -ignonreDefaultScope


Other References:

http://exchangeonline.in/how-to-change-scope-of-domain-in-powershell/

April 7th, 2015 11:18am

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

Other recent topics Other recent topics