<div>
I suggest you to use 3rd party tool. Like from Quest. <br />
<a href="http://www.quest.com/exchange-uc/" rel="ugc">http://www.quest.com/exchange-uc/</a>
</div>


I suggest you to use 3rd party tool. Like from Quest.
http://www.quest.com/exchange-uc/ [http://www.quest.com/exchange-uc/]

<div>
Thanks guys<br />
<br />
Can anyone please attach the doc of Quest Exchange migrator?
</div>


Thanks guys

Can anyone please attach the doc of Quest Exchange migrator?

<div>
<div class="content wysiwyg-content">
Hi Experts,<br />
<br />
Can anyone please provide me with some sort of documentation regarding integrating 2 or more companies into a single email systems?<br />
<br />
For example,<br />
<br />
Company A acquires Company B. Company A uses Exchange 2010 as email systems and the email domain is companyA.com. <br />
<br />
Company B uses Exchange 2003, and their email domain is CompanyB. com<br />
<br />
The management has decided all users will have one email address policy, however users should receive emails sent to their individual domains as part of a transition period, later on, they should receive email through a single email domain that could be the name of companyA.com, or a new email domain<br />
<br />
What tasks should be performing as part of the migration/integration/tran<wbr />sition?<br />
<br />
Perhaps you can attach a flow chart, visio high level presentation, blogs/links/docs?<br />
<br />
Trust relationship<br />
AD Zones<br />
DNS?<br />
OAB,GAL?<br />
MX records?<br />
Send/receive connectors?<br />
<br />
Any other ideas?
</div>
</div>


Hi Experts,

Can anyone please provide me with some sort of documentation regarding integrating 2 or more companies into a single email systems?

For example,

Company A acquires Company B. Company A uses Exchange 2010 as email systems and the email domain is companyA.com. 

Company B uses Exchange 2003, and their email domain is CompanyB. com

The management has decided all users will have one email address policy, however users should receive emails sent to their individual domains as part of a transition period, later on, they should receive email through a single email domain that could be the name of companyA.com, or a new email domain

What tasks should be performing as part of the migration/integration/transition?

Perhaps you can attach a flow chart, visio high level presentation, blogs/links/docs?

Trust relationship
AD Zones
DNS?
OAB,GAL?
MX records?
Send/receive connectors?

Any other ideas?

Exchange 2010 High level tasks required to merge 2 or more companies to use a single email system

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.