- Can I promote the new machine to be the PDC and leave the other(s) on NT 4.0?
- Money is tight for this client, but I really feel that the existing PDC needs to be replaced,
before a "big failure" occurs. I would prefer not to upgrade the BDC to Win2k at this time.
- The client's BDC is NT 4.0 and runs SQL Server for its management system.
- I want this to be a fairly simple process. Am I way off base here and missing something?
- There are approximately 30 clients that are a mix of Windows 98, Windows 2000 Pro and XP Pro.
Your consideration and advice will be appreciated. Thanks.
- Back up all of your data. Back it up again. Then back it up some more.
- Beg, borrow or steal (no, not literally on that last one) a workstation to use as a fail-back
mechanism. Install NT4 Server, configure it as a BDC, then take it offline until you're satisfied
that the Windows 2000 migration has been successful.
- Install your new machine as another NT4 BDC. When you're ready to perform the migration,
upgrade the new PC to be your NT4 PDC. (Since you have to upgrade the PDC first, this will allow
you to upgrade a "clean machine," theoretically making the process much smoother.)
- When the new machine has been installed as a Windows 2000 controller, you can transfer files and applications from the existing PDC (which is now a BDC) and upgrade any other Nt4 server machines at your leisure.
This was first published in March 2003