EMERY_BILL
Tue Mar 04 12:55:30 PST 2008
On Mar 3, 11:46=A0pm, "Ace Fekay [MVP]" <PleaseAs...@SomeDomain.com>
wrote:
> Innews:58080807-e79b-41ac-a161-84e47272c333@s12g2000prg.googlegroups.com,
> EMERY_B...@HOTMAIL.COM <EMERY_B...@hotmail.com> typed:
>
> > the plan is for the the 2000 server users to have their existing email
> > address =A0ie
> > per...@child.net =A0 =A0and to have per...@parent.net =A0 =A0 =A0 =A0com=
ing into
> > the same mailbox. i know how to go into ad on the parent server and
> > change the storeage location to childs' store. and i know how to
> > config childs 2000 server to accept meil addressed to parent.com . and
> > i know how to add per...@parent.com as an allowable email address in
> > childs ad.
> > question is, if i setup childs domain as a trusted domain to parent ,
> > will the exchange server at parent see the one at childs so that i can
> > change storage location for relevant email ?
>
> A child domain is created when you take a member server from scratch and
> promote it into the existing forest while opting to make it a DC in a new
> child domain. If you are implying taking the other company's DC and trying=
> to make it a domain controller in a child domain in your infrastructure, i=
t
> will not work. That's not how AD works.
>
> Also, I understand you can config your Exchange 2000 server to accept mail=
> for their domain, but what about the users? I suggest to create an OU or a=
> child domain, whatever you prefer, and use ADMT, (which you need to create=
a
> trust to their domain anyway), and choosing to retain their SID Histories,=
> to migrate their users, passwords, groups, and computers into your domain.=
> Then mail-enable the new accounts. Then use the Exmerge to 2 step method
> pumping out the emails from their users' mailboxes into PSTs (it names the=
m
> based on the alias) and use that to populate the mailboxes you just enable=
d.
> This way the users have all their emails, desktop profiles, etc. You can
> co-exist as you plan to do it in batches, which the SID histories allow th=
e
> newly created users to still be able to access their old domain. This is t=
he
> cleanest method.
>
> The following are links to explain in more detail about migrations and ADM=
T.
>
> Download details Active Directory Migration Tool v.2.0:
http://microsoft.co=
m/downloads/details.aspx?FamilyID=3D788975b1-5849-47...
>
> 326480 - How to Use Active Directory Migration Tool Version 2 to Migrate
> from Windows 2000 to Windows Server 2003 (it doesn't matter if going from
> 2000 to 2003, NT4 to 2000, 2000 to 2000, or 2003 to 2003, the procedure is=
> the same:
http://support.microsoft.com/?id=3D326480
>
> How to configure the Active Directory Migration Tool to migrate user
> passwords from a Windows NT 4.0 domain to a Windows Server 2003 domain (ca=
n
> be used for your scenario):
http://support.microsoft.com/kb/832221/en-us
>
> How to use a SID mapping file with the ADMT tool to perform a resource
> domain migration to Windows Server 2003
http://support.microsoft.com/kb/835=
991/en-us
>
> How to use the Exchange Migration Wizard to migrate mailboxes from an
> Exchange organization
http://support.microsoft.com/kb/328871/en-us
>
> A comparison of the migration methods for migrating from Exchange Server 5=
.5
> to Exchange Server 2003 or to Exchange 2000 Server
http://support.microsoft=
.com/kb/327928/en-us
>
> You can also opt to use the ADC method, which was really created for Ex55 =
to
> Ex 2000/2003 migrations, but I am not fond of, but is viable with larger
> migrations such as yours. But honestly I have not tried the ADC for
> migrations between Exchange 2000/2003 and Exchange 2000/2003.
>
> ADC installation requirements
http://support.microsoft.com/kb/253286/en-us
>
> XGEN: How to Configure a Two-Way Recipient Connection Agreement for Exchan=
ge
> Server 5.5 Users
http://support.microsoft.com/kb/296260/en-us
>
> How to configure a two-way recipient Connection Agreement for Exchange
> Server 5.5 and Exchange Server 2003 users
http://support.microsoft.com/kb/8=
22921/en-us
>
> Ace
use the following url
http://www.ctunion.com/node/87
it explains what we want todo and how to do it. just have to make the
server in the company that was aquired a member server first rather
than a dc which is no problem.
thank you for your help