1709 > 1803 upgrade force using WSUS

[buzzard]

Hi, I'm looking for a way to force the upgrade from 1709 to 1803 (Education), I'm just doing some testing prior to actually pushing this into the live environment. We've the deployment rings set up in WSUS as per MS Articles for WSUS and W10 and I've got the 1803 update to appear to the end user (teacher laptop). Knowing the teachers, they'll keep clicking not now, I've been looking for a way to force the update on either a date or before a date other than a manual intervention but have only come up with ways of deferring the update. I've not needed to update W10 version yet as we went live with 1709. Any pointers or advice from those who have already updated previously would be great.

 

Thanks

[NetworkServices]

I'd be very interested in hearing how others get on with an in place upgrade since this method is what I've been looking into. My only concern is that a lot of the crapware will get re-installed during the process.

[buzzard]

I'm planning on having a GP that, using a WMI query, will ID it as 1803 then 'run once' a PS script on startup to strip out the crap 1803 installs. its the forcing the update to install that I cant find any info on, closest I've found is this - https://gal.vin/2017/08/23/upgrading-to-windows-10-from-previous-version-of-windows/

[buzzard]

I dont suppose anyone's had a chance to look at this at all? I'm not getting very far with regards to consistency, if anything the more I try, the more I end up with 1709 machines that will no longer call home to WSUS

[mavhc]

Working here on Pro, just adding a few machines to a WSUS group at a time

[ICT_GUY]

It worked sporadically here. In the end it was easier to re-image all of the pcs in the school.

[ollyyllo]

I'd be very interested in hearing how others get on with an in place upgrade since this method is what I've been looking into. My only concern is that a lot of the crapware will get re-installed during the process.

 

Tested manually upgrading from 1703 to 1803 and 1709 to 1803, crapware didn't re-install.

 

This post from Microsoft suggests upgrades should behave themselves from 1703 on-wards.

 

https://docs.microsoft.com/en-us/windows/whats-new/whats-new-windows-10-version-1703

 

Additionally, apps de-provisioned by admins on Windows 10, version 1703 machines will stay de-provisioned after future feature update installations. This will not apply to the update from Windows 10, version 1607 (or earlier) to version 1703.

Edited May 21, 2018 by ollyyllo