What’s changing
Configuration Manager 2509 introduces boundary awareness for Windows PE. Previously, a device booted into WinPE did not benefit from the same boundary evaluation as a fully installed Windows client, which could lead to less predictable content source selection during deployment. With this change, WinPE participates in boundary evaluation, so the boot environment can be associated with the appropriate boundary and boundary group.
Who this affects
The change applies to Operating System Deployment scenarios that rely on Windows PE-based boot images. If you deploy operating systems with task sequences — whether via PXE, bootable media, or a running client that restarts into WinPE — this behaviour is relevant to your environment.
- Task sequence deployments that boot into Windows PE
- Environments with multiple sites, boundaries, and distribution points
- Remote or branch office locations where local content sources matter
Why it matters
Boundary awareness in WinPE means the deployment process can align content location requests with the boundary configuration you have already designed. In practice, that should mean more consistent selection of nearby content sources during imaging and fewer surprises when a device in a remote location pulls content across a slow link.
What to review
Before and after upgrading, confirm your boundaries and boundary groups accurately reflect your network layout, and check that the distribution points referenced by those boundary groups hold the content your task sequences require. Then validate a small set of test deployments from each key location so you can observe the content source that WinPE selects.
- Verify boundary and boundary group definitions, including overlaps and fallback relationships
- Confirm boot images and task sequence content are distributed to the expected distribution points
- Test OSD from at least one device per network location and review the SMSTS logs for content location decisions
Summary
WinPE boundary awareness in Configuration Manager 2509 brings the pre-installation environment in line with the boundary design you already maintain for installed clients. The main action for admins is validation: make sure boundaries, boundary groups, and content distribution are accurate, then test OSD from the locations that matter most.
Source: Microsoft Learn. Summarised independently — check the source for the latest detail.