We have a Windows 2000 network running active directory in mixed mode with 1 remote location running Windows NT as a primary domain controller. We would like to convert the NT location to Window Server 2003. I've already put Windows NT on the new server at the remote location which is running NT and promoted it to a PDC. Can I convert the new server to Windows 2003 and save the existing account information (about 100 users and computers). What is the best way yo accomplish the above?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Windows NT to Windows 2000
- Thread starter evsrcs
- Start date
You have a few options. Obviously you can do an inplace upgrade which will keep everything in place.
Another option would be to set up the 2K3 box in a new domain and use ADMT to migrate all of your user accounts and machine accounts over. This tool preserves the SIDS so you will still have access to your files.
The first option is the easiest, but is also the most risky since a failed install can leave you dead. If you have a BDC in the same domain you could take it offline to preserve everything JUST IN CASE!
Another option would be to set up the 2K3 box in a new domain and use ADMT to migrate all of your user accounts and machine accounts over. This tool preserves the SIDS so you will still have access to your files.
The first option is the easiest, but is also the most risky since a failed install can leave you dead. If you have a BDC in the same domain you could take it offline to preserve everything JUST IN CASE!
- Thread starter
- #3
In the original question I neglected to say that the NT server at a remote loaction is in a separate domain called DELMONT and the eleven remaining remote locations which are all Windows 2000 servers are in a domain called BMCO. Could I install the server which is replacing the NT server in the BMCO domain and use ADMT to run against the NT server(DELMONT domain) and migrate user and machine accounts and preserve the SIDS. We would like to end up with all locations to be in one domain(BMCO)
Mark offers sage advice. Keep a BDC so that you can rollback. ADMT is a great tool for migration.
Really you need a practice network to test out the options.
First of all I would recommend planning. What do you want the resultant Forest / Domain to look like?
Here is further advice on migration strategies.
Really you need a practice network to test out the options.
First of all I would recommend planning. What do you want the resultant Forest / Domain to look like?
Here is further advice on migration strategies.
If I understand what you have done already your approach is good.
The new clean server that you installed in the NT domain is now the PDC. I recommend you have all the security patches and Service Packs installed also, and the file format has to be NTFS.
Next step is to take the demoted old PDC offline (to have a recovery fallback if the upgrade fails).
Step two is to upgrade the the (new) PDC to WIN 2003. You will need to disable any WINS or DHCP on this server for the upgrade to work.
By the way, you have to run the upgrade from within the existing NT configuration, it will not work from boot floppies or booting from a cd to do the upgrade.
During this step you get several choices to select to create a new domain or child domain and to create a new forest or domain tree. You need to plan ahead!
Once you get the PDC converted and you know it is working properly, you can start converting the BDC's. However, I would highly recommend that you wipe the old BDC's and build them as clean DC's instead, as this provides you a clean WIN2k DC which can eventually take over the new domain, retaining the records from the original PDC, which then allows you to eventually rebuild the PDC from scratch also later. Remember that an upgraded NT server is not identical to a clean WIn2k build, and eventually you want to have all clean build machines in the domain, if possible.
Strongly recommend you read up on the process, even though it is pretty straigh forward. Always back up your server before you do this!!!!
HTH,
David
The new clean server that you installed in the NT domain is now the PDC. I recommend you have all the security patches and Service Packs installed also, and the file format has to be NTFS.
Next step is to take the demoted old PDC offline (to have a recovery fallback if the upgrade fails).
Step two is to upgrade the the (new) PDC to WIN 2003. You will need to disable any WINS or DHCP on this server for the upgrade to work.
By the way, you have to run the upgrade from within the existing NT configuration, it will not work from boot floppies or booting from a cd to do the upgrade.
During this step you get several choices to select to create a new domain or child domain and to create a new forest or domain tree. You need to plan ahead!
Once you get the PDC converted and you know it is working properly, you can start converting the BDC's. However, I would highly recommend that you wipe the old BDC's and build them as clean DC's instead, as this provides you a clean WIN2k DC which can eventually take over the new domain, retaining the records from the original PDC, which then allows you to eventually rebuild the PDC from scratch also later. Remember that an upgraded NT server is not identical to a clean WIn2k build, and eventually you want to have all clean build machines in the domain, if possible.
Strongly recommend you read up on the process, even though it is pretty straigh forward. Always back up your server before you do this!!!!
HTH,
David
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
