Upgrade to Windows 10 2004 Using SCCM | ConfigMgr | Servicing

3
Upgrade to Windows 10 2004 Using SCCM

Let’s learn how to upgrade to Windows 10 2004 using SCCM. You can use Windows 10 servicing plans to keep Windows 10 up to date and secured. Windows 10 2004 is the latest version of Windows 10.

You can manage Windows as a service using ConfigMgr (A.K.A Configuration Manager). You can learn how to upgrade to Windows 10 2004 version using ConfigMgr. Windows 10 May 2020 Update is another name for Windows 10 2004.

Related post How to Enable Windows 10 servicing using SCCM | ConfigMgr | WSUS

TL;DR

Windows 10 Servicing

Windows 10 servicing is the modern way of upgrading Windows 10 to the latest version without using the in-place upgrade (IPU) Task Sequence.

You can create service plans to form deployment rings and ensure that Windows 10 systems are kept up-to-date when new builds are released. You can also view alerts when Windows 10 clients are near the end of support for their Semi-Annual Channel build.

Prerequisites

  • Windows 10 Software Update Management. Windows Update for Business should not be enabled.
  • Online Service Connection Point
  • Enable Specify thread priority for feature updates from Client settings (1902 or later).
  • Enable Dynamic Update for feature updates from Client settings (1906 or later).
Upgrade to Windows 10 2004 Using SCCM
Upgrade to Windows 10 2004 Using SCCM
  • From the Products make you have enabled the following product.
    • Windows 10, version 1903 and later 
Upgrade to Windows 10 2004 Using SCCM
Upgrade to Windows 10 2004 Using SCCM
  • Click on UPGRADE and enable the checkmark for upgrade option from the Classification tab from Software Update Point Component Properties.
Altaro Office 365 Backup
Advertisement Altaro Office 365 Backup
Upgrade to Windows 10 2004 Using SCCM
Upgrade to Windows 10 2004 Using SCCM

NOTE! – Make sure all the prerequisites mentioned the following post is in place- Enable Windows 10 servicing using SCCM.

Search for Windows 10 2004 Servicing

  • Navigate to \Software Library\Overview\Windows 10 Servicing\All Windows 10 Updates
  • Search with Product and Date Released:
    • Product Windows 10 version 1903 and Later.
    • Date Released is On or AfterLast 28 Days.
  • Click on the Search button.
  • Click on the available update named – Feature update to Windows 10 (business editions), version 2004, en-us x64.
    • The “required” column shows 1.

NOTE! – Select the other languages if you want to deploy non-English languages.

Upgrade to Windows 10 2004 Using SCCM
Upgrade to Windows 10 2004 Using SCCM

Download Windows 10 2004 Servicing Package

  • Right-click on Feature update to Windows 10 (business editions), version 2004, en-us x64 and Click on Download.
Download Windows 10 2004 Servicing Package
Download Windows 10 2004 Servicing Package
  • Select Create a new deployment package.
    • Enter the Name – Download Windows 10 2004 Servicing Package.
  • Enter the package name source – UNC path to store the source file.
Create a new deployment package SCCM - ConfigMgr for Windows 10 2004
Create a new deployment package SCCM – ConfigMgr for Windows 10 2004
  • Click on Add and select Distribution Point.
  • Select the Distribution Point – Click on the DP Name.
  • Click OK and Next.
Add and select Distribution Point - Upgrade to Windows 10 2004 Using SCCM
Add and select Distribution PointUpgrade to Windows 10 2004 Using SCCM
  • Select the option “Automatically Download Content when packages are assigned to distribution points.”
Upgrade to Windows 10 2004 Using SCCM
Upgrade to Windows 10 2004 Using SCCM – Automatically distribute the content
  • Download Source files from the Internet.
    • Download Software Updates from the internet.
  • Click Next continue
Upgrade to Windows 10 2004 Using SCCM - Download Software update from the internet
Upgrade to Windows 10 2004 Using ConfigMgr – Download Software update from the internet
  • Specify the update languages for products.
    • Select the different languages by clicking on the Edit button.
  • Click Next.
Specify the update languages for products - Upgrade to Windows 10 2004 Using ConfigMgr
Specify the update languages for products – Upgrade to Windows 10 2004 Using ConfigMgr
  • Click on Next on Summary page.
