Step-by-Step SCCM 2503 Upgrade Guide

This comprehensive SCCM 2503 upgrade guide provides detailed instructions for updating your existing SCCM servers to version 2503, along with steps for upgrading the console and client components.

Configuration Manager 2503 is the first current branch release of the year 2025. As per the release cadence, Microsoft is committed to releasing two current branch versions every year. The next version of ConfigMgr will be 2509, which will be released in October 2025.

The version 2503 update is only applicable to sites running version 2403 or later. If you’re running version 2409 in your setup, you can directly upgrade to version 2503 without any issues.

SCCM 2503 Release Date

Microsoft released SCCM version 2503 on March 31, 2025. The support for SCCM 2503 ends on September 30, 2026.

The 2503 version of SCCM is a baseline version. When installing a new site, you can download and use the 2503 baseline version, but remember that the baseline media will be available only after global availability.

General Availability of version 2503

As of April 4, 2025, the version 2503 is currently released for the early update ring. To install this update, you need to opt in. After a few weeks, the update will be released globally for all customers.

New Features in SCCM 2503 Release

The SCCM 2503 release doesn’t include any new features. As part of Microsoft’s Secure Future Initiative (SFI) the 2503 version of Configuration Manager focuses only on security and quality updates. Over 230 reported bugs are resolved in the SCCM 2503 update. However, have a look at the KB31909343 that lists the summary of changes in Configuration Manager current branch, version 2503.

Pre-Upgrade Checklist

Before you upgrade to ConfigMgr 2503, review the below pre-upgrade checklists:

• Begin installing the update 2503 from the top-level site of your hierarchy. Start the installation from your central administration site (CAS) or from your stand-alone primary site.
• 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.
• The 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 upgrade.

Installing 2409 Hotfixes before Upgrading to 2503

If you are upgrading to version 2503, you can skip the hotfixes that were released for 2409 and upgrade directly to the 2503 version. Microsoft supports a direct upgrade from SCCM 2409 to 2503, even without any installed hotfixes.

The version 2503 of Configuration Manager current branch includes the following hotfixes:

• KB30385346: Update rollup for Microsoft Endpoint Configuration Manager current branch, version 2409
• KB30833053: Cloud management gateway installation update for Configuration Manager 2409

Windows ADK Support for SCCM 2503

SCCM 2503 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/11 to newer versions, you must upgrade your ADK to the latest version available. Use the following guide to update ADK on SCCM server.

Update Microsoft ODBC Driver for SQL Server

Configuration Manager current branch versions 2503, 2403, and 2309 contain a prerequisite rule that checks for Microsoft ODBC Driver 18 for SQL setup. Before performing the upgrade on any site system servers, this needs to be manually installed. The installation of Microsoft ODBC Driver 18 does not require a restart.

As per Configuration Manager 2503 release notes, the Microsoft ODBC redistributable component is updated to version 18.4.1.1. The Visual C++ redistributable is updated to version 14.40.33816.

Browse to the following download link to get the most recent version of the ODBC driver for SQL Server. Also download the latest Microsoft Visual C++ Redistributable version and install it before you install the new SCCM update. Refer to the following guide to install or upgrade the ODBC driver on SCCM Server.

Get the Early Update Ring Script for 2503

Download the following PowerShell script that adds your hierarchy or stand-alone primary site to the early update ring for version 2503: Version 2503 opt-in script.

Run the 2503 opt-in script and extract the contents to a folder. This folder contains the EnableEarlyUpdateRing2503.ps1. When you execute this script, it downloads the update 2503 in the console.

Close the Configuration Manager console. Launch PowerShell as an administrator. Change the path to the script location and run the enableearlyupdatering2503.ps1 PowerShell script. Enter the site server name (top-level site server name or IP address), and the script will download the SCCM 2503 update in the SCCM console.

In the Updates and Servicing node of the console, we now see the Configuration Manager 2503 Update state shows as ‘Downloading.’ If the update displays as Downloading and doesn’t change, review the hman.log and dmpdownloader.log for errors.

Troubleshooting Update Download Issues

