WSUS server Windows 20H2 detect and report
Please,
update WSUS and Update agents to correctly show new 19.042.572 (20H2)in WSUS management console. Need it for Inventory and Esset management. Thanx :D
Anonymous
shared this idea
8 comments
-
Karl Wester-Ebbinghaus (@tweet_alqamar)
commented
This also affect Windows Server 2016 / 2019 being reported as Windows (10.0)
-
Nekku
commented
It's needed to verify from WSUS console, what OS build is on client desktop
-
AC
commented
21H1 will seemingly be another enablement package laid upon a 2004/20H2 base, so this issue will soon become even worse when we won't be able to distinguish 3 separate Win10 versions from each other in WSUS. Seriously, this has to get fixed, either by Windows 10 itself updating the build number of the Update Engine, or WSUS getting patched to instead reflect clients' build numbers.
-
Karl Wester-Ebbinghaus (@tweet_alqamar)
commented
This also applies to 1903 / 1909.
This database string can be fixed by this tool, so Why not originally by MSFT?
https://www.ajtek.ca/wam/what-is-wsus-automated-maintenance/ -
Ichikawa Kazuaki
commented
私は、年を取っているのでよくコンピュータシステムがよくわかりません又その用語も、よくわかりません。その辺を考慮してアドバイスを宜しくお願い致します。
-
Reham Hesham commented
windows 10
-
Ta Dong
commented
vhjmb k
-
Mika Melonen
commented
This will become a problem when upgrading 20H2 to production and trying to see which workstations are updated. Luckily 2004 is reporting right and it can be consider to be production ready.