Microsoft has released new version of SCCM Current Branch ie Configuration Manager, version 2006. 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 1810 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
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 2006
For detailed list, you can follow this What’s new in version 2006
This new version includes lots of improvements and new features, important things to be noted down is:
- Install applications from the admin center
- Endpoint analytics data collection enabled by default
- VPN boundary type
- Improved support for Windows Virtual Desktop
- Improvements to CMPivot
- Install and upgrade the client on a metered connection
- Improvements to managing device restarts
- Improvements to available apps via CMG
- Microsoft 365 Apps for enterprise
- Improvements to OS deployment
Once you are ready to install SCCM 2006, see Checklist for installing update 2006.
Let’s Begin the installation
As SCCM Version 2006 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 2006 opt-in script provided by Microsoft which enables you to be on Fast Ring to get the updated right away.
Once download the file EnableEarlyUpdateRing2006.exe, run it to extract EnableEarlyUpdateRing2006.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 2006” under “Updates and Servicing”.
Select “Configuration Manager 2006” and click on Download to initiate the download of update in cab format.
Monitor the download through dmpdownloader.log, update will be download at:
D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\ 68b5a14b-d9e7-4908-b076-7cb7c4453c28
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\Monitor the download through dmpdownloader.log
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 2006”
Run Prerequisite Check
Select “Configuration Manager 2006”, right click and 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 2006”, from the top ribbon select “Install Update Pack”.
This will launch “Configuration Manager Updates Wizard”. Ignore the “Prerequisites warning”, though this is not recommended in production environment. Select Next.
Under Features page, we can select any option under Features included in update pack. select the options you want to select or leave it as default. You can enable this at later stage as well. Select Next.
Under Client Update options, its always better to use option “Validate in pre-production collection” so that you can test new client agent on few systems before rolling out in production. Select Next.
Under License Terms page, check the box “I accept these License Terms and PrivacyStatement. Select Next.
Under Summary page, Select Next to initiate the installation. You can monitor the installation through Monitoring \ Overview \ Updates and Servicing Status and through CMUpdate.log.
Update Pack installation status will show success in cmupdate.log & in console.
Verify the same in SCCM console as well:
Once installation is done, and you try to open the SCCM console, this will ask you to update your console.
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 control version (by clicking on top left of the SCCM ribbon and selection option “About Configuration Manager”.
Console Version: 5.2006.1026.2000
Site version: 5.0.9012.1000
We can see the Production client version is 5.00.8968.1042 and Pre-production client version is 5.00.9012.1018 under Site Configuration > Hierarchy Settings > client Upgrade.
Updated client version (5.00.9012.1018) 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.