Microsoft has released new version of in-console update ie 1910 for SCCM Current Branch. You can apply this updated on sites that run version 1806 or later.
As version 1910 is an in-console
update, not a baseline version:
You can upgrade to 1910 only from SCCM version 1806,1810,1902 or 1906.
If you have to do a fresh setup of SCCM. Then first you need to install SCCM using Baseline version 1902, once installed – 1910 can be installed as In-Console update directly, you can skip 1906. Here is the link for SCCM 1902 step by step upgrade guide.
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 is the only supported Baseline version as previous Baseline version 1802 support has already been ended. You can download the complete source of SCCM 1902 through Volume Licensing Service. If you are doing fresh setup of SCCM, you can use this Baseline version for installation.
This new version includes heaps of
features, important things to be noted down is:
Configuration Manager is now part of Microsoft Endpoint Manager. Configuration Manager Intune Desktop Analytics Autopilot Other features in the Device Management Admin Console
Deploy Microsoft Edge, version 77 and later
Search the task sequence editor
Copy and paste task sequence conditions
Task Sequence download on demand over the internet
Import a single index of an OS Upgrade package
Improved language support in task sequence
Office 365 ProPlus Pilot and Health Dashboard
Checklist for SCCM 1910 can be followed through this link
Let’s Begin the installation
As SCCM Version 1910 has recently
released, for next couple of weeks it might not be visible under “Updates and
Servicing”. You can still get this update using Version 1910 opt-in
script provided by Microsoft which enables you to be on Fast Ring to get
the updated right away.
Once download (in exe format), run
it to extract enableearlyupdatering1910.ps1
Open PowerShell on Site Server with Admin rights and run the script in following format: enableearlyupdatering1910.ps1 <SiteServerName>
Once completed, you will be able to see “Configuration Manager 1910” under “Updates and Servicing”, running of script also starts executing the update which can be monitored through dmpdownloader.log and the location of update will be: D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\6630e282-aa3f-4921-a65d-4cf493c42066
Verify Download status
It will initially download in cab format, ie 6630e282-aa3f-4921-a65d-4cf493c42066.cab
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 1910”
Run Prerequisite Check
Select “configuration Manager 1910” , 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 1910”, from the top ribbon select “Install Update Pack”. This will initiate “Configuration Manager Updates Wizard”. Ignore the Prerequisite warnings and select next.
Under “Features included in update pack”, click next. You can enable this feature anytime later also.
Next screen shows Client Update Settings, 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.
In next page, accept the terms.
Next page shows, wizard completely successfully. This will take some time to update SCCM.
Select “Configuration Manager 1910” and click on “Show Status”
This will open “Update Pack Installation Status”, you can monitor the whole installation progress through this page.
Installation can be verified through cmupdate.log as well.
Once installation is done, and you try to open the SCCM console, this will ask you to update your console. Click ok to continue. New console version is 5.1910.1067.1400. which will uninstall old console version 5.1906.1096.1600
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”.
This can be verified by navigating to Administration \ Site Configuration \ Sites, selecting the site on right Pane and selecting Hierarchy Settings on Ribbon, click on Client Upgrade tab.
Updated client version (5.00.8913.1008) 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 / staging client version to Production client version, you need to navigate to Monitoring \ Client Status \ Pre-production Client Deployment, right click and select Promote Pre-production Client