Separate Windows 10 by branch / version
Actually Windows 10 on WSUS is only reflected by a major product category and LTSB.
It would be much better if you could add a product category for each branch / release:
Windows 10 1507 (LTSB 2015)
Windows 10 1511
Windows 10 1607 (LTSB 2016, CBB)
Windows 10 1703 (CB)
This would allow companies with a good patch management to effectively avoid downloading CU patches for Windows 10 that they do not use and also would help to categorize updates in the views.
adrian moss commented
currently supporting 8.5k of devices and none of the are x86 and a mix of 1709 and 1803 would be good to limit things more
Good news folks,
Microsoft has not committed it officially but this one is subject to change:
1. Every H1 version (Spring release) will be seeing a major update from any previous version
2. Every H2 version (autumn release), which has also extended 30 Months support on Ent/Edu is just a CU like upgrade of H1 if you step up from the same year H1, else it is a usual big update chunk (3,x GB upgrade for x64)
Both releases will have an own WSUS product category, share the SAME patches, and I hope that this will follow the scheme for 20H1 / 20H2 releases.
This means we are saving additional 50% of space on WSUS and can also limit to one version.
Know that express installation files till Windows Vista till Windows 10 1803 have 4x the size of the usual updates. The express updates starting from 1809 and later have about 1/10 of the size of the usual updates. Means that with 1903 instead of
8 GB the usual monthly CU (4 times x 2 releases x 1 GB per monthly CU) we have 1 CU about 150-300 MB for a whole release).
Philip Sannwald commented
Separation by architecture would be helpful, too.
Currently, I' supporting close to 150 systems, none of which are x86 or ARM64. Wish I did have to have those updates in the database.
This is still unsolved and causes unwanted overhead in the WSUS DB guys.
If a customer only has to patch 1709, don't let him down to enlist and he has manually to decline all 1507,1511,1607,1703 updates this is a real mess of work every month, sometimes several times a month.
Please fix this design issue in the product categories. You do it for driver packages but not for the updates, makes no sense to me why.
there is still no change. Companies using Windows 10 / 2016 Server cannot run auto acknowledgement rules for CUs without downloading
CUs for 1607 / 2016 Server, understandably
but could avoid CUs for 1511, 1507, 1703, 1709 depending how fragmented their rollout infrastructure for clients look like.