Prevent CM clients from attempting to switch SUP's when there is no network connectivity of any kind
It's rare today to be in locations without any network connectivity at all, but it does happen. In this situation the CM client will continually attempt to switch SUP's. This can result in a user returning to the office and receive patching errors because the CM client happens to be trying to reach a SUP it can't contact, a DMZ server for example. Yes, this should correct itself over time, but preventing it from happing in the first place would be preferred.
So the suggestion is to add some sort of network connectivity check to the SUP selection process to prevent unnecessary SUP switching.
I have exactly this issue. If I set up a boundary with the DMZ IP ranges and assign the DMZ SUP as a site server associated with the boundary group then home users (whose IPs tend to fall in the same range) all try to hit the DMZ server automatically. With no boundary set up and the DMZ SUP just added to the default boundary group, it's a 50/50 chance a client will attempt to use it.