Windows Server Update Services (WSUS) deprecation

Karl-WE Thanks for the replies.

"Shutdown the Internet servers that WSUS uses"

AUM uses the same catalog and WU Services as Windows Clients / Servers would be natively using. I am not aware WSUS would connect to anything else. Does it? 

Probably not, but who knows? However, I would be surprised if Microsoft could not distinguish from where catalog/updates requests are coming from. It could be as simple as something, like, an agent string.

Off the top of my head, I see a couple ways to kill WSUS when desired:

1. If WSUS identifies itself during connection, simply drop those requests.
   1. If needed, one of the monthly cumulative Windows Updates could modify the WSUS role to include this "identification". This change may already have been done
2. Switch to new Internet endpoints that WSUS is unaware of.
   1. Duplicate the Internet endpoints. Use a Windows "Servicing Stack" Update to prefer the new endpoints. Of course, do not update WSUS's configuration. This change may already have been done

There are several ways to artificially break WSUS in this way. Microsoft has a history of doing things just like this.