Microsoft has announced a smaller wsusscn2.cab file will be available in a temp location until March 2022 when the new smaller wsusscn2.cab file will be available in the default location. This workaround can be used to publish and distribute the smaller wsusscn2.cab while we investigate options to add this temp location in Radia. I have run through these steps using the new wsusscn2.cab in the lab and successfully acquired MS-KB5007186. If you have any questions or problems please open a case with support. 

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/announcing-a-smaller-wsus-scan-cab/ba-p/2928256

The smaller wsusscn2_new.cab file can be manually downloaded for Radia to use to publish and distribute to the Radia end points.

1.> Download the new wsusscn2_new.cab and rename the file to wsusscn2.cab
http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2_new.cab

For data acquisition:
2.> Copy the wsusscn2.cab file to
C:\Program Files (x86)\PSL\RCA\Data\PatchManager\patch\microsoft
C:\Program Files (x86)\PSL\RCA\Data\PatchManager\patch\microsoft\wua

For metadata only acquisition:
2.> Copy the wsusscn2.cab file to
C:\Program Files (x86)\PSL\RCA\Data\PatchManager\patch\msft
C:\Program Files (x86)\PSL\RCA\Data\PatchManager\patch\msft\wua

3.> Add the following syntax to the acquire job, command line overrides section. 
-SKIP_WSUSSCNCAB_DOWNLOAD Y -SKIP_WSUSSCNCAB_EXTRACTION N

4.> Run the acquire job. The new smaller wsusscn2.cab file will be used to publish and distribute Security patch content in Radia.

Problem:

The following error appears in the logs and no October 2021 bulletins are being acquired. 

20211012 15:22:04 Error: can't read "bulletin_srvc_options(MS-KB5005635)": no such element in array
while executing
"split $bulletin_srvc_options($bname) "
(object "::Acquire::nEWMSFT0" method "::Acquire::NEWMSFT::get_srvc_filtered_bulletin_list" body line 14)
invoked from within
"get_srvc_filtered_bulletin_list"
(object "::Acquire::nEWMSFT0" method "::Acquire::NEWMSFT::convert_bulletins" body line 4)
invoked from within
"$p1 convert_bulletins"
20211012 15:22:04 Error: can't read "bulletin_srvc_options(MS-KB5005635)": no such element in array

Cause:

The Offline scan file format has changed.

Resolution:

Development is currently working on an official hotfix and a test hotfix is available. Please open a case with support and request the patch.tkd module. 

Microsoft has released out-of-band security updates to address a critical Windows print spooler vulnerability. Persistent has created the following custom XML files to distribute the security patches. Please open a case with Persistent and request the required kb numbers.  

Windows Print Spooler Remote Code Execution Vulnerability

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-34527

Here are all the bulletins that have the July 2021 OOB patch. These are applicable to x86 and x64 systems. Please open a support case with the required kb numbers. 

Windows 7 and Windows Server 2008 R2
July 6, 2021 KB5004953 (Monthly Rollup) Out-of-band

2021-07 Security Monthly Quality Rollup for Windows 7 for x86-based Systems (KB5004953)
2021-07 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB5004953)
2021-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5004953)

Windows 8.1 and Windows Server 2012 R2
July 6, 2021 KB5004954 (Monthly Rollup) Out-of-band

2021-07 Security Monthly Quality Rollup for Windows 8.1 for x86-based Systems (KB5004954)
2021-07 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB5004954)
2021-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5004954)

Windows 10 1607 LTSB and Windows Server 2016
July 7, 2021 KB5004948 (OS Build 14393.4470) Out-of-band

2021-07 Cumulative Update for Windows 10 1607 LTSB for x86-based Systems (KB5004948)
2021-07 Cumulative Update for Windows 10 1607 LTSB for x64-based Systems (KB5004948)
2021-07 Cumulative Update for Windows Server 2016 for x64-based Systems (KB5004948)

Windows 10 Version 1809/LTSB and Windows Server 2019
July 6, 2021 KB5004947 (OS Build 17763.2029) Out-of-band

2021-07 Cumulative Update for Windows 10 Version 1809 for x86-based Systems (KB5004947)
2021-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5004947)
2021-07 Cumulative Update for Windows 10 LTSB Version 1809 for x86-based Systems (KB5004947)
2021-07 Cumulative Update for Windows 10 LTSB Version 1809 for x64-based Systems (KB5004947)
2021-07 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5004947)

Windows 10 X64 Version 1909
July 6, 2021 KB5004946 (OS Build 18363.1646) Out-of-band

2021-07 Cumulative Update for Windows 10 Version 1909 for x86-based Systems (KB5004946)
2021-07 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5004946)

Windows 10 X64 Version 2004, 2009, 2104
July 6, 2021 KB5004945 (OS Builds 19041.1083, 19042.1083, and 19043.1083) Out-of-band

2021-07 Cumulative Update for Windows 10 Version 2004 for x86-based Systems (KB5004945)
2021-07 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB5004945)
2021-07 Cumulative Update for Windows 10 Version 20H2 for x86-based Systems (KB5004945)
2021-07 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5004945)
2021-07 Cumulative Update for Windows 10 Version 21H1 for x86-based Systems (KB5004945)
2021-07 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems (KB5004945)

