[1909, ou] WSUS for 1909

[Warwick_Tech]

Hey All,

 

I know a lot of people have moved away from WSUS, but I'm happy with my setup!

 

Basically 1909 hasn't shown up on my classifications page yet; according to SCCM 1903 and 1909 share the same common core so updates are applied to both, but I wanted to check with everyone here before I ticked the box

 

Has anyone else got 1909?

 

[themightymrp]

Nope, the 1903 option seems to cover it for us.

[foofighterjim]

We have a few test machines running 1909 (including mine) with the same WSUS Products selected as you do + the 1903 and later option, 1803 and 1909 clients all updated from WSUS without an issue for January and February. Edited March 3, 2020 by foofighterjim

[mavhc]

What's the difference between the "Windows 10" cat and the "xxxx or later", and why is there more than 1 "xxxx or later"?

[themightymrp]

I was finding that my updates for 1909 weren’t downloading until I ticked the 1903 and later tick box directly above “Windows 10”. Not sure why? I still have that Windows 10 box ticked as this is servicing the machines I still have on an older build.

 

The other boxes I believe include the options for drivers and the big 6 monthly feature updates. Which I don’t want as will manage manually.

[Warwick_Tech]

I updated my WSUS server overnight with the cumulative update and I got 'Windows 10 Vibranium and later' instead of 1909....

 

What on Earth is Windows 10 vibranium ??

 

 

https://www.howtogeek.com/fyi/get-ready-for-windows-10-vanadium-and-vibranium/

[themightymrp]

Love it!

[mavhc]

https://www.thurrott.com/windows/windows-10/190138/windows-10s-next-major-updates-will-be-codenamed-vanadium-vibranium

[Warwick_Tech]

After a manual sync and more tickboxes seems to be working now - cheers all

 

 

I just wish Ms would stick to a pattern instead of this seemingly random roadmap

[CHiLL]

I updated my WSUS server overnight with the cumulative update and I got 'Windows 10 Vibranium and later' instead of 1909....

 

What on Earth is Windows 10 vibranium ??

 

[ATTACH=CONFIG]56991[/ATTACH]

 

https://www.howtogeek.com/fyi/get-ready-for-windows-10-vanadium-and-vibranium/

Yeah I see that too, although like you, I don't have just "Windows 10, Vibranium and later". Instead I just have "Servicing Drivers" and Upgrade & Servicing Drivers".

 

Edit: I wonder if they're changing it to avoid confusion? Windows 10 2003 would be weird under their previous naming convention of yy/mm. Although that is still the naming convention for SCCM (2002 is due in March)

Edited March 4, 2020 by CHiLL

[themightymrp]

Not sure why they don'y use the 19H2 , 20H1 naming convention? That at least makes some sense and the terminology is already out there.

[ictgoodpractice]

Are am having a new server installed. All workstations need to be re-imaged. We are running 1903. Is 1909 something people would upgrade to or should I ask to stay on 1903?

[Guest Guest]

I'd upgrade to 1909 as the 09 builds are supported for longer than 03 builds

[Primus]

Agreed get to 1909.

[RebelBurr34]

I'd upgrade to 1909 as the 09 builds are supported for longer than 03 builds

Good luck.

[mavhc]

Wait a week, get 2004

[kyleii]

Yeah wait 2004

[Wubbalubbadub]

Where can I find 2004 release date?

[Primus]

We tend not to deploy a new release immediately. Also as said the H2 releases have a longer life - if something cropped up and you couldn’t move to a later version you’d have more time with updates on an H2 release.