Scenario: Existing domain is child.domainA.corp. Exchange 2003 SP1 (will SP2 before move) and a few DC are all that is in the root & child domains, no member servers or workstations. Due to being bought by another company they are asking us to move to their domain, lets call is domainB.corp. DomainB.corp already has their existing Exchange 2003 setup & going. How would child.domainA.corp's Exchange deal with suddenly being part of domainB.corp and their Exchange organization? Is a domain rename an option for this scenario, or would my time be better spent on an Exchange Migration plan? I've seen quite a few articles on domain renames & the Exchange effects, but those were more "rename" oriented and not a "move"
From http://support.microsoft.com/?id=842116 ... "You cannot use the Exchange Domain Rename Fixup tool or the Windows Server 2003 domain rename tools to merge two Exchange organizations that are in different Active Directory forests into a single Exchange organization." Anyway, you're going to get it done an awful lot quicker with a simple migration... HTH, Tim wrote in message news:1147111924.802580.218720@g10g2000cwb.googlegroups.com... > Scenario: > > Existing domain is child.domainA.corp. Exchange 2003 SP1 (will SP2 > before move) and a few DC are all that is in the root & child domains, > no member servers or workstations. Due to being bought by another > company they are asking us to move to their domain, lets call is > domainB.corp. DomainB.corp already has their existing Exchange 2003 > setup & going. > > How would child.domainA.corp's Exchange deal with suddenly being part > of domainB.corp and their Exchange organization? Is a domain rename > an option for this scenario, or would my time be better spent on an > Exchange Migration plan? > > I've seen quite a few articles on domain renames & the Exchange > effects, but those were more "rename" oriented and not a "move" >
