Configuration Manager 2409 Upgrade Guide

In this step-by-step Configuration Manager 2409 upgrade guide, I will explain how to update your existing SCCM servers to version 2409. This guide will cover all the new features and known issues in the 2409 release, as well as details on console and client upgrades.

On November 29, 2024, Microsoft released SCCM 2409, marking the second current branch release of the year. As per the SCCM release cadence, there will be two current branch versions released every year. In the year 2025, current branch versions 2503 and 2509 will be released.

Update 2409 for the current branch of Configuration Manager is available as an in-console update. You can apply this update on sites that run version 2309 or later.

New Features in SCCM 2409

Version 2409 of Configuration Manager introduces the following enhancements and new features.

• The all-new centralized search box now enables the option to select the desired workspace for searching.
• SQL extended protection for authentication, a security feature, strengthens defenses against Man-in-the-Middle (MITM) attacks, increasing the security of SQL Server connections made with extended protection.
• Configuration Manager 2409 supports deploying Windows 11 24H2 and Windows Server 2025.
• The 2409 update adds software metering support for Arm64 devices.
• BitLocker support is available on Arm64 devices.
• CMG Enhanced security option.
• Microsoft has improved the performance of policy processing and collection evaluation.

All the features listed above are detailed in Microsoft’s post on what is new in Configuration Manager version 2409.

Pre-Upgrade Checklist

Before you perform the Configuration Manager 2409 upgrade, please review the below pre-upgrade checklists:

• Begin installing the update 2409 from the top-level site of your hierarchy. Start the installation from your central administration site (CAS) or from your stand-alone primary site.
• To update to version 2409, ensure your Configuration Manager is running version 2309 or later.
• Configuration Manager now requires Microsoft .NET Framework version 4.6.2 for site servers, specific site systems, clients, and the console.
• Install Windows Updates on your site server before upgrading. Install any critical OS updates for each applicable site system. If there is a pending reboot, the upgrade will fail.
• Before upgrading to the 2409 version, site servers and site system roles must have the Microsoft ODBC Driver for SQL Server 18.1.0 or later installed.
• Make sure there are no database replication issues before the upgrade.
• Temporarily stop any antivirus software, as it may block the upgrade.
• Create a backup of the site database before the upgrade. A successful backup will aid in disaster recovery.
• If you or a third-party product customizes any Configuration Manager configuration files, save a copy of your customizations.
• Review hardware inventory customizations.
• Ensure that no content distributions are made to branch distribution points during the 2409 upgrade.

Installing Hotfixes before Upgrading

There were plenty of hotfixes released ConfigMgr version 2403 and most administrators want to know if they should install all the existing hotfixes before updating to version 2409. The short answer is ‘No.’ That’s because the new SCCM 2409 release will contain all previously issued hotfixes for Configuration Manager. Microsoft supports a direct upgrade from SCCM 2403 to 2409, even without any installed hotfixes.

Windows ADK Support for SCCM 2409

SCCM 2409 supports both the latest versions of the Windows 10 ADK and the Windows 11 ADK.

• For Windows 10, you can install the Windows ADK for Windows 10 version 2004.
• For Windows 11, you can install the Windows ADK for Windows 11 version 23H2.

If you have installed an older version of ADK on your SCCM server and are upgrading your Windows 10 to newer versions like Windows 10 24H2 or Windows 10 23H2, you must upgrade your ADK to the latest version available. Use the following guide to update ADK on SCCM server.

SCCM 2409 Generally Available

Update: As of December 16, 2024, SCCM version 2409 is globally available for all customers to install. The Slow Ring update for 2409 has been published and is now available to all customers without the need for opt-in. That means the SCCM 2409 update should be available in the console for installation. You don’t have to run the opt-in script anymore.

The ConfigMgr 2409 update takes a few minutes to download and extract all the necessary files. The update state changes from ‘Downloading‘ to ‘Ready to Install‘ in the console. If the update displays as downloading and doesn’t change, review the hman.log and dmpdownloader.log for errors.

Run the setup prerequisite checker for 2409

Before you perform the SCCM 2409 upgrade, you must always run the prerequisite check. The prerequisite check will determine if update 2409 can be installed without any issues.

Here’s how you run a prerequisite check for the 2409 update. Launch the Configuration Manager console. Navigate to Administration > Overview > Updates and Servicing. In the top ribbon, select Run Prerequisite Check.

Depending on your configuration, the prerequisite check could take a long time to complete. You can monitor all the prerequisite checks in the monitoring node of the console. In addition, you can also review the ConfigMgrPreReq.log to know the status of the prerequisite check.

Configuration Manager 2409 Upgrade

Once the prerequisite check is successful, you can install the SCCM 2409 update with the following steps:

• Launch the Configuration Manager console.
• Navigate to Administration > Overview > Updates and Servicing Node.
• Select the Configuration Manager 2409 update and click ‘Install Update Pack.’

Configuration Manager version 2409 includes the following updated components:

