Help moving user profiles in new LAN (Win2k Clients from NT4 to Win2k3 domain)

[Johnny Noitargim]

Hi everyone,

I currently have 40 Win2k users logging in to a LAN (Windows NT4 domain). I
have completely redesigned the network and will soon introduce a brand new
Win2k3 domain with AD on a new server.

What I would like to do is minimise disruption when disjoining all users
from the old domain and joining them to the new domain. Is there any way I
can centrally backup their user profiles and 'feed' them into the new domain
profiles?

Once that is done I will implement either Win2k3 roaming profiles or folder
redirection (decision soon to be made! )

Any advise will be greatly appreciated,

Many thanks,

Johnny

 

[Herb Martin]

I currently have 40 Win2k users logging in to a LAN (Windows NT4 domain). I
have completely redesigned the network and will soon introduce a brand new
Win2k3 domain with AD on a new server.

Any advise will be greatly appreciated,

Don't use a new domain is generally the best advice;
this is the "BEST" way to minimize disruption.

Upgrade the current domain -- of course with only 40
users it is not impossible to move them.

What I would like to do is minimise disruption when disjoining all users
from the old domain and joining them to the new domain. Is there any way I
can centrally backup their user profiles and 'feed' them into the new domain
profiles?

Yes, profiles are (largely) just "files". If you arrange to
have the "files" located by the reference in each user's
AD account property sheet they will be picked up.

Once that is done I will implement either Win2k3 roaming profiles or folder
redirection (decision soon to be made! )

Actually, you should probably do it the other way around.

Implement roaming profiles pointing to the 'moved/restored'
profiles saved from the "old users on the old domain" before
you let the new users logon.

 

[Johnny Noitargim]

Thanks Herb,

although I tend to believe that upgrades are a lot 'dirtier' than
migrations, point is taken.

J

 

[Herb Martin]

Thanks Herb,

although I tend to believe that upgrades are a lot 'dirtier' than
migrations, point is taken.

These operating systems were DESIGNED for upgrades.

I had one system that had started life as a "DOS 3.3" and made
it through every version of Windows, 2.x, 3.0, 3.1, then NT 3.1,
3.5 (with a bunch of internal MS Betas -- I mean WEEKLY
builds), 3.51, 4.0 to SP6a (sp1, 2, 3, 5, then 6a).

I only retired it because the 486 -- it had had hw upgrades--
wouldn't support Win2000.

Upgrades are fine if you take care of your systems.

 

[Cary Shultz [A.D. MVP]]

Johnny,

In addition to what Herb is telling you, you might want to go the upgrade
route and then eventually replace the "old" hardware when the new hardware
arrives.

So, if you have the old WINNT 4.0 domain you would upgrade the WINNT 4.0 PDC
( please follow the correct procedures for this! ). So, now you have a
WIN2003 domain with a WINNT 4.0 BDC ( or a few, whatever the case might
be ). You could then add the new hardware when it comes as an additional
Domain Controller. So, now you have two DCs. That is a good thing. If you
needed / wanted to have a second DC ( always a good thing ) then you could
simply dcpromo the upgraded DC, make sure that it is correctly removed from
AD and then format and load a clean install of WIN2003. That way you have
a clean machine.

You would just need to make sure that you did everything correctly...sure
that you would!

HTH,

Cary