I have a small network of about 10 clients and a single Win2000 DC. I just bought a new server loaded with Win2003 to replace the existing Win2000 server. The existing server is just a simple fileserver in addition to being the DC, it doesn't do anything fancy.
My proposed order of operations is as follows:
1. Connect Win2003 server to the existing Win2000 domain
2. Promote the Win2003 server to a DC
2.5 Do anything necessary to make AD realize that it's now a Win2003 domain and that the Win2003 server should be the "master" of everything
3. Demote the Win2000 server to a member server
4. Copy all data from the Win2000 server to the Win2003 server
5. Recreate the shares on the new server and update the login scripts to change all user mapped drives to the matching shares on the new server.
6. Reboot all clients and verify that they can access the shares on the new server.
7. Remove the Win2000 server from the network
7. Reboot all clients again and verify that they can still login to the domain and access their data on the 2003 server.
First of all, I believe I have to do something with domainprep/forestprep to the 2000 domain before it will accept a 2003 DC.
Second, after I have added the 2003 server as a DC, will everything automatically recognize it as the schema master and all that stuff?
Please let me know your thoughts as to my plan of attack and anything I may have left out. I just want to make sure I'm not going to break anything when I remove the existing DC. My goal is to make this transition fairly transparent to the client PCs. They should still be able to login with their current domain accounts, and access shares on the new server.