replace-an-old-server-with-a-new-server-using-the-same-ip-same-name-same-shares

Tavis Gardner

I’ve 2003 server on a Workgroup named “server1” that I want to replace with a new 2019 server currently name “server2” (they are called something different in production and server2 on local network currently). Don’t know for sure why on workgroup but it does connect to special network through ASA firewall and also to our local network. The FW setup allows for ping/connecting by IP to both networks and using hosts files. When ready I want to shutdown old server, connect network connections from old server and assign all IPs on it to new server.
My question is what problem or no problems should occur if I try to name the new server from “server2” to “server1” in a Workgroup (no domain) after old server disconnect from network connection. Also I’m not sure about shares, registry or special users or other configurations other than hosts file.
This seems to be good for domain computer but what about workgroup computer is my question:
https://community.spiceworks.com/how_to/75097-replace-an-old-file-server-with-a-new-file-server-using-the-same-ip-same-name-same-shares
In AD domain you can’t have computer with same name and if you just disconnect old computer and bring up new computer and rename it to new computer name it may have problems or replace old computer. Which is what I want but not sure what may occur. I believe best practice in AD domain is to delete same name and add new computer to domain after deletion completes. But sometimes on AD domain with multiple DC replication of change doesn’t reach all DC in timely manner. Which can lead to remote desktop issue and the trust issue. To fix remove one, run ipconfig /flushdns and add back with different name.

Mike Rodrick

@Tavis-Gardner ,

In a workgroup, you don't have as many things to worry about. In a domain environment, you have to worry about the computer account in Active Directory.

Best practice in a domain is NOT to delete the computer account, because the computer account may belong to groups, and you will lose those group memberships if you delete the object. Instead, you should reset the computer account, and then join the new server to the domain using the existing account. This way group membership and permissions are not lost.

Since there is no centralized account in a workgroup, you won't have to worry about this. Most name resolution is dynamic, so it will be updated automatically. Flushing caches as you mentioned will speed the process up. Once you remove the old server, remove any DNS records for that server. Then when you rename and reboot the new server, run ipconfig /registerdns to speed up the registration of new DNS records.

You will have to recreate any shares and other configurations on the new server. This includes any local accounts that are used to grant access to the server. You will need to recreate these with the same password, or update anywhere these accounts might be referenced. I would recommend keeping the old server around (offline) so you can boot it up if needed to check configurations that were missed.

The biggest concern will be anything that uses MAC addresses. Much of this should be updated dynamically, but it might take some time. Switches should update their MAC address table pretty quickly. Might be a good question for our Cisco forums!