Package:
The software updates will be placed in a new package:
• Download Windows 10 2004 Servicing Package
Content (1):
• CMMEMCM.MEMCM.COM
Distribution Settings
• Priority: Medium
• Enable for on-demand distribution: Disabled
• Prestaged distribution point settings: Automatically download content when packages are assigned to distribution points
Software updates that will be downloaded from the internet
Feature update to Windows 10 (business editions), version 2004, en-us x64
Windows Update Language Selection:
English
Office 365 Client Update Language Selection:
English (United States)
Upgrade to Windows 10 2004 Using ConfigMgr
Upgrade to Windows 10 2004 Using ConfigMgr
  • Download the following files completed –
    • 19041.264.200511-0456.vb_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_en-us.esd
    • WindowsUpdateBox.exe
Upgrade to Windows 10 2004 Using ConfigMgr
Upgrade to Windows 10 2004 Using ConfigMgr
  • Download Column confirms the serving update is downloaded.
Upgrade to Windows 10 2004 Using ConfigMgr
Upgrade to Windows 10 2004 Using ConfigMgr

Deploy Windows 10 Servicing Package

You have already downloaded Windows 10 2004 servicing package. Now, let’s deploy the Windows 10 servicing update to test collection.

  • Navigate to \Software Library\Overview\Windows 10 Servicing\All Windows 10 Updates.
  • Right-Click on a Feature update to Windows 10 (business editions), version 2004, en-us x64 and click on Deploy.
Deploy Windows 10 2004 Servicing Package
Deploy Windows 10 2004 Servicing Package
  • Enter the Name of Windows 10 Servicing Deployment
    • Windows 10 2004 Servicing
Windows 10 2004 Servicing Deployment using ConfigMgr SCCM
Windows 10 2004 Servicing Deployment using ConfigMgr SCCM
  • Select Type of Deployment – Required.
  • Select State Message Level – Only Success and Messages.
Select Type of Deployment - Required
Select Type of Deployment – Required
  • Select Schedule Evaluation – Client Local Time.
  • Select Software Available Time – As Soon As Possible.
  • Select Installation Deadline – Specific Time – Date and TIme.
Schedule Details for Windows 10 Servicing Deployment using SCCM ConfigMgr
Schedule Details for Windows 10 Servicing Deployment using SCCM ConfigMgr
  • Select all the default values for Windows 10 Servicing
    • Deadline Behavior.
    • Device Restart Behavior.
    • Write Filter handling for Windows Embedded Devices.
    • Software Updates Deployment re-evaluation behavior upon restart.
Software Updates Deployment re-evaluation behavior upon restart.
Software Updates Deployment re-evaluation behavior upon restart.
  • Select the default alert configuration for Windows 10 servicing deployment.
alert configuration for Windows 10 servicing deployment
alert configuration for Windows 10 servicing deployment

Select the following options for Windows 10 2004 servicing deployment using SCCM (a.k.a ConfigMgr).

  • Deployment Options:
    • Do not install software updates
  • Deployment Options
    • Download and Install software updates from the distribution points site default boundary group
Do not install software updates for Windows 10 Servicing
Do not install software updates

Summary – Deployment

Updates Targeted:
• Feature update to Windows 10 (business editions), version 2004, en-us x64 3012973(Article ID)
General:
• Deployment Name: Windows 10 2004 Servicing
• Description: Windows 10 2004 Servicing
• Collection: HTMD Collection
Deployment Settings:
• Send wake-up packets: No
• Verbosity Level: Only success and error messages
Scheduling:
• Deployment schedules will be based on: Client local time
• Available to target computers: 6/4/2020 10:13:00 PM
• Deadline for software update installation: 6/8/2020 9:55:00 PM
• Delayed enforcement on deployment: No
User Experience:
• User Notifications: Display in Software Center and show all notifications
• Install software updates outside the maintenance window when deadline is reached: No
• Restart system outside the maintenance window when deadline is reached: Suppressed
• If a restart is required it will be: Allowed
• Commit changes at deadline or during a maintenance window (requires restarts): Yes
• If any update in this deployment requires a system restart, run updates deployment evaluation cycle after restart: No
Alerts:
• On software update installation error generate a Window Event: No
• Disable Window Event while software updates install: No
Download Settings:
• Computers can retrieve content from remote distribution points: No
• Download and install software updates from the fallback content source location: Yes
  • Click on the Next button.
  • Click on the Close button to complete the deployment process.
Close button to complete the deployment process
Close button to complete the deployment process – Upgrade to Windows 10 2004 Using SCCM
  • Confirm the deployment for Windows 10 servicing using Configuration Manager.
