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 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.
RetirementAction required 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 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.
Feature updateAction required 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.
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.
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.
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.
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 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.
Feature updateAction required 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 page date changed to September 22, 2026, and the “What’s new” link changed from version 2503 to version 2609.
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 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 now lists SQL Server 2025 and removes SQL Server 2016, SQL Server 2014, and the SQL Server 2016 upgrade link.
The documentation now lists Windows 11 25H2 as supported with ConfigMgr 2503, 2509, and 2603, and adds ConfigMgr 2609 to the matrix.
The documentation date was updated, and the support table now lists ConfigMgr 2509, 2603, and 2609 instead of 2503, 2509, and 2603.
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.