This is a SCCM 2002 step by step Upgrade guide using in-console update. Microsoft has released new version of SCCM Current Branch ie Configuration Manager, version 2002. Starting onwards SCCM 1910, Microsoft has given this product a new name which is called Microsoft Endpoint Configuration Manager. This has been made available as in-console update which can be applied to the site on sites which are running version 1806 or later through Configuration Manager service method called Updates and Servicing.
New Baseline version
Configuration manager, version 2002 is also a baseline version. This means that you can install new site using this baseline version.
To summarise this, SCCM 2002 is an in-console update as well as baseline version which has the ability:
- You can install new site using Baseline version.
- You can upgrade to SCCM 2002 from SCCM version 1806 or later through in-console update.
What is In-console Update
- In-console updates provides greater flexibility of upgrading the SCCM Current Branch by getting updates of SCCM within SCCM console only.
- You just need to make sure that “Service connection point site system role” should be installed on SCCM to make sure synchronization schedule pull latest updates for SCCM.
- Once you install in-console update on CAS site, updates are automatically been applied to Primary sites. For secondary sites, you need to initiate it manually.
Supported Baseline Version:
SCCM 1902 & SCCM 2002 is the only supported Baseline versions. You can download the complete source of SCCM 2002 through Volume Licensing Service. If you are doing fresh setup of SCCM, you can use this Baseline version for installation.
What’s new in SCCM 2002
For detailed list, you can follow this What’s new in version 2002
This new version includes lots of improvements and new features, important things to be noted down is:
- Remove a Central Admin Site
- Improvements to CMPivot
- Exclude certain subnets for peer content download
- Client log collection
- Wake up a device from the CAS
- Microsoft Edge management dashboard
- Task sequence as an app model deployment type
- Improvements to Check Readiness task sequence step which provides following prerequisite conditions:
- Architecture of current OS
- Minimum OS version
- Maximum OS version
- Minimum client version
- Language of current OS
- AC power plugged in
- Network adapter is connected and not wireless
- Improvements to task sequence progress to show current step umber, total number of steps and percent completion.
- Integrate with Power BI Report Server
Once you are ready to install SCCM 2002, see Checklist for installing update 2002.
Let’s Begin the installation
As SCCM Version 2002 has recently released, for next couple of weeks it might not be visible under “Updates and Servicing”. You can still get this early update ring using Version 2002 opt-in script provided by Microsoft which enables you to be on Fast Ring to get the updated right away. At this moment you won’t be able to see Configuration Manager 2002 in console.
Once download the file EnableEarlyUpdateRing2002.exe, run it to extract EnableEarlyUpdateRing2002.ps1
Open PowerShell on Site Server with Admin rights and run the script in following format:
Once completed, you will be able to see “Configuration Manager 2002” under “Updates and Servicing”, running of script also starts downloading the update in cab format which can be monitored through dmpdownloader.log and the location of update will be:
D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\ b39bba45-e1f0-4233-971e-bb66eb25359d.cab
Verify Download status
It will initially download in cab format, once downloaded, cab file will be extracted in a folder with same name ie. D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\b39bba45-e1f0-4233-971e-bb66eb25359d
Once cab file is downloaded, it will extract the content with same folder. Original downloaded cab file will be deleted.
Once update is download, you will see the status as “Ready to Install” for “Configuration Manager 2002”
Run Prerequisite Check
Select “Configuration Manager 2002”, from top ribbon select “Run Prerequisite Check”. Verify CMUpdate.log for process initiation and verify c:\ConfigMgrPrereq.log for success or failure.
We got the result “Prerequisite check passed with warnings”, we can continue with installation now, but in production environment make sure to get rid of any warnings that appears which can be checked through Updates and servicing status.
Open SCCM Console, click on Administration Tab, go to Overview > Updates and Servicing. On right Pane you will be able to see now “Configuration Manager 2002”, from the top ribbon select “Install Update Pack”.
This will open “Configuration Manager Updates Wizard“, This will display Prerequisite warnings, click on next to continue.
Under Features included in update pack page, select the options you want to select or leave it as default. You can enable this at later stage as well.
Under Client Update Options page, select “Validate in pre-production collection” so that you can test new client agent on few systems before rolling out in production. Specify a collection where you want to deploy new client.
Under License Terms, Software Assurance expiration date will be shown, click Next.
Finally, completion status will appear stating Summary of update package installation.
You can monitor the installation through Monitoring \ Overview \ Updates and Servicing Status and through CMUpdate.log.
Once installation is done, and you try to open the SCCM console, this will ask you to update your console with the message A new version of the console is available.
This will initiate download of console. Downloading & installation of console can be verified through log file c:\ConfigMgrAdminUISetupVerbose.log
Once completed, you can verify the Site version and Console version (by clicking on top left of the SCCM ribbon and selection option “About Configuration Manager”.
Updated client version (5.00.8968.1012) is currently Pre-production client version which is targeted on collection “Client Pilot Collection” as we selected during installation Phase.
Source of this client version is created in StagingClient under Microsoft Configuration Manager Folder.
Promote Pre-production Client
If you want to promote the Pre-production client in production environment, then navigate to \Monitoring\Overview\Client Status. Right click Pre-production Client Deployment and select Promote Pre-production Client.
Promote Pre-production Client window will appear, click on Promote to replicate the changes in the environment using new SCCM client package.