Jump to content

Recommended Posts

Posted

Last year I deployed windows 10 education 1809 - supported until May 2021, plenty of time.

 

We use wsus for updates, I haven't approved feature updates, and have group policy set to delay them by 365 days.

 

I have booted some computers this summer and they seem to now want to install 1903 update, no idea why (maybe it's been out over 365 days now). I intended to go to 1909 sometime this term via wsus, because of the longer support date of 1909.

 

I have now removed the 365 day delay group policy, and instead deployed the new one using the targetreleaseversioninfo policy, and set it to 1909, and approved the 1909 update in wsus. If I boot a machine that has been off for a while it seems to work as planned, takes a while to get the new policies, but then updates itself to 1909.

 

The machines that have updated to 1903 though do not seem to further update to 1909. Is there any reason for this? I could understand if the delay 365 days was still set but it isn't, they should surely update to the target release version of 1909?

Posted

Err iirc 1903->1909 is a different update as 1903 already had 1909 in it, just was a small patch to enable it

 

Check in WSUS for something "via enablement"

 

Steve

  • Thanks 1
Posted
1903 to 1909 is just a case of having the latest CU installed on 1903 and then doing the "via enablement package" update, which basically doesn't install anything new it just turns on the 1909 features that have been smuggled in by the CU. 1903 was late to release, and 1909 didn't introduce a great deal, so they slipped it in as part of the CU.
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...