A Radia custom (XML) Patch service can be used to update an endpoint from Windows 10 2004 to Windows 10 2009 using the Windows 10 version 20H2 Enablement Package (KB4562830). This enablement package is a more efficient way of updating the operating system as it does not require the full Windows 2009 ISO image file to be deployed to the endpoints. The KB4562830 enablement package is approximately 86MB in size whereas the full Windows 10 20H2 ISO payload is approximately 4.8GB in size. Therefore, deploying the Windows 10 20H2 feature update using the enablement package requires far less network bandwidth during the upgrade process.

Prerequisites

You must have the following prerequisites installed before applying this update:

• Servicing stack update for Windows 10, version 2004: September 8, 2020 or a later servicing stack update
• October 13, 2020 KB4579311 (OS Build 19041.572) or a later cumulative update

In some instances, it is not necessary to update the wsusscn2.cab file on each acquisition. Custom (XML) Patch services are independent of the wsusscn2.cab file so the wsusscn2.download and extraction can be skipped when acquiring custom XML files. 

NOTE: To request custom patch services from professional services, please open a case with support with the kb number or third-party application name, OS and architecture. For instance, KB4562830, Windows 10 2004 x64. 

Instructions:

(Request a copy of the custom xml file MSC-KB4562830.xml from support.)

1.> Copy the custom XML file MSC-KB4562830.xml into the <InstallDir>\RCA\data\PatchManager\patch\custom folder prior to acquisition. 

2.> Create a new custom acquisition job named custom or use an existing acquire job. A sample configuration is shown in the screenshot below.

3.> Enter the Bulletin to be acquired: MSC-KB4562830. 

4.> In the Command Line Overrides enter the following syntax to skip the wsusscn2.cab file download and extraction.

      -SKIP_WSUSSCNCAB_DOWNLOAD Y -SKIP_WSUSSCNCAB_EXTRACTION Y

5.> Set “Acquire Microsoft Patches” to Yes.

6.> Run the acquisition from the Operations Tab in the console and check the CSDB editor for the bulletin MSC-KB4562830.

7.> Assign the MSC-KB4562830 service in policy to start updating Windows 2004 systems to Windows 2009(20H2) the KB4562830 enablement package.

Starting with Radia 10 CP4, Software Download Manager is enabled by default. The Download Manager will download bits in the background using only radstgrq.exe and will not consume a Radia connect.

Refer to the 10.0CP4_Guides/New_Features_10.0_CP4.pdf starting on page 54 for detailed information on the new Software Download Management feature in CP4. 

Using preload=b initiates the background transfer of files to the endpoint.  

These instructions are for example WINDOWS_1903_ESD. This will deliver the Windows 10 install media to the end point in the background.  The Windows 10 ISO was extracted and published using basic component select mode. 

• Download the ISO, extract and publish the media. Example WINDOWS_1903_ESD

NOTE: After the service is published open the CSDB and set desired bandwidth throttling on the service.

• Assign WINDOWS_1903_ESD in Policy, NOTE: The service is set to Optional so it can be targeted using sname=WINDOWS_1903_ESD

• Create a preload background job or new timer instance to initiate the background transfer of WINDOWS_1903_ESD. Use sname=WINDOWS_1903_ESD and preload=b to enable the background transfer of the WINDOWS_1903_ESD service. Since this is a preload no radtray is available during this operation. The radstrgq.exe process runs while the transfer is running and will start and stop with system reboots, etc.

NOTE: Use DNAME=RADSTAGE or leave DNAME= off the command line so it will be automatically set to RADSTAGE.

Radskman.exe mname=radia,dname=RADSTAGE,uid=$MACHINE,ip=jlongoR11,port=3464,cat=prompt,cop=y,context=m,LOG=connect_preload_software.log,LOGSIZE=4096000,mnt=n,dname=radstage,sname=WIN10_1909_ESD,preload=b,rcsuri=tcp://jlongoR11:3464,datauri=http://jlongoR11:3466

• The service exists under the RADSTAGE folder

• The data is downloaded to the DATA folder

• After the preload completes create a new job or timer instance to build the media, note the preload=b has been removed.

Radskman.exe mname=radia,uid=$MACHINE,ip=jlongoR10,port=3464,cat=prompt,cop=y,context=m,LOG=connect_preload_software.log,LOGSIZE=4096000,mnt=n,sname=WINDOWS_1903_ESD,dname=software

• The new connect runs like a normal Radia connect and will display in the radtray.

• Once complete the media should exist in the expected folder.

• Review the new Download reporting in ReportingServer to see status of downloads for devices and services.

Windows 10, version 1903 will reach the end of service on December 8, 2020. This applies to the following editions of Windows 10 released in May of 2019:

• Windows 10 Home, version 1903
• Windows 10 Pro, version 1903
• Windows 10 Pro Education, version 1903
• Windows 10 Pro for Workstations, version 1903
• Windows 10 Enterprise, version 1903
• Windows 10 Education, version 1903
• Windows 10 IoT Enterprise, version 1903

Windows 10, version 1809 reached end of service On November 10, 2020 (Home, Pro, Pro for Workstations). If you are experiencing problems patching Windows 10 1809 we recommend updating Windows 10 to a supported version.