This is in-console Upgrade guide of SCCM Current Branch ie Configuration Manager, version 2103 which is now known as 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 1910 or later through Configuration Manager service method called Updates and Servicing.
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:
Configuration Manager 2103 & 2002 are the only supported Baseline versions. You can download the complete source of SCCM 2103 through Volume Licensing Service. If you are doing fresh setup of SCCM, you can use this Baseline version for installation.
Supported versions
Following are the supported versions of Configuration Manager (including both Baseline and In-console update)
| Version | Availability date | Support end date | Baseline | In-console update |
| 2103 (5.00.9049) | 05-Apr-21 | 05-Oct-22 | Yes | Yes |
| 2010 (5.00.9040) | 30-Nov-20 | 30-May-22 | No | Yes |
| 2006 (5.00.9012) | 11-Aug-20 | 11-Feb-22 | No | Yes |
| 2002 (5.00.8968) | 01-Apr-20 | 01-Oct-21 | Yes | Yes |
| 1910 (5.00.8913) | 29-Nov-19 | 29-May-21 | No | Yes |
Servicing Support for Configuration Manager
Microsoft releases update for Configuration Manager current branch version 3 times a year. Each update is supported for a period of 18 months. Following is the servicing life cycle for Configuration Manager updates.
What’s new in SCCM 2103
For detailed list, you can follow this What’s new in version 2103
This new version includes lots of improvements and new features, important things to be noted down is:
- New prerequisite checks
- Improvements to the collection relationships viewer
- Allow exclusion of organizational units (OU) from Active Directory User Discovery
- Improvements to query preview
- Improvements to collection evaluation view
- Change foreground color for Software Center branding
- Disable application deployments
- Deploy a feature update with a task sequence
- Task sequence error shows more check readiness details
- Improvements to BitLocker management
- Change default maximum run time for software updates
- Improvements to the product lifecycle dashboard
- OneTrace support for jump lists
Once you are ready to install Configuration Manager 2103, see Checklist for installing update 2103 for Configuration Manager.
Installation Steps
Login to SCCM server, open Configuration manager console and navigate to \Administration\Overview\Updates and Servicing, we can see new version available “Configuration Manager 2103” version 5.00.9049.1000.
Right click “Configuration Manager 2103” and click on download.
The status of the update will soon change from available to downloading. It will download 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
Update will be downloaded at:
D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\8f4febb7-f5c4-4d73-893f-29042015727f.cab
Verify Download status
Once cab file is downloaded, it will be extracted in a folder with same name ie. D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\8f4febb7-f5c4-4d73-893f-29042015727f
Once content is extracted within same folder. Original downloaded cab file will be deleted.
Monitor the download through dmpdownloader.log
Once update is download, you will see the status as “Ready to Install” for “Configuration Manager 2103”
Run Prerequisite Check
Select “Configuration Manager 2103”, right click and select “Run Prerequisite Check”. Verify CMUpdate.log for process initiation and verify c:\ConfigMgrPrereq.log for success or failure.
You will see following in CMUpdate.log:
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.
Initiate Install Update Pack
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 2103”, from the top ribbon select “Install Update Pack”.
This will launch Configuration Manager Update Wizard, under General page check the box Ignore any prerequisite check warnings and install this update regardless of missing requirements. Once again, don’t do it in production environment. Click Next.
Under Features included in update pack page, select the options you want to enable or leave it as default. You can enable this at later stage as well. Click Next
Under Client Update Settings page, select Validate in pre-production collection and select the collection used for this so that you can test new client agent on few systems before rolling out in production. Click Next.
Under License Terms page, check the box “I accept these License Terms and Privacy Statement”. Click Next.
You will get completion status, click on Close to exit.
Under SCCM Console, you will see the installation status showing as Installing.
You can monitor the installation through Monitoring \ Overview \ Updates and Servicing Status and through CMUpdate.log.
Navigate to \Monitoring\Overview\Updates and Servicing Status, select Configuration Manager 2103, right click and select Show Status.
Update Pack Installation Status will show the installation progress.
After waiting for some time, Update Pack installation status will show success in cmupdate.log with message:
Successfully reported ConfigMgr update status
Once installation is done, status will be shown as Installed under \Monitoring\Overview\Updates and Servicing Status.
When trying to open the SCCM console, it will be asked to to update your console with version 5.2103.1093.1800. Click on Ok to initiate download and install.
Download will happen at following location:
C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\{105904E1-B214-4634-96EF-C22D8B8B8D12}
Adminconsole.msi will be visible which will be executed automatically.
Downloading & installation of console can be verified through log file:
c:\ConfigMgrAdminUISetup.log
c:\ConfigMgrAdminUISetupVerbose.log
Once completed you can verify the site version and control version (by clicking on top left of the SCCM ribbon and selection option “About Configuration Manager”.
Console Version: 5.2103.1059.1800
Site Version: 5.0.9049.1000
Client Update
We can see the Production client version is 5.00.9040.1015 and Pre-production client version is 5.00.9049.1010 under \Administration\Overview\Site Configuration\Sites.
Updated client version (5.00.9049.1010) 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.
Useful links:
https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/whats-new-in-version-2103
https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/current-branch-versions-supported
https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/updates#version-details
Leave a Reply