![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 33%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBZ%3C/text%3E%3C/svg%3E)
Microsoft Security | Intune | Configuration Manager | Deployment
Deploying software and updates using Configuration Manager
The issue you are experiencing with OSD in your secondary site after upgrading to version 2509 of Configuration Manager may be related to the requirement for Boundary Group Management Point (MP) assignments. In version 2509, Windows PE-based OSD scenarios require that the Boundary Group the WinPE client belongs to must contain at least one Management Point. If no MP is associated with the client’s Boundary Group, WinPE will fail to retrieve policy, leading to errors like the ones you are encountering.
To resolve this issue, ensure that:
- The Boundary Group for the secondary site has a valid Management Point assigned.
- The Management Point is operational and can be reached by the clients in the secondary site.
- Check the logs for any additional errors that might provide more context on the failure, such as the
smsts.logwhich may show specific errors related to MP location queries.
If the MP is correctly assigned and operational, you might also consider reviewing the Configuration Manager logs on both the primary and secondary sites for any additional insights or errors that could be affecting the OSD process.