[2004, 20h1] Windows 10 feature Update Via WSUS

[2097]

Has any one else tried updating to a feature update via WSUS ?

 

I kept getting an install error , My network is setup so only outside access is via a firewall.

 

Ultimately found the solution via

 

https://social.technet.microsoft.com/Forums/en-US/3a8740cc-ccb0-4ebb-a209-25e08ccc6f61/update-win10-2004-is-not-installed-without-the-internet?forum=winserverwsus

 

Seems a very backwards way of doing things.

[3s-gtech]

Yes, I updated from 1703 to 1903 last year, site wide, using WSUS.

 

Worked much better than I thought it would, only a few odd laptops missed it. My PCs are set to never connect to Windows Update online via GP.

[2097]

Yes, I updated from 1703 to 1903 last year, site wide, using WSUS.

 

Worked much better than I thought it would, only a few odd laptops missed it. My PCs are set to never connect to Windows Update online via GP.

 

Hi ,

 

Did you have to do the above ? Or did it work ok for that update.

[3s-gtech]

No, didn’t need to do that - only thing I scripted was emptying the SoftwareDistribution folder in C:\Windows which helped to kick off any devices that weren’t detecting the update.

[jthompson]

I had to add whatever file type it is that's used for feature updates (ESD?) to IIS that's serving WSUS, so that clients could actually download it from WSUS, but apart from that, it worked. It took ages, but it worked.

 

Not rolled out a big feature update in this way here at scale though, since our machines are mainly imaged as 1903 and going to 1909 using the enablement patch.

[2097]

I had to add whatever file type it is that's used for feature updates (ESD?) to IIS that's serving WSUS, so that clients could actually download it from WSUS, but apart from that, it worked. It took ages, but it worked.

 

Not rolled out a big feature update in this way here at scale though, since our machines are mainly imaged as 1903 and going to 1909 using the enablement patch.

 

Yes i have already done that.

 

Defiantly seems i need to add that file to the default user folder on each machine. Otherwise it seems to try and connect to the internet instead of WSUS to try and grab the file.

 

Its my first feature update as we are already on 1909 and are new adapters to Windows 10

[2097]

Also.. Have another problem .

 

Im getting the message popup on each machine saying " Restart to install feature update"

 

Unless you manually click restart on each one, it wont upgrade.

 

Any way to automate this with a GPO setting ?

[computer_expert]

Also.. Have another problem .

 

Im getting the message popup on each machine saying " Restart to install feature update"

 

Unless you manually click restart on each one, it wont upgrade.

 

Any way to automate this with a GPO setting ?

 

What about a deadline set in WSUS? I've not tried it with feature upgrades but when using deadlines on normal monthly updates it does the job.

[2097]

What about a deadline set in WSUS? I've not tried it with feature upgrades but when using deadlines on normal monthly updates it does the job.

 

Thanks for that , As i have the ESD file and windowsupdatebox.exe, i have just packaged it into an application for SCCM. Might be a lot easier to install that way

[computer_expert]

Thanks for that , As i have the ESD file and windowsupdatebox.exe, i have just packaged it into an application for SCCM. Might be a lot easier to install that way

 

There's an even easier way as you have SCCM/MEMCM - Windows 10 Servicing Plans https://docs.microsoft.com/en-us/mem/configmgr/osd/deploy-use/manage-windows-as-a-service

 

My preferred way would be to use a task sequence to perform the upgrade as you get more control over the process (e.g. uninstall incompatible software before the upgrade and reinstall after, modern app removal etc)