Hi there, I asked this question in the 'Windows Server Forums > Migration' forum and it was suggested that I post here for ack mout options to undo what I've done.
Apologies for the length of this message but I wanted to get in as much useful detail and background info as possible.
I was trying today to transfer Windows 2003 domain control over to a Windows 2008 R2 member server. It didn't work and I now need to undo the changes.
I started off with the original Microsoft Windows Server 2003 SBS 32-bit SP1 Domain controller for the DOMAIN domain :
old-server 192.168.2.1
The new server is Windows Server 2008 R2 Foundation 64-bit SP1 and has been on the domain for over a year now.
new-server 192.168.2.8
I first upgraded 'old-server' through Windows Server 2003 SP2 on until all critical updates had been applied. I also applied any outstanding updates to 'new-server'.
The original 'old-server' domain controller is old and well out of warranty so I wanted to transfer the Domain Controller function from 'old-server' to the 'new-sever'. The intention would ultimately then be to retire 'old-server'.
I followed Microsoft's instructions on 'How to view and transfer FSMO roles in Windows Server 2003' (sorry I can't post links or images yet) and it all actually appeared to go okay. However, when I rebooted and logged in to 'new-server', I got the following warning (and continue to get it now every time I login to 'new-server' :
The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliant check cannot be completed, the server will automatically shut down in 9 days 22 hour(s) 30 minute(s).
Clicking on the <Help> buttom here brings you to a 'Troubleshooting Windows Server 2008 R2 Foundation' page which indicates :
Error message | Explanation |
|---|---|
The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. | This error occurs when the server cannot finish checking the number of users. It usually happens when the server cannot connect to a domain controller. You can safely close this message, but you should confirm the connection between the server and a domain controller. The server will not shut down as a result of this issue. If the message does not recur within two hours, the problem is resolved. |
The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliant check cannot be completed, the server will automatically shut down in 0 hour(s) 30 minute(s). | This error occurs when the server cannot finish checking the requirements for the root domain, forest trust configuration, or both. It usually happens when the server cannot connect to a domain controller. Sometimes this error occurs intermittently—if you close the error message and it does not recur within two hours, the problem is resolved. However, if the situation persists, the server will shut down 10 days after the first time the compliance check failed. Each time this error message occurs, it will state the actual time remaining before the server will shut down. If you restart the server after is has shut down because of noncompliance, the server will shut itself down again in 3 days. |
The biggest problem is that now the company's main SQL Server and .NET-based application (which runs on 'new-server' won't load, even on the 'new-server' itself.
To be honest, if I could just get things back to the way they were then I'd be happy.
Can anyone suggest what I might try now to get things back the way they were? Thanks.