joining parent company domain

[EMERY_BILL]

have an windows 2000 server running exchange 2000. company has been
purchased by another company. the parent company has their own 2003
server with their own domain.
i have vpn setup between the two offices and now want to setup the
exchange 2000 server so that emails that come in to users here
addressed to parent company's domain will come in here.
i know how to change the storage location of the users mailbox in ad,
but i think im going to have to setup trusted domains etc.
dont know what to do so that i dont have to re-create all mailboxes ,
ad etc.
anyone have a clue ?

 

[Ace Fekay [MVP]]

In

have an windows 2000 server running exchange 2000. company has been
purchased by another company. the parent company has their own 2003
server with their own domain.
i have vpn setup between the two offices and now want to setup the
exchange 2000 server so that emails that come in to users here
addressed to parent company's domain will come in here.
i know how to change the storage location of the users mailbox in ad,
but i think im going to have to setup trusted domains etc.
dont know what to do so that i dont have to re-create all mailboxes ,
ad etc.
anyone have a clue ?

You mention that you know how to change users' mailbox storage locations.
Does this mean your intentions are to only try and move your users to the
parent?

If so, you can't simply do that in AD. Each AD is in their own forest,
therefore two totally separate entities, separate Schema, Exchange
organization, etc. So if the answer is the parent company wants to
consolidate (absorb, assimulate, etc) your company into their AD
infrastructure, then you will need to perform a complete migration. You will
need ADMT to migrate the users, groups and computer accounts from your
domain into their's, then you want to use Exmerge to migrate the mailboxes
to your migrate users' accounts. This is a straightforward, yet extensive
task, depending on the size of your company. If a small number of users,
such as under a 1000, you can migrate them, the above method. If there a
1000s of users, then you will want to look into using the ADC.I prefer a
straight migration no matter how many users.

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

 

[EMERY_BILL]

the plan is for the the 2000 server users to have their existing email
address ie
(e-mail address removed) and to have (e-mail address removed) coming 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 (e-mail address removed) 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 ?

 

[Ace Fekay [MVP]]

In

the plan is for the the 2000 server users to have their existing email
address ie
(e-mail address removed) and to have (e-mail address removed) coming 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 (e-mail address removed) 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, it
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 them
based on the alias) and use that to populate the mailboxes you just enabled.
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 the
newly created users to still be able to access their old domain. This is the
cleanest method.

The following are links to explain in more detail about migrations and ADMT.

Download details Active Directory Migration Tool v.2.0:
http://microsoft.com/downloads/deta...b1-5849-4707-9817-8c9773c25c6c&DisplayLang=en

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=326480

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 (can
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/835991/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 Exchange
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/822921/en-us


Ace

 

[EMERY_BILL]

In

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, it
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 createa
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 them
based on the alias) and use that to populate the mailboxes you just enabled.
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 the
newly created users to still be able to access their old domain. This is the
cleanest method.

The following are links to explain in more detail about migrations and ADMT.

Download details Active Directory Migration Tool v.2.0:http://microsoft.com/downloads/details.aspx?FamilyID=788975b1-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=326480

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 (can
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 2003http://support.microsoft.com/kb/835991/en-us

How to use the Exchange Migration Wizard to migrate mailboxes from an
Exchange organizationhttp://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 Serverhttp://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 requirementshttp://support.microsoft.com/kb/253286/en-us

XGEN: How to Configure a Two-Way Recipient Connection Agreement for Exchange
Server 5.5 Usershttp://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 usershttp://support.microsoft.com/kb/822921/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

 

[Ace Fekay [MVP]]

In

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

Here I thought you wanted to merge both companies. Sorry for
misunderstanding your intentions. I am glad you found a resolve.

Ace