The student sites are now running on a Windows 2003 Server Active Directory. I learned a few things along the way:
- Don’t try to reuse an existing server name if it is staticly mapped in your WINS database. The Windows Server 2003 upgrade process will think there is a name collision and use some randomly generated name for the server, UNIVERSI-2345a8 for example.
- If you have messed around with the User Rights on your NT4 domain, you’d best find the defaults for Windows 2003 and reset them. Updates and other things just don’t install correctly until they are reset. (The Threats and Countermeasures Guide came in pretty handy here too.)
- Until the workstations DNS server and the default DNS domain name is changed, they keep working right along as if the domain is still NT4 based. Dynamic DNS doesn’t start working until then either.
I still need to move all the FSMO roles off the temporary DC, but that doesn’t need to happen any time soon. I may put any more changes off until winter break.