Windows Forum

Ask something
Discussion Locked

Windows 2000 server upgrade

0 helpful
6 replies

by fel2k

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have an existing Netserver running Windows NT server 4.0. For upgrade purposes we baught another server running Windows 2000 Server, my question is , Is it possible to import or copy the existing user accounts and policy from my old server to thenew server running Windows 2000 server. I need your advice ASAP.

6 replies

by baddragon

If it is not a Domain controller, yes it is, Microsoft has some nifty utilities just for that, or you can go to www.netiq.com, they specialize in just that, netiq can also migrate exchange accounts, printers, whole groups, and domain controlers.GL

by timwalsh

Is your NT 4 server just a server in a workgroup or a domain controller?
Assuming your NT 4 server is your Primary Domain Controller (PDC), and your want your new server to perform the same function in a Win2K domain, you have 2 options.

First some Win2K domain basics:
1. Win2K requires Active Directory (AD) to become a Domain Controller (DC).
2. Win2K DCs CANNOT exist in a NT4 domain.
3. Win2K (and AD) MUST be installed on a NT4 PDC to migrate a NT4 domain (user accounts and securitypolicies).

Having said that, on to your options:
Option 1: If your NT4 server meets the requirements for Win2K, install Win2K on that computer first. The setup program will invoke AD setup if it recognizes that Win2K is being installed on a NT4 PDC. (NOTE: Win2K and AD need access to DNS to successfully install.) Once your NT4 domain has been migrated to a Win2K AD domain, you can install AD on your new Win2K server (which will make it a DC), make sure AD replicates correctly, tansfer all DC roles to the new server, and then demote your old server and take it out of operation.
(cont.)

by timwalsh

(Continued)
Option 2: If your old server does not meet the requirements for Win2K or you want to maintain it as a NT4 backup, uninstall Win2K on your new server and install NT4 as a Backup Domain Controller. Force synchronization from the PDC to the BDC. Promote the BDC (new server) to PDC. Reinstall Win2K on the new server (now the NT4 PDC) as in option 1. (To give yourself a fall-back alternative in case reinstallation of Win2K does not go well, take the old server (now a NT4 BDC) off line before intalling Win2K on the new server. Then you can always reinstall it on the domain and promote it to PDC if necessary.)

While neither option is "easy", they are the only 2 ways to go. Make sure you do your homework on AD before you jumpinto this.
Good Luck!

This discussion is closed to new replies.