• Configuration Manager site server updates
• Configuration Manager console updates
• Configuration Manager client updates
• Fixes for known issues
• New Features

Since we have already performed the prerequisite check, you can enable the checkbox to ignore the prerequisite check warnings. Click Next.

On the Features tab, check the boxes for the new 2409 features you want to enable during the upgrade. For now, you can skip this step and enable these new features after the upgrade is complete.

For Client Update Options, select the desired option for updating the clients in your hierarchy. There are two client update options available while installing the update.

• Upgrade without validating: This option allows updating only client members of a specific collection.
• Validate in pre-production collection: With this option, you can validate the client update on members of the pre-production collection while keeping your production client package intact.

Please refer to the SCCM client upgrade options to understand the options available for upgrading the client agents automatically to the latest version. Select the desired client agent update option and click Next to continue.

On the License Terms tab, accept the license terms that are mandatory to install the 2409 update and click Next.

If you have already enabled SCCM Cloud Attach (Tenant Attach) with Intune, you will see an option to upload the Microsoft Defender for Endpoint Data for reporting on devices uploaded to Intune. If your SCCM setup does not include tenant attach, you can skip this step and proceed to the next step.

In the Summary window, you see a summary of the settings that you have configured for installing the SCCM 2409 update. Review them and click Next.

On the Completion window, click Close.

Monitor the ConfigMgr 2409 Upgrade

A Configuration Manager administrator can monitor the 2409 upgrade process using the following steps:

• In the Configuration Manager Console, go to the Monitoring workspace.
• Select Overview > Updates and Servicing Status.
• Right-click the Configuration Manager 2409 update and select Show Status.
• You can also review the 2409 upgrade by reviewing the CMUpdate.log file located on the site server.

Upgrade the Console

The SCCM 2409 upgrade will uninstall the old console version and install a newer one. You should not skip the console upgrade process because you will be unable to use an older version of the console.

To upgrade the Configuration Manager console to the latest version, you can either refresh the console once or close and launch the console. For some of you, a yellow notification bar appears just below the top ribbon. Click Install the new console version to begin the console upgrade.

After upgrading to version 2409, the new Configuration Manager console version is 5.2409.1181.1000. If the console upgrade fails, restart the server and try again. If the error persists, review the ConfigMgr Console log files.

Verify the upgrade

After the console upgrade is successful, launch the console. In the top-left corner, click on the drop-down arrow near the home button and select About Microsoft Configuration Manager.

The following details confirm that your site has been upgraded to version 2409.

• Microsoft Configuration Manager Version: 2409
• Console Version: 5.2409.1181.1000
• Site Version: 5.0.9132.1000

The build number of Configuration Manager version 2409 is 9132, and the full version is 5.00.9132.1000. Refer to the following post on build numbers and versions of previous Configuration Manager releases.

Upgrading Clients

The production client version of SCCM 2409 is 5.00.9132.1009. The recommended method to upgrade all the existing clients is by using the Automatic Client Upgrade feature. This will upgrade all the clients in your production setup to version 5.00.9132.1009.

Using the automatic client upgrade, you can upgrade the clients to the 2409 version.

• In the SCCM console, go to Administration > Site Configuration > Sites.
• Click Hierarchy Settings in the top ribbon and select the Client Upgrade tab.
• Tick the checkbox “Upgrade all clients in the hierarchy using the production client“.
• Set the required number of days for an automatic client upgrade to occur.
• Click Apply and OK to save the changes.

To group all the clients who have not updated to the latest version for the 2409 build, use the query below to create a device collection. The query will list all the computers that don’t have the latest client agent version, 5.00.9132.1009.

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion != '5.00.9132.1009'

Post-Update Checklist

The following post-update checklists are suggested by Microsoft following the installation of an SCCM 2409 upgrade:

• Confirm SCCM version and restart the server.
• Confirm site-to-site replication is active.
• Update Configuration Manager consoles to the latest version.
• Reconfigure database replicas for management points.
• Reconfigure availability groups and any disabled maintenance tasks.
• Restore hardware inventory customizations
• Restore user state from active deployments
• Update Client Agents
• Check for expired third-party extensions.
• Enable any custom solutions.
• Update boot images and media.
• Update PowerShell to help content

Known issues in ConfigMgr 2409

There are two known issues in the SCCM 2409 fast ring version:

1. CMPivot issue found in the Fast Ring. This issue is resolved in the slow ring release. For customers who have already installed the update, a new hotfix will be released.
2. Customers must upgrade SQL 2012 or 2014 Express, Standard, or Enterprise editions to SQL 2016 or the latest supported version. VC++ Redistributable version needs to be upgraded to the latest version on secondary sites.

SCCM 2409 Deprecated features

MDT integration with SCCM and stand-alone is no longer supported with Configuration Manager 2409. The deprecation was first announced in December 2024, and the end of support will take place after the first release on October 10, 2025. Customers should remove MDT task sequence steps, followed by removing MDT integration, to avoid TS corruption and modification failures.