Microsoft has released new version of SCCM Current Branch ie Configuration Manager, version 2010. 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 1906 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 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.
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|
|2010 (5.00.9040)||November 30, 2020||May 30, 2022||No||Yes|
|2006 (5.00.9012)||August 11, 2020||February 11, 2022||No||Yes|
|2002 (5.00.8968)||April 1, 2020||October 1, 2021||Yes||Yes|
|1910 (5.00.8913)||November 29, 2019||May 29, 2021||No||Yes|
|1906 (5.00.8853)||July 26, 2019||January 26, 2021||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 2010
For detailed list, you can follow this What’s new in version 2010
This new version includes lots of improvements and new features, important things to be noted down is:
- Microsoft Endpoint Manager tenant attach
- Troubleshooting portal lists a user’s devices based on usage
- Enhancements to applications in Microsoft Endpoint Manager admin center
- Cloud-attached management
- Cloud management gateway with virtual machine scale set for CSP
- Disable Azure AD authentication for onboarded tenants
- Desktop Analytics
- Support for new Windows 10 diagnostic data levels
- Support for Windows 10 Enterprise LTSC 2019
- Site infrastructure
- Monitor scenario health
- Improvements to the administration service
- Client management
- Wake machine at deployment deadline using peer clients on the same remote subnet
- Improved Windows Server restart experience for non-administrator accounts
- Collection query preview
- Collection evaluation view
- View collection relationships
- Application management
- Improvements to available apps via CMG
- OS deployment
- Deploy an OS over CMG using bootable media
- Deploy a task sequence deployment type to a user collection
- Manage task sequence size
- Analyze SetupDiag errors for feature updates
- Improvements to task sequence performance settings
- Software updates
- Enable user proxy for software update scans
- Notifications for devices no longer receiving updates
- Immediate distribution point fallback for clients downloading software update delta content
- Configuration Manager console
- Improvements to in-console notifications
- Improvements to the Configuration Manager console
- Content management
- Improvements to client data sources dashboard
- Improvements to the content library cleanup tool
- Update PowerShell help
- Support for PowerShell version 7
- Improvements to cloud management gateway cmdlets
Once you are ready to install SCCM 2010, see Checklist for installing update 2010.
As SCCM Version 2010 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 2010 opt-in script provided by Microsoft which enables you to be on Fast Ring to get the updated right away.
Once download the file EnableEarlyUpdateRing2010.exe, run it to extract enableearlyupdatering2010.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 2010” under “Updates and Servicing”.
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\d5054056-f41c-4e61-90a7-4f135b76f806.cab
Verify Download status
Monitor the download through dmpdownloader.log
Once cab file is downloaded, it will be extracted in a folder with same name ie. D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\d5054056-f41c-4e61-90a7-4f135b76f806
Once content is extracted within 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 2010”
Run Prerequisite Check
Select “Configuration Manager 2010”, 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.
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 2010”, 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 2010, 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 & in console.
Once installation is done, and you try to open the SCCM console, this will ask you to update your console with version 5.2010.1093.1800. Click on Ok to initiate download and install.
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.2010.1093.1800
Site Version: 5.0.9040.1000
We can see the Production client version is 5.00.9012.1018 and Pre-production client version is 5.00.9040.1015 under Site Configuration > Hierarchy Settings > client Upgrade.
Updated client version (5.00.9040.1015) 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.