I have read two solutions for changing the domain name on a Windows server 2000 system. One requires the use of an NT4 box that replicates the AD then gets promoted. The other solution (the one most preferred by MS) is to upgrade to 2K3 and use the Domain Name Change Tool.
Our company is running 2K, needs to change the domain name from company.net to company.com, has a license for 2K3, but is not prepared to spend money on the CALs to bring us to compliance for the new server system.
I am wondering if the following scenario is plausible:
1. Set up a 2K3 server as a BDC to the 2K Server (company.net), transfer the roles, etc.
2. Demote the 2K server to a member server.
3. Use the Domain Name Change tool for 2K3 to convert our AD from company.net to company.com
4. Promote 2K server to a DC, transfer roles, etc.
5. Take 2K3 server offline.
I think it should work, and I am in the process of setting up a test environment to see if, indeed it will.
I would like to know if there are any caveats that I should be concerned with, or if this is possible at all.
--Kopar
Our company is running 2K, needs to change the domain name from company.net to company.com, has a license for 2K3, but is not prepared to spend money on the CALs to bring us to compliance for the new server system.
I am wondering if the following scenario is plausible:
1. Set up a 2K3 server as a BDC to the 2K Server (company.net), transfer the roles, etc.
2. Demote the 2K server to a member server.
3. Use the Domain Name Change tool for 2K3 to convert our AD from company.net to company.com
4. Promote 2K server to a DC, transfer roles, etc.
5. Take 2K3 server offline.
I think it should work, and I am in the process of setting up a test environment to see if, indeed it will.
I would like to know if there are any caveats that I should be concerned with, or if this is possible at all.
--Kopar