NT4.0 to WS2003 upgrade questions
|
Original Message
|
Name: patricio2626
Date: February 4, 2008 at 12:24:43 Pacific
Subject: NT4.0 to WS2003 upgrade questionsOS: WS2003CPU/Ram: n/aModel/Manufacturer: n/a |
Comment: Hello all, I will be getting rid of our NT4.0 machine here and replacing it with a fresh WS2003 machine. I've read articles/posts about upgrading, but most either deal with upgrade on the same machine (easy to keep AD structure in that case), or installing NT on the new machine, then upgrading (not an option for me). Is there any other way to transfer domain info between the machines? Also, is there an easy way to export settings? Sorry for the noobish questions, I just can't find good answers that apply to my case. Thank you kindly! J'ai des fourmis dans mon epee! -Cyrano
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: wanderer
Date: February 4, 2008 at 13:40:57 Pacific
Subject: NT4.0 to WS2003 upgrade questions |
Reply: (edit)"Is there any other way to transfer domain info between the machines?" No. This is because in the NT world there are only domains whereas in the AD world there are Forests with domains being a subset. "easy to keep AD structure in that case" Thre is NO Ad structure in NT If you can export your users to file you may be able to do this to import them. http://www.microsoft.com/technet/pr... Imagine the power if you knew how to internet search
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: Curt R
Date: February 5, 2008 at 07:14:33 Pacific
Subject: NT4.0 to WS2003 upgrade questions |
Reply: (edit)Depending on the number of users and amount of data on the present NT server, you may find it best to just port the data over and create new user accounts within AD on the 2003 DC. In a small environment, this may be the best way to go. It's simple enough to install/setup the 2003 DC and then test porting the data over. If that goes good then it's just a matter of the time it takes to create user accounts within AD. On the plus side, this gives you your NT server as a 'fallback' should something go wrong when you deploy the AD infrastructure. Depending on the age of the present NT server, you could even look at installing 2003 server on it and making it a redundant DC in your domain once you've deployed it and are confident everything is working as it should be.
Report Offensive Follow Up For Removal
|
Use following form to reply to current message: