This post is the SCCM 1810 upgrade step by step guide. Recently, Microsoft released SCCM 1810. In this post, you will get the details about how to upgrade SCCM 1810. Microsoft already released SCCM 1810 in the slow ring and it’s available for all the environment.
What are the prerequisites which you suppose to look at before upgrading? More details below read through.
Table of Contents
How to Download SCCM 1810 Production Version
You don’t have to go to Microsoft website and download SCCM 1810. Instead, SCCM 1810 will be available in your SCCM console if you are using the supported version. You should have an ONLINE Service Connection point to get the updates available in the console.
The Supported version of SCCM CB – https://www.anoopcnair.com/sccm-life-cycle/
Why SCCM 1810 is NOT Available in my Console?
You could end up in the above situation that SCCM 1810 is not available in your console. Ok, don’t worry your SCCM infra might be fine. Microsoft follows two rings when they release SCCM 1810.
SCCM 1810 will get released in a SLOW and FAST ring. SCCM 1810 fast ring is an opt-in update. The fast ring won’t be available to your console until you are opt-in for SCCM 1810 update. More details available in the following post from Microsoft.
So the SCCM 1810 version released this week is a FAST/opt-in ring, and that is why you can’t see the latest SCCM 1810 version in your console. Once you complete the opt-in process, SCCM 1810 version will be available in your console.
You will get more details about SCCM 1810 upgrade checklist and prerequisites in this section of the post.
SQL Server Native Client version; Warning; Configuration Manager sites require a supported SQL Server Native Client version. To enable TLS 1.2 support, you must install a supported version of SQL Server Native Client on the specified site database server. For more information, see https://go.microsoft.com/fwlink/?linkid=2026746
SQL Requirements for SCCM 1810 Upgrade
You need to make sure your SQL version is supported and ready for SCCM 1810 upgrade. In an SCCM hierarchy with multiple sites, different sites can use different versions of SQL Server to host the site database. The following are the support SQL version for SCCM 1810. More details available here.
SQL Server 2017 CU2: Standard, Enterprise
SQL Server 2016 SP2: Standard, Enterprise
SQL Server 2016 SP1: Standard, Enterprise
SQL Server 2016: Standard, Enterprise
SQL Server 2014 SP3: Standard, Enterprise
SQL Server 2014 SP2: Standard, Enterprise
SQL Server 2014 SP1: Standard, Enterprise
SQL Server 2012 SP4: Standard, Enterprise
SQL Server 2012 SP3: Standard, Enterprise
Windows Server OS Requirements for SCCM 1810 Upgrade
Windows server OS requirements for SCCM 1810 upgrade. This is important to check the compatibility of your server version with SCCM 1810. I don’t think this would be an issue for most of your SCCM environment. But, it worth checking the list of supported OS for SCCM CB from Microsoft here.
Windows Server 2019: & Windows Server, version 1809 – Site Systems
Windows Server 2016: Standard and Datacenter
Windows Server 2012 R2 (x64): Standard and Datacenter
Windows Server 2012 (x64): Standard and Datacenter
Hardware, Prerequisite, and Size-Scale Support for SCCM CB 1810
The following are another critical documents which you want to look and confirm whether your SCCM CB environment is ok to continue with SCCM 1810 upgrade.
SCCM 1810 is Baseline version and Checklist?
SCCM 1810 is not a baseline version, and I think, SCCM 1902 will be the next baseline version for SCCM CB. You have to upgrade to the latest baseline version from SCCM 2012. The newest baseline version of SCCM CB is 1802.
Once you are in SCCM 1802, you can update your SCCM version to 1806 via in-console update. SCCM 1810 in console version will be available only for the SCCM versions 1710, 1802, or 1806. I would recommend reading Microsoft doc to get more details about the same.
SCCM 1810 Update Download Stuck Issues?
Do you have trouble downloading the SCCM 1810 update? OK, no worries I have seen these issues many times, and I made a video post about the SCCM CB updates and servicing download issues.
If any of the above steps are not working, then I’m sure there is a problem with your enterprise network and proxy settings. Try to make sure you have proxy exception and firewall ports open.
- Process update package
- Download update package cab file
- Extract update package payload
- Download redist
- Report package as downloaded
Start – SCCM 1810 Upgrade
How to start the upgrade of SCCM 1810? Make sure you read the checklist and prerequisites mentioned in the above section before you kick-start the SCCM 1810 installation process. You can start the upgrade process once it’s downloaded and in Ready to Install state.
I would recommend running the prerequisite checks a couple of days before the actual SCCM 1810 upgrade date and schedule.
- Navigate to SCCM console to Administration workspace
- Go to Cloud Services -> Updates and Servicing
- Click on Configuration Manager 1810 update and click on Install Update Pack
- Go through the Configuration Manager Update Wizard and complete the wizard as I mentioned in the below video to kick-start the SCCM 1810 upgrade process
- The installation will take a long time depending on DB size, Specs of your server, the performance of the server, etc.
I have made a video tutorial to explain the upgrade process in details, and I have more information about this in the video posted here.
Features Included in SCCM 1810 Update Pack
This SCCM 1810 update pack includes the following feature. For my test environment, all the 22 available features are enabled. Only one new feature which you should enable (if you want) is SCCM 1810 SMS Provider API.
SMS provider API provides Read-only API interoperability access to WMI over HTTPS. More details available in the Microsoft documentation here. This is a new feature which was never introduced to any of SCCM preview versions yet.
You don’t need to worry about these new feature selections in Configuration Manager Update Wizard as you can these settings after the SCCM 1810 upgrade as well.
Client Update Settings Option
Client Update Settings is another important option in Configuration Manager Update Wizard for SCCM 1810 upgrade. SCCM Client update settings include an update for SCCM client. You can upgrade your clients immediately. Or validate this client in pre-production collection before you upgrade all your SCCM clients.
I would recommend validating the client version with pre-production collection devices before upgrading the SCCM 1810 client package to all your clients directly.
Upgrade without validating
If you select the SCCM client upgrade without validating option, this overwrites your current SCCM client package with the new SCCM client update. All new client installations and client upgrades use this new client update.
Validate in Pre-production collection
If you select “Validate in Pre-production collection” option, then you will get an option to validate the new client update on members of pre-production collection while you keep your production client package intact. Later once you are confident with the new client package, you can overwrite the production package using Client Update Options in the Updates and Servicing node of the SCCM console.
Once you complete the Configuration Manager update wizard, the SCCM 1810 upgrade process will kick start. And the updates and servicing node in SCCM console will show that the update is in installing state.
You can start monitoring SCCM 1810 upgrade from this stage. You can click on a link “Show Status” from related objects. Show status will show you the details about the installation status in monitoring workspace. I would recommend following the below screenshot to see the real-time updates of SCCM upgrade.
You can confirm whether the SCCM 1810 upgrade is completed from monitoring and administration workspace of SCCM console. Once the installation of SCCM 1810 is completed, SCCM console will prompt you to update the console version to SCCM 1810.
You need to make sure all your remote SCCM console installations are upgraded to latest version. This is not very critical if your remote SCCM console is already running with the n-1 version (where n = 1810 in this scenario). But if your remote SCCM console is not n-1 then, you need to make sure your console is updated otherwise you won’t be able to connect to SCCM console.
SCCM 1810 Console Version (Fast Ring) = 5.1810.1075.1300
SCCM 1810 upgrade is completed successfully. So it’s time to concentrate on post installation tasks. Because you might have disabled some of your services and maintenance tasks as part of SCCM CB upgrade checklist which you need to enable back.
More details available in the following link – https://docs.microsoft.com/en-us/sccm/core/servers/manage/checklist-for-installing-update-1810#post-update-checklist
The following are the high-level SCCM post-installation tasks:
- Check the Version of SCCM Client and Site
- Confirm SQL based site-to-site replication is active
- Update Configuration Manager consoles
- Reconfigure database replicas for management points
- Reconfigure any disabled maintenance tasks
- Reenable the Antivirus products
- Update clients
- Third-party extensions
- Update custom boot images and media
Find out the list of SCCM site, console, client versions of SCCM 1810.
- SCCM 1810 site version ==> 5.00.8740.1000
- SCCM 1810 Client version ==> 5.00.8740.1003
- SCCM 1810 Console version ==>5.1810.1075.1300
Why Should I upgrade to 1810 ? What is New with SCCM 1810 -> https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1810
Windows 10 Support as SCCM Client – https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10
Windows 10 ADK Support for SCCM 1810? https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10#windows-10-adk