none
Windows Server 2016 WSUS Clients shown as "Windows (Version 10.0)" RRS feed

  • Question

  • Dear all,

    I have a question to add Windows Server 2016 WSUS Clients to WSUS Server 2012 R2.

    In my domain I am using a Windows Server 2012 R2 Server as WSUS Server. Yesterday I installed the first Windows Server 2016 member server in the domain. This member server is a WSUS client, configured by GPO to get updates from the WSUS server.

    The member server is shown as client in the WSUS console. I now have sorted the client with "Group by operating system" in the console.

    The Windows Server 2016 member server and the Windows 10 clients are grouped to one operating system version group: "Windows (Version 10.0)".

    Is this the right way to show the WSUS clients or is there any patch missing at WSUS server?? Has anyone experience with this case? I expect to group the clients to "Windows 10" and "Windows Server 2016".

    Helpful answers are welcome! Thank you.

    Wednesday, April 26, 2017 1:55 PM

Answers

All replies

  • Am 26.04.2017 schrieb L3ll3r:

    In my domain I am using a Windows Server 2012 R2 Server as WSUS Server. Yesterday I installed the first Windows Server 2016 member server in the domain. This member server is a WSUS client, configured by GPO to get updates from the WSUS server.

    The member server is shown as client in the WSUS console. I now have sorted the client with "Group by operating system" in the console.

    <https://social.technet.microsoft.com/Forums/getfile/1054993>

    The Windows Server 2016 member server and the Windows 10 clients are grouped to one operating system version group: "Windows (Version 10.0)".

    Yes, this is correct in W2012R2. If you are install WSUS direct on
    W2016, then you have the correct description.

    Is this the right way to show the WSUS clients or is there any patch missing at WSUS server?? Has anyone experience with this case? I expect to group the clients to "Windows 10" and "Windows Server 2016".

    You can run in Taskplaner hourly this Script:
    https://wsus.de/de/Scripts/Windows-Editionen-anzeigen

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Wednesday, April 26, 2017 4:16 PM
  • Hi L3ll3r,

    >Is this the right way to show the WSUS clients or is there any patch missing at WSUS server??

    Yeah, this is a known issue at present on WSUS server 2012R2:

    Besides, please check if the WSUS server has installed KB3095113 and KB3159706(with manual steps), if not, please install the two KBs to upgrade the WSUS server.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, April 27, 2017 5:05 AM
    Moderator
  • Hi L3ll3r,

    Just to check if the above reply could be of help? If yes, you may mark useful reply as answer, if not, welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 3, 2017 5:43 AM
    Moderator
  • WSUS running on Server 2016 will show correct OS name for WSUS clients.

    E.g. "Windows 10 Enterprise" or "Windows Server 2016 Standard"
    Unfortunally Hyper-V Server 2016 is still shown as "Windows (Version 10.0)"

    Tuesday, May 23, 2017 9:46 AM
  • I have a similar question, but about Server 2019.

    My WSUS is running on Server 2012 and Servers 2016 and now 2019 appear as Windows Server (Version 10.0)

    So the "problem" is OS on which WSUS resides?


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Wednesday, May 8, 2019 2:54 PM
  • Am 08.05.2019 schrieb pob579:

    I have a similar question, but about Server 2019.

    My WSUS is running on Server 2012 and Servers 2016 and now 2019 appear as Windows Server (Version 10.0)

    So the "problem" is OS on which WSUS resides?

    Yes and no. Did you use my SQL Server Script i posted here?

    Winfried


    WSUS Package Publisher:
    https://github.com/DCourtel/Wsus_Package_Publisher
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home
    GP-PACK - PRIVACY AND TELEMETRIE: http://www.gp-pack.com/

    Wednesday, May 8, 2019 6:56 PM
  • I've been running the SQL script however I'm finding, now we have a few 2019 servers these are also displayed as Server 2016.

    I'm assuming this is because for Server 2019 the 'OSMajorVersion' is also '10' and 'ProductType' is the same. 

    Is it possible to update the SQL script to look at the Version Number reported by WSUS and update the OSDescription accordingly i.e.

    If Version is 10.0.14393 set OSDescription to Windows Server 2016 Version 1607

    If Version is 10.0.16299 set OSDescription to Windows Server 2016 Version 1709

    If Version is 10.0.17763 set OSDescription to Windows Server 2019 Version 1809

    etc.

    I've no knowledge of the WSUS SQL DB so not sure if this is even possible.

    Thanks

    Tuesday, September 17, 2019 8:26 AM
  • I did in place upgrade of WSUS on2012 to Server 2019.

    Everything displays as it should be.

    This turn out as known issue WSUS on 2012 not showing correct OS of upper versions.

    WSUS on 2019 is version 10.

    To prevent issues after upgrade monitor the memory usage and add if necessary.

    The new server flying and everything displays correctly.


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Tuesday, September 17, 2019 5:15 PM
  • I've been running the SQL script however I'm finding, now we have a few 2019 servers these are also displayed as Server 2016.

    I'm assuming this is because for Server 2019 the 'OSMajorVersion' is also '10' and 'ProductType' is the same. 

    Is it possible to update the SQL script to look at the Version Number reported by WSUS and update the OSDescription accordingly i.e.

    If Version is 10.0.14393 set OSDescription to Windows Server 2016 Version 1607

    If Version is 10.0.16299 set OSDescription to Windows Server 2016 Version 1709

    If Version is 10.0.17763 set OSDescription to Windows Server 2019 Version 1809

    etc.

    I've no knowledge of the WSUS SQL DB so not sure if this is even possible.

    Thanks

    WSUS Automated Maintenance © has this feature already. It will Rename all the OS Descriptions to their proper names: Eg: Windows Server 2012 R2 Datacenter, Windows 10 1709 Enterprise, Windows 10 Pro 1903, Windows Server 2016 Standard, etc.

    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Tuesday, September 17, 2019 7:40 PM