You create the accepted domains in the current Exchange organization. Then, you make a corporate decision whether you will use "linked accounts" in the Exchange forest or if you will create new accounts for the b.com and c.com users. Not knowing the relevant size, it's difficult to make a recommendation (what I would do for 50 users is different than what I would do for 1,000 users).
Then assign email addresses to the new mailboxes. I think the concept of linked accounts is covered pretty well on TechNet. Search for that phrase and perhaps msExchMasterAccountSid. From: [email protected] [mailto:[email protected]] On Behalf Of Rami SIK Sent: Tuesday, September 9, 2014 2:09 PM To: [email protected] Subject: [Exchange] Exchange 2013 and merges Hi All, I have a working AD domain A.com with Exchange 2013 for company A. Company A wants to merge with company B, say B.com. The new domain name after the merge will be C.com. They want company A users keep receiving emails for both A.com and C.com, and company B users B.com and C.com. C.com will be an AD domain in its own forest, and they are planning to have one way trust from C.com to both A.com and B.com. After the merge, new user accounts will be mostly likely to be defined in C.com only. And of course, they want to keep the cost at the minimum so that they want to use already existing EX2013 server(s) in A.com. I am not sure how this can be accomplished so I wanted to check with the group to see if anybody had any similar experience and their findings. I'd appreciate even if you forward me some related article on such merges. Rami ________________________________ If this message is not meant for you, do not use it - please let us know, and then delete it. We try hard to keep our messages and attachments free of viruses and other malicious programs, but are not liable if our precautions don't prevent their spread.
