NT to Windows 2000 server

[troyz]

I currently have a small network with one NT4 server. I would like to move to a windows 2000 server. I have one domain on the NT4 server.

What is the best way to migrate to windows 2000 server?

Troy

 

[LiLithTecH]

I guess that would depend on how the NT Server is setup.

Win2k relies on DNS to a large extent , and AD is not for the faint of heart.
Can be summed up in one word.

Planning.

Maybe a better way to approach this is that you tell us what
you think needs to be done, and we can offer suggestions (just a thought).

 

[Rapidskies]

Ask yourself first do you need the domain information, or is it easy to recreate. If you have a small domain with just a few users, it might be worth it to just recreate users, etc. If you need the domain info, you can do an upgrade or a migration. The proper way to upgrade is to:

(there are many more steps but these are the major ones)
Sync up BDC with PDC, take BDC offline
Make sure all apps/ hardware is win2k compliant on your PDC.
Backup PDC
Upgrade PDC to win2k, if problems you can promote your BDC to PDC and restore


Migration involves using migration tools to get users, from PDC to win2k server, there are many steps involved in this that you would have to research. My advice is be sure you have a good backup before doing anything, and a recovery plan, usually things go fine, but I've had to go to tape several times for different problems. Take care.

 

[owensdj]

troyz, are you planning on getting a new server machine with Windows 2000 Server or planning on upgrading the operating system system on your existing NT 4.0 Server? Getting a new machine would obviously be the best way to go. You won't have to worry about Win2K compatibility on the old hardware, and you'll have a backup of the data on the old machine in case something goes wrong. You'll still want to make sure you have at least a few verified backups of your data before you start this migration to the new server.

You'll need to do an in-place upgrade of your NT 4.0 Server to Win2K Server. The CD that came with your new Win2K server should be able to do this. Then you can add your new Win2K Server into your Active Directory domain by running DCPROMO. Make sure your domain is synchronized. Transfer all of the FSMO roles from the old to the new server. Take a look at
Microsoft Knowledge Base Article - 255504 for info on how to do that. Make sure your new server is running the DNS service and that it has its own IP address as the DNS server. Use DCPROMO to demote the old server from being a domain controller. Remove the old server from the domain.

 

[troyz]

I would think it would be easy to recreate. The server is just used for authentication and sharing a database. I am looking at purchasing a new server. The old server (NT) has 2 NIC's for load balancing with IP forwarding. I am most worried about the whole active directory thing.

Since it will be a new server, I will be installing new hard drives so if I need to go back I can.

Troy

Originally posted by: Whade
Ask yourself first do you need the domain information, or is it easy to recreate. If you have a small domain with just a few users, it might be worth it to just recreate users, etc. If you need the domain info, you can do an upgrade or a migration. The proper way to upgrade is to:

(there are many more steps but these are the major ones)
Sync up BDC with PDC, take BDC offline
Make sure all apps/ hardware is win2k compliant on your PDC.
Backup PDC
Upgrade PDC to win2k, if problems you can promote your BDC to PDC and restore


Migration involves using migration tools to get users, from PDC to win2k server, there are many steps involved in this that you would have to research. My advice is be sure you have a good backup before doing anything, and a recovery plan, usually things go fine, but I've had to go to tape several times for different problems. Take care.

 

[owensdj]

troyz, keep in mind that if you recreate the domain, all of your users will have new profiles when they log in, even if the domain name and user names are all the same as before. If you preserve your existing domain you won't have to deal with that.

I wouldn't worry too much about Active Directory. You can do a lot with it if you have a vast organization, but you don't have to do much if you want a simple office network. You just add/delete users and computers pretty much like you always did before. You don't have to get into multiple domains or into creating organizational units unless you want to.