Let’s discuss SCCM 2503 Current Branch Update now Available. SCCM version 2503 current branch is available as an in-console update. Site that run version 2309 or later can apply this update. The SCCM 2503 current branch provides many updates.
Do you know what is Configuration Manager Current Branch? The Configuration Manager Current Branch is a version of Microsoft’s Endpoint Configuration Manager designed for modern IT environments. You can take advantages of Configuration Manager changes.
After you update the site, also update clients to the latest version. The latest version 2503 branch receives regular updates, including new features, security patches, and critical fixes etc. It helps to get the latest technology and security standards for your organization.
Users must review the latest checklist for installing this update. When you use the current branch of Configuration Manager, you can install the in-console update for version 2503 to update your hierarchy from a previous version.
Table of Contents

SCCM 2503 Current Branch Update now Available
You must use a service connection point at the top-level site of your hierarchy to get the update for version 2503. In this blog post, i will help you to know more about Update of 2503 of SCCM Current Branch Now Available.
Features |
---|
Bug Fixes |
Console Improvements |
Client and Deployment Fixes |
- SCCM 2309 Hotfix KB26129847 Client Discovery Data Fix
- SCCM High Level Architecture Design Guide
- SCCM 2309 Hotfix KB26129847 Client Discovery Data Fix
Comprehensive Guide to Upgrading SCCM to Version 2503
Here is a comprehensive guide to upgrade the SCCM to Version 2503. You can install the Configuration Manager current branch is available as an in-console update. You can refer the Comprehensive guide to grade SCCM version to 2503.
Read more – Comprehensive Guide to Upgrading SCCM to Version 2409
Checklist for Installing Update 2503
Site system role can be in online or offline mode. To download the update when your service connection point is offline, use the service connection tool. After downloading the hierarchy, you can find it in the console. Follow the list below to install update 2503.
- Open the SCCM Console
- Go to the Administration workspace, select the Updates and Servicing node.
- Select the Configuration Manager 2503 update and click ‘Install Update Pack.

- MDT Integration and Standalone Support Deprecation in SCCM Version 2409
- Known Issues and Updates in SCCM Current Branch Version 2409
- Step-by-Step Guide to Deploying Windows 11 24H2 Using SCCM Task Sequence
Pre-Update Checklist
Before installing the update, you should review prerequisites like ensuring your site system servers meet the requirements for the new version. Install any critical OS updates and verify that your Configuration Manager console is updated. The below table shows the checklist.
Checklist | Details |
---|---|
All sites run a supported version of Configuration Manager | Before start the installation, Each site server in the hierarchy must run the same version of Configuration Manager. Use version 2303 or later to update to version 2503 |
Review the status of your product licensing | To install this update, you need an active Software Assurance (SA) agreement or equivalent subscription rights. When you update the site, the Licensing page presents the option to confirm your Software Assurance expiration date. |
Review Microsoft .NET versions | Configuration Manager now requires Microsoft .NET Framework version 4.6.2 for site servers, specific site systems, clients, and the console. |
Review the version of the Windows ADK | The version of the Windows Assessment and Deployment Kit (ADK) should be supported for Configuration Manager version 2503. |
Review SQL Server Native Client version | Install a minimum version of SQL Server 2012 Native Client, which includes support for TLS 1.2. |
Review SQL ODBC driver for CM | Starting with version 2309 and later, Configuration Manager requires the installation of the ODBC driver for SQL server as a prerequisite. |
Review the site and hierarchy status for unresolved issues | A site update can fail because of existing operational problems. Before you update a site |
Review file and data replication between sites | You must make sure file and database replication between sites is operational and current. |
Database replication | For database replication, to help resolve issues before you start the update, use the Replication Link Analyzer (RLA). |
Disable site maintenance tasks at each site | Before you install the update, disable any site maintenance task that might run during the time the update process is active. |
Temporarily stop any antivirus software | Antivirus software can lock some files that need to be updated which causes our update to fail. |
Back up customized files | If you or a partner product customizes any Configuration Manager configuration files, save a copy of your customizations. |
Review hardware inventory customizations | If you changed the state of hardware inventory classes in client settings, when you update the site, some classes may revert to a default state. |
Plan to use service windows | To define a period during which updates to a site server can be installed, use service windows. |
Read the release notes | Before you start the update, review the current release notes. With Configuration Manager, product release notes are limited to urgent issues. |
Install the Update
Start the installation from your central administration site (CAS) or stand-alone primary site. Child primary sites will automatically install the update after the CAS completes its installation. Secondary sites need to be updated manually.
Need Further Assistance or Have Technical Questions?
Join the LinkedIn Page and Telegram group to get the latest step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, Join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well.
Resource
What’s new in version 2503 of Configuration Manager current branch
Author
Anoop C Nair has been Microsoft MVP for 10 consecutive years from 2015 onwards. He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.