Radia - General Discussions

Jim Longo

Windows 10 1709 to 1803 Branch Update using Radia Patch Manager

 A Radia customer recently asked if Radia Patch Manager can be used to manage Windows 10 Branch Updates. 


 The short answer is yes, it is possible to use Radia Patch Manager to update Windows 10 to a newer branch but it may be more advantageous to use Radia Software or OS Manager to manage Windows 10 Branch Updates because there is more functionality built into Software/OS Management processes.


 Radia Patch Manager is more of a drop and run scenario where Radia Patch Manager delivers the Branch Update Media and a script to initiate the update. This can be done with 2 services to deliver the content and execute the update on separate occasions, or a single service to deliver and execute the update at the same time.  


 Below is an overview of using Radia Patch Manager to deliver the Branch Update media, a script to execute the Branch Update, and a custom descriptor file to acquire/manage the delivery of a Branch Update.


 While this is not considered to be the best way of updating Windows 10 Branch Updates, this example provides some insight into the flexibility of Radia Patch Manager to provide custom content delivery and execution.. 


 Windows 10 Branch Update  overview:


1.>   Download and execute the latest MediaCreationTool.

2.>   Extract Windows.iso, rename the Windows folder to Windows_1803_ESD

3.>   Use component select mode to publish WINDOWS_1803_ESD to the PATCHMGR Domain. (For this example, folder renamed to Windows_1803_ESD and location is C:/temp).


4.>   The Windows_1803_ESD service should now be present in the PATCHMGR.ZSERVICE Domain. The service will deliver the media to the agent if the media doesn’t exist. The media can be staged on the agent in the c:/temp/Windows_1803_ESD folder using a custom Patch service, or a compiled script to copy the media to the agent over the Network prior to the install event. The install event and media delivery can be run separately in different Patch services.


5.>   Create, compile and acquire the installation script using a custom Descriptor file to manage Windows 1803. (.vbs compiled to .exe). Modify the command line with the desired install options, Example: include /Noreboot to stop the automatic reboot after the Branch Update is installed.






6.>   The MSBU-WIN1803 Patch service should now be present in the CSDB. In this example, only Windows 10 1607/1703/1709 systems are applicable and will execute if ReleaseID is not set to 1803 in the registry.

 In the PATCHMGR Domain locate the MSBU_WIN1803 service, right click/show connections, locate and drag Windows_1803_ESD service onto the MSBU_WIN1803 service.


8.>   Assign MSBU_WIN1803 in Policy and run a patch connect from a Windows 10 1709 system.


9.>   The MSBU_WIN1803 will be at risk since the ReleaseID is not set to1803 and the sub service WINDOWS_1803_ESD will deliver the OS. Once WINDOWS_1803_ESD is delivered MSBU_WIN1803 will execute installing/upgrading Windows 10 to 1803.


 And finally the compliance reporting.


1 comment

Please sign in to leave a comment.


Previous 1 comment

Nigel Ryan

Thanks Jim, your Patch Manager info is always very useful.

Comment actions Permalink

Top Contributors