FAQShop.com : Renaming a SUS Server To Stop Downloads In Progress

Renaming a SUS Server To Stop Downloads In Progress

While I was away on leave, someone took it up on themselves to push out the latest RPC Patches from my 'test' SUS Server. Little did they know that they had left pretty much all the updates approved. As this is only a 'test' box servicing a handful of client machines, it was then servicing 2200 client machines.

This flooded the network with traffic and slowed it down to a snails pace!! Once it was realized what was happening the SUS server was turned off and disconnected from the network.

I would like to know what would happen if I was to build a new SUS Server with a different name, change the Active Directory Group Policy to point to the new machine and push out the RPC Patches?? And how would I let all the the clients that were downloading from the old server finish their downloads without flooding the network again???

Contributed By: Scott Korman
I believe the download process is already underway for the those clients on the old servername.

You can use allow the clients to complete the cycle with the old servername, either with the old server or use DNS/WINS to point its name to the IP Address of the new server.

Another option would be to modify the registry settings and follow the process to force the AutoUpdate client the check-in, this would mean an AUState of "2", therefore checking in with the new settings.