deployment for Windows 10 servicing using Configuration Manager.
Confirm the deployment for Windows 10 servicing using Configuration Manager.

End-User Experience Windows 10

  • Manually Sync policies using ConfigMgr applet from Control Panel.
Upgrade to Windows 10 2004 Using SCCM
Upgrade to Windows 10 2004 Using SCCM
  • Launch Software Center and click on Updates
  • Select the available update for Windows 10 2004.
  • Click on Install button to start the installation.
Upgrade to Windows 10 2004 Using SCCM | ConfigMgr | Servicing 1
Upgrade to Windows 10 2004 Using ConfigMgr
  • User Confirmation of Windows 10 upgrade.
  • Click on Install again.
Upgrade to Windows 10 2004 Using SCCM
Upgrade to Windows 10 2004 Using SCCM

Log Files for Windows 10 Servicing

The following are the important SCCM and Windows log files that are associated with Windows 10 servicing.

  • C:\Windows\Logs\CBS\CBS.log
CBS Appl: detectParent: parent found: Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~10.0.18362.836, state: Installed
CBS TI: started and RebootPending volatile key indicates that a reboot is pending, skip startup processing.
CBS TI: Startup Processing completes, release startup processing lock.
CBS WU creates the package, AppID:UpdateOrchestrator, UpdateID:{84858A33-7E49-4280-9CEB-67882C26B267}, revision: 200
CBS Read out cached applicability from TiLight for package: Package_for_KB4552152~31bf3856ad364e35~amd64~~18362.772.1.0, ApplicableState: 112, CurrentState:112
CBS WU creates the package, AppID:UpdateOrchestrator, UpdateID:{7CC12D9B-5F51-4EC9-9F5E-D038DBF5FD9B}, revision: 200
CBS Read out cached applicability from TiLight for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.836.1.6, ApplicableState: 112, CurrentState:96
CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
CBS Winlogon: Simplifying Winlogon CreateSession notifications
CBS Winlogon: Stopping notify server
CBS Winlogon: Unloading SysNotify DLL
Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
Info CBS Ending TrustedInstaller finalization.
Log Files for Windows 10 Servicing
Log Files for Windows 10 Servicing CBS.log
  • Dism.log – C:\Windows\Logs\DISM
Dism.log - C:\Windows\Logs\DISM
Dism.log – C:\Windows\Logs\DISM
PID=4300 TID=14848 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
DISM PID=4300 TID=14848 Scratch directory set to 'C:\windows\TEMP\'. - CDISMManager::put_ScratchDir
DISM PID=4300 TID=14848 DismCore.dll version: 10.0.19041.264 - CDISMManager::FinalConstruct
DISM Initialized Panther logging at C:\windows\Logs\DISM\dism.log

Upgrade to Windows 10 2004 Using SCCM

The process details at Windows 10 side.

Installing

Installing Windows 10 Servicing
Installing Windows 10 Servicing

Restart after Installation Windows 10 2004

  • The installation of Windows 10 2004 is completed.
  • Restart the device to complete the Windows 10 Servicing using SCCM.
Upgrade to Windows 10 2004 Using SCCM | ConfigMgr | Servicing 2
  • Let’s click on restart confirmation pop-up window.
Upgrade to Windows 10 2004 Using SCCM | ConfigMgr | Servicing 3
Upgrade to Windows 10 2004 Using ConfigMgr
  • Click Yes to confirm the restart because there were other users logged into the device.
Upgrade to Windows 10 2004 Using SCCM | ConfigMgr | Servicing 4
Upgrade to Windows 10 2004 Using ConfigMgr

Confirmation of Upgrade

  • Check the status of Windows 10 2004 servicing upgrade from console.
    • \Monitoring\Overview\Deployments\Feature update to Windows 10 (business editions), version 2004, en-us x64 Status to HTMD Collection
Upgrade to Windows 10 2004 Using ConfigMgr
Upgrade to Windows 10 2004 Using ConfigMgr

Resources

3 COMMENTS

  1. I have setup a Serving Plan for Windows 10 2004 based on your instructions. Everything in SCCM seems to be correct. The Pilot group I am using shows the 4 computers in the Monitoring/Deployments. Once computer shows Compliant (still at ver 1909), the other three show as Unknown/Client check passed/Active. This was done over a week ago, but the update still does not show in Software Center. The boundaries are correct, I can ping the computers from SCCM. Not sure where to look from here…

LEAVE A REPLY

Please enter your comment!
Please enter your name here

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