On several setups, we have noticed that the SCCM 2503 update gets stuck in the downloading state. Hence, we have published a dedicated article to help you out: https://www.prajwaldesai.com/fix-sccm-update-stuck-downloading-state/.

Listed below are some common reasons why the upgrade prerequisite check fails and the solution to those errors and warnings.

• The site database has a backlog of SQL change tracking data: Solution
• Configuration Manager Pending System Restart: Solution
• SQL Server Native Client Version: Solution
• SCCM Update Stuck at Downloading State: Solution
• Enable site system roles for HTTPS or SCCM Enhanced HTTP: Solution
• Recommended version of the Microsoft .NET Framework. Warning: The Configuration Manager 2503 update requires at least DotNet version 4.6.2 but recommends the latest version 4.8: Solution
• ConfigMgr Database Upgrade Error 0x87d20b15: Solution
• Co-Mgmt slider is not pointed to Intune: Solution
• SQL client prerequisites are missing for Config Manager setup: Solution

Configuration Manager 2503 Prerequisite Check

To check if your ConfigMgr site is ready to upgrade to 2503, you must first run a prerequisite check. Launch the Configuration Manager console. Navigate to Administration > Overview > Updates and Servicing. Select the Configuration Manager 2503 update and 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.

Once the prerequisite check is complete, if you don’t see any warnings or errors, proceed to the upgrade step.

Upgrading SCCM to version 2503

Perform the following steps to upgrade your SCCM server to version 2503.

Step 1: Launch the Configuration Manager console. Navigate to Administration > Overview > Updates and Servicing Node. Select the Configuration Manager 2503 update and click ‘Install Update Pack.’

Step 2: The following components have been updated in Configuration Manager version 2503:

• 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.

Step 3: On the Features tab, check the boxes for the new 2503 features you want to enable during the upgrade. You can enable these new features after installing the update from Administration > Updates and Servicing > Features. Click on Next to continue.

Step 4: 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.

• 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.
• Upgrade without validating: This option allows updating only client members of a specific collection.

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.

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

Step 6: 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.

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

Step 8: On the Completion window, click Close.

Monitoring the ConfigMgr 2503 Upgrade

A Configuration Manager administrator can monitor the 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 2503 update and select Show Status.
• You can also review the CMUpdate.log file located on the site server to see how the update is progressing.

Upgrading the Console

After installing the SCCM 2503 update, you’ll be prompted to upgrade your console. The old console version will be uninstalled, and a newer console version will be installed. 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 2503, the final console version is 5.2503.1083.1000.

If the console upgrade fails, restart the server and try again. During the console upgrade, if you encounter any issues, you can always review the ConfigMgr Console log files.

Verify Upgrade

Once you’ve upgraded the console, launch it. Click on File and from the drop-down, select About Microsoft Configuration Manager.

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

• Microsoft Configuration Manager Version: 2503
• Console Version: 5.2503.1083.1000
• Site Version: 5.0.9135.1000

You can manually verify the site build number and version with the following steps:

• In the ConfigMgr console, navigate to Administration > Site Configuration > Sites.
• Right-click your site and select Properties.
• The site version is 5.00.9135.1000 and the build number is 9135.

Update Boot Images to the latest version

After upgrading to version 2503, the default boot images (x64 and x86) will automatically update on all the distribution points. If it’s not updated, you can manually update the boot images using the following procedure for Boot Image (x64) and Boot Image (x86):

• Launch the Configuration Manager console.
• Go to the Software Library > Operating Systems > Boot Images.
• Right-click the boot image and select Update Distribution Points.

SCCM 2503 Client Upgrade

The production client version of SCCM 2503 is 5.00.9135.1001. The recommended method to upgrade the clients is by using the Automatic Client Upgrade feature.

Using the automatic client upgrade, you can upgrade the clients to the 2503 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 production client“.
• Set the required number of days for an automatic client upgrade to occur. Click Apply and OK.

To group all the clients who have not updated to the latest version for the 2503 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.9135.1001.

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.9135.1001'

SCCM 2503 Post-Upgrade Checklist

Microsoft recommends the following post-update checklists after installing a SCCM 2503 upgrade:

• Confirm SCCM version and restart the server (if necessary)
• 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