Blogger | Techie | Navy Veteran | Entrepreneur
In July, we announced that the Windows 10 November 2019 Update would be a scoped release for select performance improvements, enterprise features and quality enhancements. Today, we are announcing that the Windows 10 November 2019 Update is now available for users on the most recent versions of Windows 10 who seek the new update via Windows Update.
Learn more here: How to get the Windows 10 November 2019 Update
Hello Windows Insiders! Today we are releasing 19H2 Build 18362.10022 to Windows Insiders in the Slow ring. This build includes the improvements and fixes from KB4515384 as well as general improvements to the overall quality of 19H2.
Source: Announcing Windows 10 Insider Preview Build 18362.10022 (19H2)
So, I ran into a situation where after upgrading a Win 10 machine to Windows 10 v1809, that it did not have .net 3.5 installed on the machine; and can only assume that the upgrade must have messed up something; and in troubleshooting figured out also that .Net 3.5 is also a Feature on Demand (FoD). My remediation below:
If you go to the Volume Licensing Service Center (VLSC) and download the FoD package, you will be able to install via offline or just create an SCCM application/package.
Once you complete the download, extract disk 1 of the FoD. Next, create a new folder so you only copy the .cab’s that are needed to install RSAT. No reason to use the huge 4.5GB file. The files/folders that are need to be copy is as follows:
metadata (folder)
FoDMetadata_Client.cab
Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~.cabNow that you have the files in a folder, create a PowerShell script in that folder to run to install .Net 3.5. Here is an example of what we used:
$NETFX3Install=Get-WindowsCapability -Online -Source .\ -LimitAccess |where name -like netfx3* | select name
foreach ($item in $NETFX3Install){
Write-Output $item.Name
Add-WindowsCapability -Online -Name $item.name -LimitAccess -source .\
}Hopefully this helps you out as it did I.
If you already didn’t know, since 1809 if I remember correctly, RSAT is now part of the Feature on Demand (FoD). This is convenient if you have your WSUS going to Microsoft, but some enterprises control and run there own WSUS environment.
Lucky I had some help thanks to Twitter @OSDownunder. If you go to the Volume Licensing Service Center (VLSC) and download the FoD package, you will be able to install via offline or just create a SCCM application/package.
Once you complete the download, extract disk 1 of the FoD. Next, create new folder so you only copy the .cab’s that are needed to install RSAT. No reason to use the huge 4.5GB file. The files/folders that are need to be copy is as follows:
FoDMetadata_Client.cab
metadata
Microsoft-Windows-ActiveDirectory-DS-LDS-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-ActiveDirectory-DS-LDS-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-ActiveDirectory-DS-LDS-Tools-FoD-Package~31bf3856ad364e35~wow64~en-US~.cab
Microsoft-Windows-ActiveDirectory-DS-LDS-Tools-FoD-Package~31bf3856ad364e35~wow64~~.cab
Microsoft-Windows-BitLocker-Recovery-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-BitLocker-Recovery-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-CertificateServices-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-CertificateServices-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-DHCP-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-DHCP-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-DNS-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-DNS-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-FailoverCluster-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-FailoverCluster-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-FailoverCluster-Management-Tools-FOD-Package~31bf3856ad364e35~wow64~en-US~.cab
Microsoft-Windows-FailoverCluster-Management-Tools-FOD-Package~31bf3856ad364e35~wow64~~.cab
Microsoft-Windows-FileServices-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-FileServices-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-GroupPolicy-Management-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-GroupPolicy-Management-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-GroupPolicy-Management-Tools-FoD-Package~31bf3856ad364e35~wow64~en-US~.cab
Microsoft-Windows-GroupPolicy-Management-Tools-FoD-Package~31bf3856ad364e35~wow64~~.cab
Microsoft-Windows-IPAM-Client-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-IPAM-Client-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-IPAM-Client-FoD-Package~31bf3856ad364e35~wow64~en-US~.cab
Microsoft-Windows-IPAM-Client-FoD-Package~31bf3856ad364e35~wow64~~.cab
Microsoft-Windows-LLDP-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-NetworkController-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-NetworkController-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-NetworkLoadBalancing-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-NetworkLoadBalancing-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-RemoteAccess-Management-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-RemoteAccess-Management-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-RemoteAccess-Management-Tools-FoD-Package~31bf3856ad364e35~wow64~en-US~.cab
Microsoft-Windows-RemoteAccess-Management-Tools-FoD-Package~31bf3856ad364e35~wow64~~.cab
Microsoft-Windows-RemoteDesktop-Services-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-RemoteDesktop-Services-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-ServerManager-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-ServerManager-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-ServerManager-Tools-FoD-Package~31bf3856ad364e35~wow64~en-US~.cab
Microsoft-Windows-ServerManager-Tools-FoD-Package~31bf3856ad364e35~wow64~~.cab
Microsoft-Windows-Shielded-VM-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-Shielded-VM-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-StorageManagement-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-StorageManagement-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-StorageManagement-FoD-Package~31bf3856ad364e35~wow64~en-US~.cab
Microsoft-Windows-StorageManagement-FoD-Package~31bf3856ad364e35~wow64~~.cab
Microsoft-Windows-StorageReplica-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-StorageReplica-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-SystemInsights-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-SystemInsights-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-VolumeActivation-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-VolumeActivation-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cab
Microsoft-Windows-WSUS-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab
Microsoft-Windows-WSUS-Tools-FoD-Package~31bf3856ad364e35~amd64~~.cabNow that you have the files in a folder, create a PowerShell script in that folder to run to install RSAT. Here is a example of what we used:
$RSATInstall=Get-WindowsCapability -Online -Source .\ -LimitAccess |where name -like rsat* | select name
foreach ($item in $RSATInstall){
Write-Output $item.Name
Add-WindowsCapability -Online -Name $item.name -LimitAccess -source .\
}Go to my GitHub page to get the .ps1 script as well.
Hopefully this helps you out as it did I.