SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM

SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On-Prem MDM? Microsoft released the next update for SCCM/ConfigMgr vNext (I don’t know whether it would be called SCCM 2016 or something else).

This version of  SCCM ConfigMgr TP is 1510, the version number is directly linked with the Year and month of the release (YYMM = 1510). This update has been successfully installed in my lab environment.

The update 1510 for SCCM/ConfigMgr vNext comes with new capabilities like Windows 10 servicing and Wipe and Retire for on-premises mobile device management.

ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On-Prem MDM

More details in the following TechNet link here.

Patch My PC
SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM
SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM

SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On-Prem MDM?

SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM
SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM

There is a new service in SCCM vNext and that is the CONFIGURATION MANAGER UPDATE Service. This new service helps SCCM to update site servers and components via the new ConfigMgr service model.

Initially, the update was not available in the SCCM console then I bounced back to the SMS_Executive service and after some time the update started appearing in the console. As explained SCCM ConfigMgr vNext TP 3 update 1509 here.

SCCM 2016 vNext TP3-42
SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM

Right-click on the available SCCM vNext (2016 ?) service update from the console and select to run a prerequisite check. This will run the prerequisites for the updates (the latest service update of SCCM) and you can find the status of the monitoring workspace of the console as shown in the screen dumps below.

Adaptiva

If you select the Install Update Pack option, you need to go through the Wizard to upgrade the SCCM site server. However, If you run to select the “Run prerequisite check” option then everything happens in the background:). This time I ran a prerequisite check but it didn’t install the update. When I looked at hman.log and it gave more details as mentioned below.

There are site server reporting WARNING in prereq check. Setup will not continue..
SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM
SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM

  I tried the update again from SCCM console Administration > Cloud Services > Updates and Services – Right clicked on available update 1510 and selected “Retry Installation“. This will you a warning “You are about to retry update pack installation. When you retry installation, the prerequisite warning are ignored”. HMAN.log file also recorded similar kinds of messages as you can see below.

SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM
SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM
Created notification file (DB316362-77FC-46C9-9984-1BAEB20615F4.CMI) for ONFIGURATION_MANAGER_UPDATE
Continue configuration manager update as it is configured to ignore prereq warnings.
INFO: Waiting for current site server to be ready to apply update:DB316362-77FC-46C9-9984-1BAEB20615F4
Waiting for the site server to be ready to apply changes
INFO: Successfully started service CONFIGURATION_MANAGER_UPDATE Successfully updated Configuration manager update DB316362-77FC-46C9-9984-1BAEB20615F4 readiness.
INFO: Waiting for CONFIGURATION_MANAGER_SERVICE to be ready to apply update: DB316362-77FC-46C9-9984-1BAEB20615F4  $<10-15-2015 09:04:25.345-330><thread=2352 (0x930)="">
C:\Program Files\Microsoft Configuration Manager\CMUStaging\\DB316362-77FC-46C9-9984-1BAEB20615F4\SMSSetup\update.map has hash value SHA256:D3356E0295152320D720A17894330D132A63B76D99BDCB03352CFD0947D47A66  $<10-15-2015 09:04:25.397-330><thread=2352 (0x930)="">
Successfully validated file C:\Program Files\Microsoft Configuration Manager\CMUStaging\\DB316362-77FC-46C9-9984-1BAEB20615F4\SMSSetup\update.map  $<10-15-2015 09:04:25.397-330><thread=2352 (0x930)="">
Detected change in update.map for component CONFIGURATION_MANAGER_UPDATE. It will be updated first.  $<10-15-2015 09:04:25.397-330><thread=2352 (0x930)="">
INFO: Stopping service CONFIGURATION_MANAGER_UPDATE  $<10-15-2015 09:04:25.397-330><thread=2352 (0x930)="">
Successfully copied file from C:\Program Files\Microsoft Configuration Manager\CMUStaging\\DB316362-77FC-46C9-9984-1BAEB20615F4\SMSSetup\bin\x64\cmupdate.exe to C:\Program Files\Microsoft Configuration Manager\bin\x64\cmupdate.exe  $<10-15-2015 09:04:27.411-330><thread=2352 (0x930)="">
INFO: Successfully started service CONFIGURATION_MANAGER_UPDATE  $<10-15-2015 09:04:29.714-330><thread=2352 (0x930)="">
Successfully updated Configuration manager update DB316362-77FC-46C9-9984-1BAEB20615F4 readiness.  $<10-15-2015 09:04:29.723-330><thread=2352 (0x930)="">

Once the hierarchy manager (HMAN) initiated the installation of the update pack, we can verify the sitecomp.log for more details. The SCCM Site component takes charge of the installation and upgrade of the site server and all the other SCCM components. What I’ve seen is, it started upgrade using 3 cmd files (climsgs.cmd, provmsgs.cmd and srvmsgs.cmd) located in the folder C:\Windows\System32\smsmsgs.

SCCM 2016 vNext TP3-56
SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM
INFO: 'ACNCM2016.NAIR.COM' is a valid FQDN.  $<10-15-2015 09:20:31.682-330><thread=5864 class="hiddenSpellError" data-mce-bogus="1" pre="" (<span="">0x16E8)>
      Installed file C:\Windows\system32\smsmsgs\srvmsgs.cmd.  $<SMS_SITE_COMPONENT_MANAGER><10-15-2015 09:20:31.712-330><thread=5864 (0x16E8)>
INFO: 'ACNCM2016.NAIR.COM' is a valid FQDN.  $<10-15-2015 09:20:31.732-330><thread=5864 class="hiddenSpellError" data-mce-bogus="1" pre="" (<span="">0x16E8)>
      Installed file C:\Windows\system32\smsmsgs\climsgs.cmd.  $<SMS_SITE_COMPONENT_MANAGER><10-15-2015 09:20:31.754-330><thread=5864 (0x16E8)>
INFO: 'ACNCM2016.NAIR.COM' is a valid FQDN.  $<10-15-2015 09:20:31.774-330><thread=5864 class="hiddenSpellError" data-mce-bogus="1" pre="" (<span="">0x16E8)>
      Installed file C:\Windows\system32\smsmsgs\provmsgs.cmd.  $<SMS_SITE_COMPONENT_MANAGER><10-15-2015 09:20:31.776-330><thread=5864 (0x16E8)>
      All files installed.  $<SMS_SITE_COMPONENT_MANAGER><10-15-2015 09:20:31.777-330><thread=5864 (0x16E8)>
      Starting bootstrap operations...  $<SMS_SITE_COMPONENT_MANAGER><10-15-2015 09:20:31.777-330><thread=5864 (0x16E8)>
SCCM 2016 vNext TP3-60
SCCM ConfigMgr vNext Comes with Windows 10 Servicing Configuration Manager On Prem MDM

SCCM vNext Site component manager thread took more than 20 minutes to complete the entire upgrade process for me. After that, it prompted me to upgrade the SCCM console to the latest version 5.0.8315.1000. SCCM Site server and console version are the same 5.0.8315.1000

Resources

SCCM Related Posts Real World Experiences Of SCCM Admins (anoopcnair.com)

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.