Windows 10 Build Updates

[yhttech]

As I prep for the new school year, the classroom computers are a couple of major build versions behind. Short of manually logging in and launching the update assistant, I can't seem to find a more efficient way to have them install these massive updates. WSUS doesn't seem to show them as available. Has anyone found a way to automate this? Can I download the latest build and create an MDT task sequence to install? I don't want to have to re-create my images every few months when MS releases a new build, and have to keep re-imaging the machines.

[ADMaster]

I’m not sure if this is a serious question, or a misunderstanding of what you’re asking. This has been talked about every six months for the last few years.

In short, script everything you can during osd, swap in the updated wim and tweak as needed for each build.

I wouldn’t bother upgrading a classroom PC, just reimage.

SCCM has an upgrade TS if you really want to do the upgrade route, I’m sure MDT has something similar.

 

It also sounds like your WSUS may not be configured properly, so you should check what products and classifications you’re syncing.

[Fazza]

If you're talking about Windows 10 1803, 1790, 1703 etc. then from what I understand these will appear in Windows Updates for Home Users but not for Enterprise users which is why you may not find them in WSUS. They are available as ISO images on the Microsoft Licensing website.

 

I've never used MDT, but to Automate it using SCCM all you do as add it as an Upgrade and then deploy it to your computers as Required and then it'll upgrade them to the latest version of Windows 10.

[gaz350b]

I think there are some pre-reqs for wsus before you will get feature updates for windows 10.

[sparkeh]

Also don’t upgrade to each release. Check the end of support dates and update when needed.

[mavhc]

I upgrade using WSUS all the time, it's not too bad.

[DBazeley95]

Install the pre-reqs for WSUS and I had to add the .esd file type to IiS for some reason but it works now

[DavR]

I got this working over WSUS, but found the in-place upgrades so slow, I just gave in to the fact I'm going to be making a new build and re-imaging now every summer :/

 

To get it working in WSUS you need the Upgrades category enabled (beware, big file storage hit) and add the esd file type in IIS as mentioned above.

[mavhc]

They're too slow to leave on shared laptops really, maybe takes an hour, scheduled overnight usually is fine.

[Asgard]

I upgrade using WSUS all the time, it's not too bad.

 

+1 worked an absolute dream for us.

 

Just in-place upgraded just shy of 2000 machines to 1803 using this as a basis;

 

https://www.joseespitia.com/2017/06/01/how-to-run-a-post-script-after-a-windows-10-feature-upgrade/

 

Broad outline;

1. Upgraded one and ran our AppX poweshell script to see what silliness was added back in

 

2. Created a remove-1803Junk.ps1 and wrapped it inside a batch file

 

3. Deployed it to all the PCs via GPO (to c:\scripts)

 

4. Tweaked the WSUS settings as per the link above and approved the feature update in Wsus

 

Sat back and let WSuS take over. We set it all to run on the last day of term and over the weekend.

 

Came in the Monday and it was virtually done just a few machines didn’t fancy rebooting as it felt it wasn’t convenient and wanted to do it at 4pm that day haha

[chris11256]

We deploy the Windows feature updates via SCCM as required. Have it setup as an upgrade and half way through it runs our script to remove all of the rubbish. Haven't had any problems with it. Newer computers take about 30 minutes, old ones take a few hours.