Preferred Software Update Points
Now that we have the option to define both Distribution Points and Management Points as preferred, it'd be terrific if we could have the same option for Software Update Points. It would make a strong case when designing a flat hierarchy.
With 1706, there is no much more control over SUPs and mapping to Boundary Groups. There is one more item left, which will allow control to failover (timeout) faster than 2 hours:
Everything else for this item is completed in 1706.
Robert Marshall - EM MVP commented
A design element that has a dramatic design influence due to the role lacking boundary affinity. This is a must have.
Please! This would be super useful in situations where there are isolated enclaves that have a large amount of servers. (DMZ's, hot sites, etc).
Big thumbs up, agree!
setting up SUP points to suit DMZ environment (No Internet Clients) caused big issues on LAN connected to same Primary. As others have mentioned DPs and MPs issue has been resolved by explicitly defining them. SUPs need to have the same ability to accommodate multiple corporate LAN \ WAN setups
I find it amazing how large Metadata transfers are to each client. Our environment has over 1500 remote locations and metadata transfers can create WAN outages. For the same reason you have Distribution Points to handle content downloads, Defining Software Updates points by Boundary Groups seems the next logical step.
Eric Delmotte commented
Very good, specially when you have machines behind a firewall always trying to reach the top level SUP in place of the one existing his side of the FW (supposed to switch on other SUP after 2 hours, but doesn't work if the FW drop packets in place of responding to the request)