Change domain names

  • Thread starter Thread starter Brian Poole
  • Start date Start date
B

Brian Poole

I am working with two companies that are merging and I want to get
some feedback on my plan to cahnge the domain names.

Currently, each company has a Windows 2000 domain (DomainA and
DomainB)running in mixed mode and each company is running Exchange
2000. In the end I wnat each company on a new domain (DomainC)and to
merge their exchange servers.

Strategy:
Build new server that administrates DomainC and install Exchange 2000
on that server. Create a trust between each of the first two domains
and DomainC. Then migrate of the users and their mailboxes to
DomainC. Remove the servers for DomainB and DomainC, then rebuild
them in DomainC.

Concerns:
Effect on the workstations that have already joined DomainA and
DomainB. Will the trust and migration ensure that I can log onto the
new domain from the workstations or will I have to join the new domain
on each machine?

How will the removal of DomainA and DomainB's exchange servers effect
the outlook configuration on the workstations. Will it automatically
forward them to their new home server or do I need to keep on server
from each domain to handle the move?

I would appreciate any comments and suggestions on this task. I have
two to three months to complete the migration.
 
I am working with two companies that are merging and I want to get
some feedback on my plan to cahnge the domain names.

Currently, each company has a Windows 2000 domain (DomainA and
DomainB)running in mixed mode and each company is running Exchange
2000. In the end I wnat each company on a new domain (DomainC)and to
merge their exchange servers.

Win2000 domain names cannot be changed. You can choose to receive
email for additional DNS domain names however.

Win2003 domain names can ONLY be changed once the Forest reaches
the "Win2003 Forest Functional Level", i.e., all domains reach Win2003
Server mode and the admin upgrades the domains which contain ONLY
Win2003 DCs.
 
I understand that I cannot change the existing domain name. That is
clear. However, after this merger I have to have a new domain name
and I am trying to develop a strategy to migrate two domains into one
new domain. Is my original logic sound, are my concerns vaild and
what other pitfalls should I be aware of. I know that some one out
there has had to deal with this issue during a merger or aquisition.
We will change to a new domain even if we have to rebuild every server
and touch every machine.
 
I will go back to the original -- your subject line was misleading.

--
Herb Martin
Brian Poole said:
I understand that I cannot change the existing domain name. That is
clear. However, after this merger I have to have a new domain name
and I am trying to develop a strategy to migrate two domains into one
new domain. Is my original logic sound, are my concerns vaild and
what other pitfalls should I be aware of. I know that some one out
there has had to deal with this issue during a merger or aquisition.
We will change to a new domain even if we have to rebuild every server
and touch every machine.




Win2000 domain names cannot be changed. You can choose to receive
email for additional DNS domain names however.

Win2003 domain names can ONLY be changed once the Forest reaches
the "Win2003 Forest Functional Level", i.e., all domains reach Win2003
Server mode and the admin upgrades the domains which contain ONLY
Win2003 DCs.
[/QUOTE]
 
Currently, each company has a Windows 2000 domain (DomainA and
DomainB)running in mixed mode and each company is running Exchange
2000. In the end I wnat each company on a new domain (DomainC)and to
merge their exchange servers.

Strategy:
Build new server that administrates DomainC and install Exchange 2000
on that server. Create a trust between each of the first two domains
and DomainC. Then migrate of the users and their mailboxes to
DomainC. Remove the servers for DomainB and DomainC, then rebuild
them in DomainC.

[I am not an expert on migrating Exchange users so take that into
consideration.]

The above is the basic idea -- plan to learn and use ADMT 2.0 (it can
migrate
more than it's predecessors.

Destination domain must be in Native mode.
Concerns:
Effect on the workstations that have already joined DomainA and
DomainB. Will the trust and migration ensure that I can log onto the
new domain from the workstations or will I have to join the new domain
on each machine?

It won't work automatically but you (using ADMT or another tool) can
migrate the machine accounts as well.
How will the removal of DomainA and DomainB's exchange servers effect
the outlook configuration on the workstations. Will it automatically
forward them to their new home server or do I need to keep on server
from each domain to handle the move?

Home server? Computers have little or nothing to do with this -- home
directories and redirected "my documents" come from the user's account
properties (on the domain), the user's profile, or the Group Policies.
I would appreciate any comments and suggestions on this task. I have
two to three months to complete the migration.

Suggest you make and restore a backup of at least one DC and Exchange
server -- on a disconnected network do a restore to new hardware, install
a new domain and try it.

Three months is plenty of time if you just figure our YOUR SPECIFIC
problems (others can point you in the right direction but a test and some
practice will teach you more and teach you faster about your environment.)

That method will also give you more specific questions to ask. People here
deal much better with, "I did X, Y happened, how do I fix that...."
 
Back
Top