Ethan Brooks
How To Upgrade to SCCM 2503: A Comprehensive Step-by-Step Tutorial
How to Upgrade Your SCCM Environment to Version 2503
## Check your current setup early on
First, make sure your current SCCM version is at least 2409. You can verify this by opening the `File` menu in the Configuration Manager console and clicking on `About Configuration Manager`. If it’s below 2409, you’ll probably need to do some interim updates before jumping to 2503—so skip ahead and update your SCCM first.
Also, double-check you’ve got the right prerequisites installed—latest Windows ADK (at least version 10.1.26000.100.2451), the newest Visual C++ redistributables, and the latest ODBC driver (version 18.1.0 or later). These are essential for a smooth upgrade; if you skip these, stuff might fail or behave weirdly.
## Get the latest Windows ADK and Windows PE
Head over to [Microsoft’s official site](https://docs.microsoft.com/en-us/windows-hardware/manufacture/windows-adk) and grab the Windows ADK. Save it somewhere like `C:\Downloads\SCCM2503\` so it’s easy to find.
Uninstall old versions first!
Go to `Control Panel` > `Programs` > `Programs and Features`, find any older Windows ADK and Windows PE, and remove them. Because of course, Windows has to make it harder than necessary.
Then, run the new ADK installer as an admin, accept all defaults, and wait till it finishes. After that, do the same for Windows PE—install that in the same folder.
## Update dependencies
Make sure your Visual C++ libraries are current. Run the installer for the latest version you downloaded—right-click, `Run as administrator`. Reboot after. Same goes for your ODBC driver, which needs to be version 18.1.0 or newer. If you’re feeling brave, update those before moving forward.
## Running the pre-upgrade script
Here’s the weird part—this is an early step but critical. You need to run the Early Update Ring script for SCCM 2503 (grab it from the official sources or your IT team). Right-click the PowerShell script, run as admin, and give it permission to extract files. It might ask for your SCCM server’s FQDN—so have that handy.
Open `Windows PowerShell ISE` as administrator, load the script, and execute. It’s supposed to help prepare your site for the new bits. No guarantees why, but on some machines, it’s a bit flaky. Maybe necessary for some environment quirks, so don’t skip it.
## Kick off the actual upgrade
Find your SCCM console, go to `Administration` > `Updates and Servicing`. You should see the 2503 update listed (if not, refresh a few times).
Right-click and pick `Download`. Watch the status pane; it can take a while, depending on your network speed.
Once downloaded, right-click again and choose `Install Update Pack`. Follow the prompts, accept the license agreements, and wait—this isn’t a fast process. On some setups, it takes quite a bit of time, so plan for idle time or a coffee break.
## Upgrade your console and verify
After the core update, the console will probably close itself once the install finishes, then re-open. When it does, check `File` > `About Configuration Manager` to confirm the version is now 2503. Yay.
## Don’t forget clients and boot images
Update your boot images: right-click on `Boot Images` under `Operating Systems`, then `Update Distribution Points`. Make sure to reload the PE environment with the new Windows ADK and Windows PE installed earlier.
Also, make sure client agents are updating smoothly—no point in having a shiny new server if clients are still running old agents.
## Troubleshooting and last-minute tips
– Backup everything beforehand. Yes, every blog says that, but it’s especially true here.
– If you hit errors, quickly check the log files in `C:\Program Files\Microsoft Configuration Manager\Logs`. They usually give enough clues.
– Patience is key—this process can stall or fail if the environment isn’t ready, so if something looks stuck, wait a bit or check for missing prerequisites.
– Sometimes, after the update, things aren’t quite right. Restart your site server, and recheck the console version again.
—
Summary
- Check your current SCCM version and prerequisites.
- Download and install the latest Windows ADK & PE, uninstall old versions first.
- Update Visual C++ libraries and ODBC driver.
- Run the pre-upgrade PowerShell script prepared for SCCM 2503.
- Download the update from Updates and Servicing in the console.
- Install the update pack and verify the version.
- Update boot images and client agents as needed.
Hopefully this shaves off a few hours for someone. Just something that worked on multiple machines. Fingers crossed this helps.