To improve Windows Server I suggest you ...

WSUS on Win2012: Fix issue that causes Windows Server 2016 clients OS to be listed as "Windows (Version 10)"

When using WSUS on Windows 2012 (WSUS 4.x), the WSUS console incorrectly lists Windows Server 2016 clients with Operating System "Windows (Version 10)". This is confusing to customers, and causes them concerns related to reporting, as well as the ability to update Win2016 clients with WSUS on Windows 2012.

This issue does not occur with WSUS on Windows 2016, where Windows Server 2016 clients are listed with Operating System as "Windows Server 2016 <edition>".

21 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Eric Ellis shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Brandon commented  ·   ·  Flag as inappropriate

        This bug is back again with the semi-annual build of Server 2016. Even on a 2016 WSUS server, any servers with WS2016 1709 installed show up as "Windows (Version 10.0)"

      • Neil commented  ·   ·  Flag as inappropriate

        The fix currently suggested by Microsoft, ie running a sql command on the susdb database every time that a new Win2k16 client is added, results in a laborious process. It also does not specify if in fact the Windows 10 clients will now appear in the Win2k12 Wsus server as Win2k16 after the fix has been applied.
        To avoid further confusion, a permanent WSUS fix from Microsoft for this issue is needed soon.

      Feedback and Knowledge Base