Add Boundary Group Selection to SUP Creation Process
It has become a semi-regular occurrence in the various communities that someone has created a new environment or rebuilt their SUPs and suddenly none of their clients updates are managed by ConfigMgr and they're getting updates direct from Microsoft.
Often the root cause is that they did not add the new SUP to any boundary groups. It's an additional step that users just need to kinda of magically know ahead of time to do. Which is to say people aren't going to know and find out the hard way.
Let's solve this somehow. For me, making boundary group selection part of the SUP configuration makes sense. I'd suggest defaulting to the default boundary group in that scenario.
Bryan Dam
shared this idea
1 comment
-
Bryan Dam
commented
It occurred to me just now that while SUPs are the one I've seen most frequently (probably because nuke-n-pave is a popular option) this should probably apply to all boundary aware site roles. If clients will only use a newly created role based on boundary information then make that part of the configuration process so that admins do not neglect it.