Microsoft has released the first SCCM version for 2019. Microsoft still uses the same standard naming versions. You can begin upgrading your SCCM Current Branch environment to the latest 1902 release. If you want to install the latest updates, this post is a complete step-by-step SCCM 1902 upgrade guide.
If you’re looking for a comprehensive SCCM installation guide, see our blog series which covers it all. You won’t be able to install SCCM 1902 if you are running SCCM 2012, but 1902 this is the new baseline version. This means that if you’re downloading the source from Volume Licensing, 1902 will be the starting version of your new SCCM site.
To install SCCM 1902 as an update, you must have installed at least SCCM 1710, SCCM 1802
Keeping your infrastructure up to date is essential and recommended. You will benefit from the new features and fixes, which some of them can apply to your environment. It’s easier than ever to upgrade since Microsoft has implemented the servicing model directly from the console.
SCCM 1902 New Features and Fixes
SCCM 1902 includes lots of new features and enhancements in the site infrastructure, content management, client management, co-management, application management, operating system deployment, software updates, reporting, and configuration manager console.
You can consult the What’s new in version 1902 of System Center Configuration Manager Technet article for a full list of changes.
Here’s our list of favourite features:
- New Client health dashboard
- Stop cloud service when it exceeds
- Add cloud management gateway to boundary groups
- Distribution point maintenance mode
firstscreen only during remote control
- Improvements to application approvals via email
- Progress status during
in-placeupgrade task sequence
- Import a single index of an OS image
- Optimized image servicing
- Replace toast notifications with
- Office products on lifecycle dashboard
- View recently connected consoles
- In-console documentation dashboard
Support for SCCM Current Branch Versions
Ensure to apply this update before you fall into an unsupported SCCM version. Read about the support end date of the prior version of the following Technet article.
Windows and SQL Support
Before installing, make sure that you are running a supported Operating System and SQL version. Older SCCM version was giving a warning during Prerequisite check but 1902 is giving an error which prevents the installation from continuing.
SCCM 1902 supports only Windows 2012+ and SQL 2012 SP3+.
Before you Begin SCCM 1902 Upgrade Guide
Downloading and installing this update is done entirely from the console. There’s no download link, the update will appear on your console once the Service Connection Point is synchronized.
If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. After the CAS upgrade, you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site. Until all sites in your hierarchy are upgraded, your hierarchy operates in a mixed version mode.
Before applying this update, we strongly recommend that you go through the upgrade checklist provided on Technet. Most importantly, initiate a site backup before you upgrade.
In this post, we will update a stand-alone primary site server, consoles, and clients. Before installing, check if your site is ready for the update:
- Open the SCCM console
- Go to Administration \ Updates and Servicing
- In the State column, ensure that the update Configuration Manager
1902 is Available
- If it’s not available, right-click Updates and Servicing and select Check for Updates
WarningThe SCCM 1902 update is not yet available for everyone. If you need it right away you can run the Fast-Ring script and the update will show up.
- If the update is not downloading, click on the button Download on the upper node. The update state will change to Downloading
- You can follow the download in Dmpdownloader.log or by going to Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status
- The process will first download .CAB file and will extract the file in the EasyPayload folder in your SCCM installation directory.
- It can take up to 15 minutes to extract all files.
SCCM 1902 Upgrade Guide
Step 1 | SCCM 1902 Prerequisite Check
Before launching the update, we recommend launching the prerequisite check first. To see the prerequisite checklist, see the Microsoft Documentation
- Open the SCCM console
- Go to Administration \ Updates and Servicing
- Right-click the Configuration Manager 1902 update and select Run prerequisite check
- Nothing will happen, the prerequisite check runs in the background and all menu are unavailable during the check
- One way to see progress is by viewing C:\ConfigMgrPrereq.log
- You can also monitor prerequisite check by going to Monitoring / Update and Servicing Status, right-click your Update Name and select Show Status
- When completed the State column will show Prerequisite check passed
TLS 1.2 SupportYou might get a warning for TLS 1.2 support. Make sure to check ConfigMgrPrereq.log and look why the error occurs. In our situation, a higher version of SQL Server Native Client was required.
- Right-click the Configuration Manager 1902update and select Install Update Pack
Step 2 | Launching the SCCM 1902 Update
We are now ready to launch the SCCM 1902 update. At this point, plan about 45 minutes to install the update.
- On the General tab, click Next
- On the Features tab, checkboxes on the features you want to enable during the update
- Don’t worry, if you don’t select one of the features now and want to enable it later, you’ll be able to so by using the console Administration \ Updates and Servicing \ Features
- In the Client Update Options, select the desired option for your client update
- This option allows updating only clients member of a specific collection. Refer to our pre-production client deployment post for more details
- On the License Terms tab, accept the license terms and click Next
- On the Summary tab, review your choices, click Next and close the wizard on the Completion tab
The whole process took a minute but the installation begins on the back end.
- During installation, the State column changes to Installing
- We suggest you monitor the progress, by navigating to Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status
Unfortunately, the status is not updated in real time. Use the Refresh button to update.
- Open the SCCM log SCCM Installation Directory\Logs\CMUpdate.log with CMTrace
Important InfoWe’ve done numerous SCCM upgrades. Some installation start a couple of minutes after you complete the wizard but we’ve seen some installation starts after a 10 minutes delay. Do not reboot or restart any services during this period or your update can be stuck in “Prerequisite check passed” status. There’s actually no officially documented methods by Microsoft to fix that. Patience is the key!
- When completed, you’ll notice the message There are no pending update package to be processed in the log file
- Monitoring / Updates and Servicing Status, right-click your Update Name and select Show Status, the last step will be Installation Succeeded
- Refresh the Updates and Servicing node in Administration, the State column will be Installed
Updating the Outdated Consoles
As a previous update, the console has an auto-update feature. At the console opening, if you are not running the latest version, you will receive a warning and the update will start automatically.
- Since all updates operations were initiated from the console, we didn’t close it during the process. We received a warning message when clicking certain objects. You will have the same message when opening a new console
- Click OK, console restart and update will start automatically
- Wait for the process to complete. You can follow the progress in C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log. Once completed, the console will open and you’ll be running the latest version
After setup is completed, verify the build number of the console. If the console upgrade was successful, the build number will be 8740 and the version is now Version 1902.
Beginning with 1802, this is a new version nomenclature for the console. The console will no longer include the main build number (8740). The last 2 numbers refer to the admin console build number. For example, in the Configuration Manager version 1902, the initial site version is 5.0.8790.1000, and the initial console version is 5.1902.1085.1500. The build (1075) and revision (1300) numbers may change with future hotfixes to the 1902 release.
- Go to Administration \ Site Configuration \ Sites
- Right-click your site and select Properties
- Verify the Version and Build number
SCCM 1902 Clients
The client version will be updated to 5.00.8790.1005 (after updating, see section below)
SCCM 1902 Client Package distribution
You’ll see that the 2 client packages are updated:
- Navigate to Software Library \ Application Management \ Packages
- Check if the update is successful, otherwise, select both packages and initiate a Distribute Content to your distribution points
Boot images will automatically update during setup. See our post on upgrade consideration in a large environment to avoid this if you have multiple distribution points.
- Go to Software Library / Operating Systems / Boot Images
- Select your boot image and check the last Content Status date. It should match your setup date
Updating the Clients
Our preferred way to update our clients is by using the Client Upgrade feature: (You can refer to our complete post documenting this feature)
- Open the SCCM Console
- Go to Administration / Site Configuration / Sites
- Click the Hierarchy Settings in the top ribbon
- Select Client Upgrade tab
- The Upgrade client automatically when the new client update is available to the checkbox is enabled
- Review your time frame and adjust it to your needs
Monitor SCCM Client Version Number
SCCM Reports Client Version
You can see our SCCM Client version reports to give detailed information about every client version in your environment. It’s the easiest way to track your client updates.
In conclusion, you can create a collection that targets clients without the latest client version because is very useful when it comes to monitoring a non-compliant client.
Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contains this collection)
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.8790.1005'
Share this Post
Pingback: Step-by-step SCCM 2002 Upgrade Guide
i hope you can help me.
I would like Update the System Center from CB1802 to CB1920.
In one fell swoop, the update is not possible.
I must update on 2 steps
1 – Update from CB1802 to CB1902
2- Update from CB1902 to CB1910
I hope to receive feedback and I am grateful for any input
Does 1906 fixes the hanning: “Install Software Updates” issue during a OSD?
I am upgrading from 1810 to 1902
ERROR:DropStateMessage Exception: Object reference not set to an instance of an object.
INFO:Successfully imported console content but still not showing on SCCM Console.
Did anyone faced this issue ?
I am able to resolve this issue by using different copy of serviceconnection tool. But now I am unable to import update binaries in SCCM Console. It says “INFO:Successfully imported console content.” but nothing is visible on SCCM console.
Why does the prerequisite check get greyed out after the first time you attempt an installation? I got the TLS 1.2 warning and upgraded the native SQL client. However, there is no option to rerun a prerequisite check, it’s greyed out. I can retry installation, but it says that the Prereq Warnings will be ignored. WTF was the development team thinking? There’s no way to rerun a just prerequisite check if you attempted an installation with a prerequisite check halting the installation?
Updateted from 1802 to 1902 two weeks ago, without any issues. Was a bit nervous, as always, but your guide gave me confidence for making the update!
Thanx a lot for sharing your knowledge!
Trying manual upgrade 2012R2 to 1902 as I do not find any other versions prior to 1902. However, I get a prerequisite check error Link ID 722800. “SELECT * FROM Quar_QuarantineCIs” returned zero results.
I have ran the update to 1902 as per above and all looked to go well, however i am now unable to run OSD as it is now failing on downloading the image with the dreaded 0xc0000001 a required device isn’t connected or can’t be accessed error.
Nothing else on the environment has changed, Any ideas on where is best to look hints on why this is failing?
Is this with PXE? does the same happen with USB boot or in-place upgrade?
Unfortunately, i have restarted the server during the upgrade process and now the configuration manager 1902 installation is stuck on extract update package. i’ve left it for two days and it doesn’t proceed to anywhere. How do i resolve this issue and restart the installation again. Appreciate your advice. Thanks.
I have upgraded sccm 1809 to 1902 , after that i got many errors in server “LocationServices” The log says “Failed to send management point list Location Request Message” to “my sccm server name”
“MP_Status” The log says “Mp Status: processing event: SMS_RemoteClient_ManagementPointCertificate_CrossVerificationFailure, for machine: “client machines”
when i cross-checked all of the client machines the client “LocationServices” log says “Failed to validate the certificate ” from management point ” my sccm server name”. and “Failed to retrieve MP certificate authentication information over http.”
“CertificateMaintenance” in client machine the log says “Failed to verify signature of message received from MP using name ‘my sccm server name’
My ADK version is 10.1.17763.1 OSD and Patching not working on clients.
I have not changed anything just upgraded and rebooted.
Please suggest me to fix this issue.
Hi, I’m prepping to upgrade configmgr from 1806 to 1902. As far as ADK goes, I have 10.1.17134.1 (Windows ADK for Windows 10 v1803) installed. For Windows 10, we currently have 1709 in production. We are building out new sequence for 1809.
Should I install the latest ADK? And will I still b able to deploy and manage 1709 if I upgrade?
You uninstall the old ADK and install the new one always before SCCM upgrade because it will auto generate the boot images based on the current ADK version.
My workflow is:
1. Uninstall the old ADK and Windows PE add-on for the ADK and restart computer
2. Install the new ADK and Windows PE add-on for the ADK and restart computer.
3. Upgrade SCCM.
If you’re upgrading from 1710 and 17xx ADK the new thing since version 1809 is that you need to install ADK and Windows PE add-on because Windows PE is not anymore included in ADK. You will find this info on ADK download page. If you skip Windows PE add-on the new boot images will not be created.
We are currently running v1710 and will be upgrading to 1902. As it has been a while since we have done an upgrade, correct me if i’m wrong but do we uninstall ADK/MDT After or Before the 1902 upgrade
1902 still isn’t in VLSC, but the evaluation center has it listed now:
Because its not there. I think the latest SCCM version in VLP is 1804 or 1802. Not every version is uploaded to VLP.
It was already fixed in 1810 and the latest CU and KB4490575
God bless you for posting this. One question. I don’t see 1902 in the Volume Licensing portal. Am i looking in the right place?
Thank you, Per!
The checklist on Technet says “Each site server in the hierarchy must run the same version of Configuration Manager before you can start the installation of update 1902. To update to 1902, you must use version 1802, 1806, or 1810” so I guess that’s a third opinion.
Hello, what is the source of your information that says it is possible to upgrade to 1902 from 1710? I was just told by our Microsoft PFE that we will have to upgrade to 1810 first before going to 1902.
Do we have to update windows ADK and MDT ? How proceed ? ADK, MDT and SCCM.
Thanks for your informations.
I can’t find the 1902 Baseline Version in the Volume Licensing Portal. Do you know when the Baseline Version will be released in the Volume Licensing Portal`?
Dose 1902 can show us config drift information? Any plan fir Power BI integration?
Any promises about instant success or riches are sham.
When commence talking for about brand awareness are generally wasting your hard.
Alternatively, figure out the best way to produce realize. http://familie-huettler.de/link.php?link=austudio.global
Does 1902 fixes the hanning: “Install Software Updates” issue during a OSD?