Support For Windows 11
The documentation now lists Windows 11 version 26H2 (build 10.0.26300) with support indicators shown as ❌, ✅, and ✅.
Track documentation and Message Center changes for Microsoft Configuration Manager.
Microsoft Learn documentation ↗The documentation now lists Windows 11 version 26H2 (build 10.0.26300) with support indicators shown as ❌, ✅, and ✅.
The documentation now states that built-in Asset Intelligence reports are removed from Monitoring > Reporting > Reports in version 2609. References apply to version 2603 and earlier.
The documentation now states that all SQL Server versions currently supported by Configuration Manager support TLS 1.1 and TLS 1.2. Secondary site servers now require SQL Server 2017 Express with CU2 or later, replacing the previous SQL Server 2016 Express SP2 minimum.
The documentation now states that Microsoft Defender Antivirus contextual file and folder exclusions can be specified in the policy setting or with the Set-CMAntimalwarePolicy cmdlet starting in version 2609.
The documentation states that the deprecated `scepinstall.exe` installer will no longer be included with Configuration Manager starting in version 2609.
The index now includes Configuration Manager 2609 and links to KB 2377842. Entries for versions 2107 through 2211 were removed, and the page date was updated.
The documentation states that version 2609 removes the Catalog Synchronization and Inventoried Software Status sections from the Asset Intelligence home page and removes Asset Intelligence reports from Monitoring > Reporting > Reports.
The documentation now requires ODBC Driver 18.6.2.1 or later for Configuration Manager 2609 and later, and SQL Server 2017 CU2 or later starting with 2609. Unsupported versions can block installation or upgrades; it also identifies version-specific incompatible ODBC releases and adds a non-blocking warning about automatic client approval.
Starting with version 2609, the Asset Intelligence report category and its 67 reports will be removed. They apply to version 2603 and earlier.
Starting in version 2609, the Catalog Synchronization and Inventoried Software Status sections, along with Asset Intelligence reports, are removed. The page instead provides deprecation information and links to the product lifecycle dashboard and Asset Intelligence client settings. Earlier procedures apply only to version 2603 and earlier.
The page date changed to September 22, 2026, and the “What’s new” link changed from version 2503 to version 2609.
The documentation now specifies Microsoft ODBC Driver for SQL Server and links to minimum, validated, and blocking versions. Starting in version 2609, Configuration Manager automatically installs the Microsoft OLE DB Driver for SQL Server and no longer requires SQL Server Native Client; versions 2603 and earlier retain the previous Native Client behavior.
The guidance now requires TRUSTWORTHY for Configuration Manager 2603 and earlier, but says it isn't needed and should be skipped for version 2609 and later when loading SQLCLR assemblies.
The documentation marks SQL Server 2016 and SQL Server 2016 Express as deprecated in version 2609. SQL Server editions earlier than SQL Server 2017 CU2 must be upgraded before installing or updating to 2609; the Visual C++ Redistributable on secondary sites must also be updated.
The documentation no longer lists Windows Server 2012 R2, Microsoft Hyper-V Server 2012, or Windows Server 2012. The page date was updated to September 21, 2026.
The documentation date was updated, and the support table now lists ConfigMgr 2509, 2603, and 2609 instead of 2503, 2509, and 2603.
The documentation now lists Windows 11 25H2 as supported with ConfigMgr 2503, 2509, and 2603, and adds ConfigMgr 2609 to the matrix.
The documentation table now lists ConfigMgr 2509, 2603, and 2609 instead of 2503, 2509, and 2603. The page date was also updated.
The documentation now states that Configuration Manager supports data deduplication with distribution points on supported Windows Server versions, replacing the explicit “Windows Server 2012 or later” wording.
Starting with Configuration Manager version 2609, the TRUSTWORTHY database property is not required to load Microsoft-signed SQLCLR assemblies, including for databases using SQL Server Always On availability groups. Version 2603 and earlier still require TRUSTWORTHY to be enabled.
Starting with Configuration Manager version 2609, Windows Server 2012, Windows Server 2012 R2, and their Windows Storage Server editions will no longer be supported as client operating systems.
The page now lists version 2609 (5.00.9152.1000), released September 28, 2026, with support through March 28, 2028. Version 2503 is now shown as plain text.
The documentation now lists SQL Server 2025 and removes SQL Server 2016, SQL Server 2014, and the SQL Server 2016 upgrade link.
The Configuration Manager version 2309 documentation now links to the prerequisite-checks page for minimum required versions, validated versions, and known blocking issues for the ODBC driver for SQL Server.
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.