Apply Boundary Groups to WinPE Management Point selection
Currently it appears that when the SCCM agent in the WinPE boot image connects to a Management Point, it selects one without using the Boundary Group rules, instead selecting one from the AD published list, starting with the first alphabetically.
Instead this should behave like the full blown Windows SCCM Client and select a Management Point based on Boundary Groups such as IP range.
It is worth noting that Distribution Points are selected correctly according to Boundary Group by the WinPE client, for OSD content.
Thank you for the feedback, updating status to Noted
See https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/ for an explanation of each status value
I was having issues with my OSD via PXE taking a long time because of this. I have multiple DP/MP between sites and boundary groups setup. Would be nice if there was a way to specify which MP to hit maybe within the boot image.
I used Trey Bruneau's work around and it worked like a charm. Couple things I did different:
1. Instead of a scheduled task, im setting the reg value in group policy
2. I just changed the order of the value inside the key. This way all MPs are still listed but its trying the one I want first. If it fails, the second MP can still service the request.
It should at least be possible to specify a default MP for any given DP as an option and have it pick that up during PE. Editing regkeys as a workaround should not be necessary.
I don't know how this isn't more of a pain-point, especially for international companies. It adds considerable time to imaging.
Frank Rojas commented
Boundaries for MPs are not currently supported during Task Sequences. This is actually documented here (see the second note):
Trey Bruneau commented
As a workaround we are modifying the following registry setting via scheduled task everyday on the local DP to ensure clients pick the right MP.