''SCCM 2503'' Version Upgrade Guide
In this article, I will explain the steps for updating the Configuration Manager product to version 2503 comprehensively.
Microsoft regularly releases two new versions of Configuration Manager each year. These are typically released in April and October. These versions have an 18-month lifecycle after their release date, after which support for these products ends. It's crucial to keep your Configuration Manager version up-to-date to ensure support and avoid critical issues.
NEW IN THIS VERSION
As part of Microsoft's Secure Future Initiative (SFI), Configuration Manager version 2503 focuses on security and quality updates. This release includes no new features. Additionally, it addresses approximately 230 bugs from the previous release. You can review the bug summary here.
EARLY UPDATE RING
Currently, version 2503 is available in the early update ring, and you need to run the following powershell script to view and download this update in the console.
https://go.microsoft.com/fwlink/?linkid=2099733
After this process, you will see that version 2503 has started to be installed in the Configuration Manager console.
PRE-UPDATE CHECKLIST
- Current Version Control
To install version 2503, you must first upgrade your current version to at least 2309. However, since HTTP connections will not be accepted in the new version's prerequisites due to the EHTTP feature introduced with version 2403, if you are using a version lower than 2403, I recommend first upgrading to 2403 and then directly to 2503.
- Microsoft .NET Framework Version Control
The latest version of .Net version 4.82 must be installed on all components of the Configuration Manager.
- Check Windows ADK Version
https://learn.microsoft.com/en-us/intune/configmgr/core/plan-design/configs/support-for-windows-adk
You can access the list of supported versions and if it is missing, you can download and install the appropriate version.
- ODBC Driver Check for SQL Server
Microsoft ODBC Driver for SQL Server 18.1.0 or later must be installed on site servers and site system roles.
- Windows Update
After installing all existing updates on the server and restarting it, the version update process should be continued.
POST-UPDATE CHECKLIST
There are a few important things to check after the version update process is complete. These are:
- Configuration Manager Console:
Once the process is complete, the console must be restarted to install the new version. When the console restarts, a screen will open to install the new version, and the installation process must be completed from there.
- Updated Client Package:
- Client Upgrade Setting:
In the client upgrade settings in the hierarchy settings, ensure that the "Automatically upgrade the client when a new client update is available" option is selected. As long as this feature is enabled, client agents are automatically updated with each version upgrade.
- Deployment Control with Group Policy:
If the Configuration Manager agent is distributed to clients via script or VBS via group policy, the agent version must be updated in the scripts that are linked to the relevant policy.
In conclusion
While Configuration Manager version 2503 doesn't offer any new features, it stands out as a critical update for system stability, with its security and quality improvements. By following the steps above, you can ensure a smooth transition in your environment and take advantage of the support period.
Remember, the key to a sustainable and secure infrastructure for system administrators is to stay up to date!