replacing w2k server with w2k3: user profiles ?

  • Thread starter Thread starter Tim Moor
  • Start date Start date
T

Tim Moor

dear ad gurus,
i have to to replace the only w2k dc in a small domain with a new w2k3 dc.
server name, domain-name and ip will still be the same. now my (12) xp
clients all have local profiles. how can i save the clients profile settings
while changing the dc ?

thanx alot
tim
 
Hello tim,

The client profile is stored on the local pc. Think you mean the USERS configuration
in Active directory? For that i think the best is upgrade your schema to
2003, add the 2003 as a second DC to the domain, make it a DNS server, Global
catalog server and let them replicate. After that move the FSMO roles to
the 2003 server, copy all necessary data configure additional services like
DHCP and so on. Change the clients to use the 2003 server as DNS. If everything
works run dcpromo on the 2000 server, demote it to a member server and then
remove it from the domain.

Moving FSMO roles to another server:
http://support.microsoft.com/kb/324801

If you don't like this way, maybe move the server to different hardware helps
you:
http://support.microsoft.com/kb/249694/en-us

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
 
Tim Moor said:
dear ad gurus,
i have to to replace the only w2k dc in a small domain with a new w2k3 dc.
server name, domain-name and ip will still be the same. now my (12) xp
clients all have local profiles. how can i save the clients profile
settings while changing the dc ?
Click to expand...

If the profiles are local there is no problem with the server -- the
profiles
would be on the user workstations.

Yes still the easier way to do such things without screwing something up
is to UPGRADE the current OS, even if the means first migrating it to
new hardware, or upgrading it and then migrating to new hardware.

Upgrade are almost always safer and simpler than "replacing" something.

BTW, you should have two (or more) DCs anyway -- even with good
backups.

Why must the "name" and IP be the same? Perhaps this is the time to
remove those restrictions...

The normal way to "add" a Win2003 DC requires it to have a new name;
DCPromo while the old DC is (still) online.
 
Back
Top