Swapping Windows NT Server With Windows Server 2003 Small Business Server
Posted on 2005-04-04
I frequently install servers for small businesses with Windows Server 2003 Small Business Server. In doing so, I have to replace the present server which is typically Windows NT Server 4.0 or Windows 2000 Server. So far, the quickest way for me to replace the server is to match User Accounts, File and Printer Shares, IP Address, Domain Name, login script, etc. - then copy all files off the old server to new server. I then remove the old server off the network and promote the new server to the Domain Controller. My downfall in this process however is that now I have to go around to each of the workstations and rejoin each workstation to the domain. I have tried matching the Computer Accounts in use on the present server with the new server but to no avail. This problem appears to occur in Windows NT Server 4.0, Windows 2000 Server as well as Windows Server 2003 (I recently had to upgrade an existing server that was running 2003 with another server that was running 2003). I may be wrong, but this problem does not appear to be related to Active Directory. It would appear that the workstations are looking for a SID perhaps rather than an IP or another identifying value. Am I on the right track? Or can someone point me to a better way of swapping servers. I am not attracting to the Microsoft way of demoting/promoting servers. I'd rather simply take the old server off the network as soon as possible. My question then is this - if there is an identifying value that I need to match on the new server - can I copy this value with a tool somehow? Or is there a better way that I could be swapping servers?