Microsoft has released new version of in-console update ie 1810 for SCCM Current Branch. You can apply this updated on sites that run version 1710, 1802 or 1806.
As version 1810 is an in-console update, not a baseline version:
- You can upgrade to 1810 only from SCCM version 1710,1802 or 1806.
- If you have to do a fresh setup of SCCM. Then first you need to install SCCM using Baseline version 1802, once installed – 1810 can be installed as In-Console update. Here is the link if you want to install Baseline version SCCM 1802: https://www.manishbangia.com/2018/03/sccm-1802-step-by-step-upgrade-guide/
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.
SCCM Supported Versions
Some updates for Configuration Manager are available as both an in-console update version for existing infrastructure, and as a new baseline version.
The following supported versions of Configuration Manager are currently available as a baseline, an update, or both:
|Version||Availability date||Support end date||Baseline||In-console update|
|Nov 27,2018||May 27, 2020||No||Yes|
|July 31, 2018||January 31, 2020||No||Yes|
|March 22, 2018||September 22, 2019||Yes||Yes|
|November 20, 2017||May 20, 2019||No||Yes|
Note: Starting from SCCM Version 1710, supported has been change to 18 months as previously SCCM current branch support cycle was 12 months only.
Supported Baseline Version:
SCCM 1802 is the only supported Baseline version as previous Baseline version 1702 support has already been ended on March 27, 2018. SCCM 2012 can be upgraded using this version of SCCM as you can download the complete source of SCCM 1802 through Volume Licensing Service. This also means that if you have to do the fresh setup of SCCM, you can use this Baseline version for installation.
What’s new in SCCM 1810
For detailed list, you can follow this link
One of the feature related to OS support is that now it support Windows Server 2019.
Checklist for SCCM 1810 can be followed through this link
Let’s Begin the installation
As SCCM Version 1810 has recently released, for next couple of weeks it might not be visible under “Updates and Servicing”. You can still get this update using a PowerShell script provided by Microsoft which enables you to be on Fast Ring to get the updated right away.
You can download the script (in form of exe) from here.
Once download you need to extract it in a folder which contains EnableFastUpdateRing1810.ps1
Run this script on Site Server with Admin rights in PowerShell.
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 1810”, right click and select “download”.
Update will be download as cab file under following location (D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\a2233cd3-586a-4dfe-affc-e200e55f61bb) and can be verified using log file dmpdownloader.log
Verify Downloading Status
Downloading status can be verified through Monitoring \ Overview \ Updates and Servicing Status.
Once downloaded it will extract the content with same name folder as cab file. Original Cab file will be deleted then. Following can be verified in the log dmpdownloader.log showing details:
Run Prerequisite Check
Once update is downloaded, status will change to “Ready to install”, right click “configuration Manager 1810” on console 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.
Right click “Configuration manager 1810” and click on install.
Select next, select the options you want to select or leave it as default. You can enable this at later stage as well.
Next screen shows 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 and specify your Software Assurance expiration date.
Click next to complete.
You can monitor the installation through Monitoring \ Overview \ Updates and Servicing Status and
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”.
Updated client version (5.00.8740.1004) 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: