This post is a complete ConfigMgr 2002 upgrade guide demonstrating the steps to upgrade to SCCM version 2002 on sites running SCCM version 1806 or later.
In other words, you can upgrade to Microsoft Endpoint Configuration Manager (MECM) 2002 if you are running the following versions: SCCM 1806, SCCM 1810, SCCM 1902 or SCCM 1906 or SCCM 1910.
Most importantly, if you are deploying ConfigMgr 2002 on a new site, it is also available as a baseline version. This post summarizes the changes and new features in Configuration Manager version 2002.
Servicing Support
Configuration Manager 2002 is the first current branch release for the year 2020. When you see a new update version, it remains in support for 18 months from its general availability release date.
The Configuration Manager 2002 update will include security and critical updates for the first four months. And for the next 14 months, it will only receive security updates. The below SCCM servicing support pic should give you a clear idea of servicing phases.
New Features in Configuration Manager version 2002
There are several new features in the SCCM 2002 update. Most of the features were already part of technical preview builds. You can read about all the new features of Configuration Manager 2002 here.
For the time being, I will list some of the new features introduced in Update 2002. In a separate post, I will be covering all the new features in detail.
- Remove a central administration site
- Several new management insight rules
- The administration service automatically uses the site’s self-signed certificate.
- Proxy support for Azure Active Directory discovery and group sync
- Token-based authentication for cloud management gateway
- Critical status message ID 11488 shows up when server connection errors to required endpoints occur.
- The Desktop Analytics Connection Health dashboard shows client connection issues.
- CMPivot Improvements
- Exclude certain subnets for peer content download
- Collect SCCM log files from remote client computers.
- Shiny Microsoft Edge management dashboard
- Wake up a device from the central administration site
- Task sequence as an app model deployment type
- Task Sequence and OSD improvements
- Orchestration groups enhancements
- Improvements to BitLocker Management
- Integrate PowerBI report server with Configuration Manager
- Attach error files during feedback
Upgrade Prerequisites Checklist
Here are some of the prerequisites to check before installing Configuration Manager’s current branch 2002 update.
- Update 2002 is available as an in-console update for Configuration Manager’s current branch.
- Yes, there is an SCCM 2002 baseline version also available.
- To apply this update on your sites, ensure you have installed SCCM version 1806 or later.
- If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. First perform the CAS upgrade; later you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site.
- Ensure that you are running a supported operating system and SQL Server version.
- If you’re running SCCM version older than 1806, check the SCCM In-place upgrade paths.
- After you upgrade your site to 2002, you must also update clients to the latest version. In the last section, I will cover how to upgrade client agents in your hierarchy.
Install SCCM 1910 Hotfixes?
A hotfix contains either one individual fix or a bundle (a rollup of fixes). All the hotfixes released for Configuration Manager 1910 will be included in SCCM 2002. So if you see any hotfixes in your console while installing version 2002, you may skip them and directly install the 2002 update.
You can monitor the update download by opening the dmpdownloader.log file. At this point if your SCCM 2002 update gets stuck in a downloading state, here is a post to help you: https://www.prajwaldesai.com/fix-sccm-update-stuck-downloading-state/.
SCCM 2002 Prerequisite Check
Before installing the update 2002, I recommend that you run the SCCM 2002 Prerequisite Check.
- Launch the SCCM console.
- Navigate to Administration > Overview > Updates and Servicing Node.
- Right-click Configuration Manager 2002 update and click Run Prerequisite check.
Open the ConfigMgrPrereq.log file to monitor the prerequisite check process. Look for this line. We have completed the prerequisite checking.
In the console, we see the Configuration Manager 2002 prerequisite check passed successfully. I did not see any errors or warnings, which is a good thing.
Here are some common reasons why the SCCM 2002 prerequisite check might not work. Click the Solution to resolve the issues.
- The site database has a backlog of SQL change tracking data – Solution.
- Configuration Manager Pending System Restart – Solution.
- SQL Server Native Client Version – Solution.
Start ConfigMgr 2002 Upgrade
- Launch the Configuration Manager console.
- Navigate to Administration > Overview > Updates and Servicing Node.
- Right-click Configuration Manager 2002 update and click Install Update Pack.
The Configuration Manager version 2002 includes:
- Configuration Manager site server updates
- Configuration Manager console and client updates
- Fixes for known issues
- New features
Click Next.
You can enable the new features post installing the update. Click Next.
Click Next and finally on Completion page, click Close.
Monitor SCCM 2002 Update Installation Status
To monitor the SCCM 2002 update installation
- In ConfigMgr Console, go to Monitoring node.
- Click Overview > Updates and Servicing Status.
- Select the Configuration Manager 2002 update and click Show Status.
SCCM 2002 Console Upgrade
To get the SCCM 2002 console upgrade box, either refresh the ConfigMgr console or close and reopen it. The new version of console 5.2002.1083.1700 will be installed over the old console version 5.1910.1067.2100. Click OK to proceed with the console upgrade.
Verify Configuration Manager 2002 Upgrade
In the Configuration Manager console, click the drop-down at the top left corner of the console and click About Configuration Manager. This should show the following details.
- Microsoft Endpoint Configuration Manager Version 2002
- Console Version – 5.2002.1083.1700
- Site Version – 5.0.8968.1000
Click OK.
Next, check the primary site properties. You should see version as 5.00.8968.1000 and build number as 8968.
Update Boot Images to Distribution Points
The Configuration Manager 2002 update installation is complete. Now you must update SCCM boot images to all the distribution points in your setup.
In the console, navigate to Software Library > Operating Systems > Boot Images. Right click Boot Image and click Update Distribution Points. Repeat the same for x86 boot image as well.
ConfigMgr 2002 Client Upgrade
As mentioned at the beginning of this post, after you update the site, update client agents to the latest version. I am including this because sometimes administrators skip this step, and as a result, after the upgrade, they do not see the new features. You can upgrade client agents using the client upgrade feature.
To upgrade SCCM client agents to the latest version.
- Go to Administration > Site Configuration > Sites.
- Click the Hierarchy Settings on top ribbon. Select Client Upgrade tab.
- Ensure Upgrade all clients in hierarchy using production client box is selected.
- Specify the number of days within which you want to automatically upgrade client agents.
- Click OK.
Furthermore, you can use the below query to find out the devices without the latest SCCM client version 5.00.8968.1008.
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.8968.1008'Still Need Help?
If you need further assistance on the above article or want to discuss other technical issues, check out some of these options.
