Configuration Manager And Windows As Service
The Configuration Manager documentation now links to `integrate-windows-update-client-policies.md` instead of `integrate-windows-update-for-business-windows-10.md`.
Track documentation and Message Center changes for Microsoft Configuration Manager.
Microsoft Learn documentation ↗The Configuration Manager documentation now links to `integrate-windows-update-client-policies.md` instead of `integrate-windows-update-for-business-windows-10.md`.
The article was rewritten to explain co-management scenarios, scan source policies, common pitfalls, troubleshooting, and the effects of receiving Windows updates directly from Windows Update. It documents impacts to compliance reporting, Microsoft app updates, third-party updates, and software-update-based client deployment.
The Configuration Manager article covering Windows Update client policies, co-management considerations, limitations, prerequisites, and client identification procedures was deleted.
The article’s guidance on integrating Windows Update client policies was revised. It continues to state that computers using Windows Update client policies or Windows Insiders aren’t evaluated in Windows servicing plans and must use Configuration Manager software updates with WSUS.
The article now links to `integrate-windows-update-client-policies.md` instead of `integrate-windows-update-for-business-windows-10.md`.
The article now revises its explanation of how Configuration Manager distinguishes Windows Update client policies from WSUS, including the UseWUServer attribute.
The version 1706 documentation now links to the Windows Update client policies article at a new path, retaining the same configuration section anchor.
The application documentation now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The document’s metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation replaces `ms.subservice: core-infrastructure` and `ms.service: microsoft-endpoint-configuration-manager` with `core-infra` and `configuration-manager`.
The page replaces `core-infrastructure` with `core-infra` and `microsoft-endpoint-configuration-manager` with `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page’s metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page now uses `core-infra` and `configuration-manager` as its subservice and service metadata values.
The article metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `protect`.
The page metadata changes `ms.subservice` from `core-infrastructure` to `core-infra` and `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, and its subservice metadata changed from `core-infrastructure` to `core-infra`.
The page now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page’s service classification changed from `core-infrastructure` / `microsoft-endpoint-configuration-manager` to `core-infra` / `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `configuration-manager` with `core-infra` instead of `microsoft-endpoint-configuration-manager` with `core-infrastructure`.
The article’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, and its subservice metadata changed from `operating-system-deployment` to `osd`.
The document metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The BitLocker settings documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s metadata values changed from `core-infrastructure` to `core-infra` and from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` metadata values.
The documentation metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata changed from `microsoft-endpoint-configuration-manager`/`core-infrastructure` to `configuration-manager`/`core-infra`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: osd` and `ms.service: configuration-manager` metadata values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` in place of the previous metadata values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s service metadata changed to `configuration-manager` and its subservice metadata changed to `core-infra`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The article’s metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice=core-infra` and `ms.service=configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` and `configuration-manager` service metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The document’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The checklist metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` / `core-infrastructure` to `configuration-manager` / `core-infra`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page now pairs `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous identifiers.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the `ms.service` metadata value.
The documentation metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the co-management subservice.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article’s service metadata changed to `configuration-manager`, and its subservice metadata changed to `core-infra`.