improving WSUS Database and installation

%3CLINGO-SUB%20id%3D%22lingo-sub-1409240%22%20slang%3D%22en-US%22%3Eimproving%20WSUS%20Database%20and%20installation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1409240%22%20slang%3D%22en-US%22%3EAdamJ%20made%20it%20possible%20to%20have%20a%20versatile%20paid%20script%20for%20WSUS%203.0%2FWSUS%203.2%20that%20is%20also%20correcting%20the%20Version%20Strings%20of%20WSUS%20%22clients%22%20when%20hosted%20on%20Server%202016%2F2019.%3CBR%20%2F%3E%3CBR%20%2F%3EAffected%3A%20Version%20Name%20and%2For%20number%3CBR%20%2F%3EWSUS%20%22clients%22%3CBR%20%2F%3EWindows%20Server%202016%20%26amp%3Bgt%3B%20shows%20Windows%2010.0%3CBR%20%2F%3EWindows%20Server%202019%20%26amp%3Bgt%3B%20shows%20Windows%2010.0%3CBR%20%2F%3EWindows%2010%201909%20%26amp%3Bgt%3B%20shows%20Windows%2010%201903%3CBR%20%2F%3Elikely%20Windows%2020H2%20will%20show%20Windows%202004.%3CBR%20%2F%3E%3CBR%20%2F%3EDo%20you%20plan%20to%20investigate%20some%20of%20these%20issues%20and%20fix%20them%20with%20a%20WSUS%20related%20CU%20that%20will%20approach%20the%20WSUS%20database%20issues%20and%20fix%20it%2C%20so%20we%20do%20not%20have%20to%20rely%20on%203rd%20party.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20problem%20is%20solveable%20and%20not%20by%20design.%26amp%3Bnbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20default%20behaviour%20does%20make%20WSUS%20reports%20unuseable%20and%20makes%20servicing%20harder.%3CBR%20%2F%3EIt%20is%20great%20to%20have%20a%20new%20WSUS%20update%20category%20for%201903%2F1909%20and%202004%2F20H2%2C%20but%20the%20strings%20should%20be%20displayed%20correctly.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20not%20asking%20to%20ruin%20Adam's%20work%20%2F%20business%20model%2C%20just%20to%20fix%20the%20names%20of%20WSUS%20%22clients%22%20is%20a%20minimum%20I%20would%20see.%20There%20are%20still%20a%20lot%20of%20users%20for%20WSUS%2C%20not%20matter%20if%20there%20are%20other%20methods%20like%20WuFB%2C%20SCCM%2C%20MECM.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%20when%20setting%20up%20WSUS%20with%20WID%20or%20external%20SQL%2C%20can%20you%20please%20consider%20to%20apply%20correct%20settings%20for%20IIS%20AppPool%20by%20default.%20The%20current%20setting%20will%20not%20work%20out%20of%20the%20box.%3C%2FLINGO-BODY%3E
Occasional Contributor
AdamJ made it possible to have a versatile paid script for WSUS 3.0/WSUS 3.2 that is also correcting the Version Strings of WSUS "clients" when hosted on Server 2016/2019.

Affected: Version Name and/or number
WSUS "clients"
Windows Server 2016 > shows Windows 10.0
Windows Server 2019 > shows Windows 10.0
Windows 10 1909 > shows Windows 10 1903
likely Windows 20H2 will show Windows 2004.

Do you plan to investigate some of these issues and fix them with a WSUS related CU that will approach the WSUS database issues and fix it, so we do not have to rely on 3rd party.

The problem is solveable and not by design. 

The default behaviour does make WSUS reports unuseable and makes servicing harder.
It is great to have a new WSUS update category for 1903/1909 and 2004/20H2, but the strings should be displayed correctly.

I am not asking to ruin Adam's work / business model, just to fix the names of WSUS "clients" is a minimum I would see. There are still a lot of users for WSUS, not matter if there are other methods like WuFB, SCCM, MECM.

Also when setting up WSUS with WID or external SQL, can you please consider to apply correct settings for IIS AppPool by default. The current setting will not work out of the box.
0 Replies