Best way to perform a NT 4.0 to Win2k Domain Upgrade?

[Agamar]

I am about to embark on what could be a life threatening quest. I have decided it is time to upgrade our NT 4.0 clunky domain to a Win2k "pure" domain. I want to know what yall think about what I need to do to accomplish my goals.

Goal #1: Make sure I keep all my users / groups (at least users...I can remake groups)
Goal #2: Migrate domain printers over as painlessly as possible (HP JetDirect)
Goal #3: Do not perform server upgrade...I want to do new installs

My domain is set up as so:
Primary DC (also acts as print server)
Backup DC
Standalone Server that is part of the domain

I was thinking about wiping the Backup DC, installing Win2k, and then letting it suck all the users into it. Then write down the share name and printer name of all the printers on the PDC and wipe / reload it.

Anybody see anything I am forgetting?

 

[Agamar]

Bumping me up so yall can still see me

 

[stash]

Sounds good, but just be sure to write down the port names of all your printers!!! Print out the configuration page from your printers and you will see a combo of letters and numbers (NPI304B1C for ex). You will need to create these ports in Win2k to attach the queues to. Printing in 2k is a bit nicer: you dont have to install any HP software to create "jetdirect" ports, you can use standard tcp/ip ports. Also you can set up internet printing, meaning you can print to a URL, and also view the status of the printers and connect to queues using a browser.

Also make sure you keep your Win2k domain in mixed mode unless you are positive there are NO non-win2k boxes on your domain.

Finally, when you wipe your BDC (or whatever server you do first) and install win2k, I would recommend setting up your DNS and making it rock-solid before you run dcpromo. A bulletproof DNS is essential for making AD work well. dcpromo will set up DNS for you, but I find that I have to go back and fix things. Whichever way you do it, make sure that you right click on my computer, go to properties, click on network identification, then properties, then more and type in the DNS suffix for your domain (eg. server1.microsoft.com rather than server1. which will be the default). This will save you some headaches when you install AD.

good luck.

 

[Night201]

Sounds pretty good to me. Good luck.

 

[Saltin]

The first thing you are going to want to do is make sure you have more than one BDC. If you don't, Id make one. Allow time for full synchronization. Take that BDC off line, and put it in a safe place. Don't touch it.

You can only do what you want to do (migration of users and objects) by upgrading the PDC to 2000. No one likes to do upgrades, everyone likes clean installs. The fortunate thing is, you can kill the upgraded PDC after everything falls into place.

So, when you are ready to go, slip the 2000 disc into the PDC, and select the upgrade option. This covers it pretty well.

Now here comes the trick. When you are done with the upgrade, bring up a second DC (2k) and allow time for the AD to replicate fully (I'd wait a day or two, not necessary, but no rush either). After you are sure everything is up to speed, transfer all the FSMO roles and the GC role over to the fresh install 2k DC. Wait another day or two. Watch to make sure everything is ok. If you are happy, demote the upgraded NT>2k DC and blow it away. Re-build it as a new, fresh install 2k dc.

Enjoy the fact that all your boxes are fresh installs.

Oh, and you can blow away that NT4 BDC you put away now.

 

[Agamar]

Thanks for the replies! That 2nd BDC sounds like a good idea... I was thinking about doing that anyway, since our current BDC is pretty old (P-II 266).

 

[PeeluckyDuckee]

I was taught when upgrading from NT to 2K to always keep a BDC offline in case anything goes wrong. Its an interesting idea of after promoting the PDC to 2K DC that you would setup a 2nd DC, let things replicate, then blow away the original PDC/DC. I guess my question is what would be the signifcance of keeping the original PDC/DC versus blowing it away? Wouldn't it be a bit of a hassle (especially when there's a few client dependent services running on there)?

Also, from what I'm hearing, the migration process can take up to a week's time to fully complete? With all the days in between waiting for things to replicate and such?

 

[Saltin]

<< I guess my question is what would be the signifcance of keeping the original PDC/DC versus blowing it away? Wouldn't it be a bit of a hassle (especially when there's a few client dependent services running on there)? >>



My experience has taught me that a fresh install is the only way to go. In place upgrades are wraught with issues. You need only look at this board to see the problems people have with (as an example) 98 to XP upgrades. When you throw a Directory Service and Networking Services into the mix, the matter is only complicated.

It is a necessary evil (in place upgrade)when you want to migrate from NT4 to 2k, but you only need to live with it for a short while. It's always better to be as fresh as possible.

As for the amount of time the migration actually takes.. The NT4 DS to 2k AD migration only takes as long as it takes to upgrade the PDC to a 2k DC. After that, you would want to allow adequate time for that 2k DC to replicate to its fresh partner..... varies depending on the size of the directory. Always be liberal.