locked
Windows 10 and WSUS RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    2
    Sign in to vote

    We have been using Windows 2008 R2 server for our WSUS server. It's been doing a good job, but when Windows 10 came along, WSUS flag it as Windows Vista. Any idea why WSUS flag Windows 10 as Vista?

    Thanks,

    Larry

    Wednesday, September 2, 2015 3:37 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Am 02.09.2015 schrieb MaxxamA:

    We have been using Windows 2008 R2 server for our WSUS server. It's been doing a good job, but when Windows 10 came along, WSUS flag it as Windows Vista. Any idea why WSUS flag Windows 10 as Vista?

    Check the Build from your WSUS:

    WSUS 3.0 (SP2):     Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211:     Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608:     Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185:     Build 3.2.7600.262
    WSUS 3.0 (SP2) + KB2938066:     Build 3.2.7600.274

    Here you find the correct place for control the Build:
    http://www.wsus.de/images/wsus-version.png

    Or you can use this TSQL-Script:

    UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]
SET [OSDescription] = 'Windows 10'
WHERE [OSMajorVersion] = '10'
AND [OSMinorVersion] = '0'
AND [OldProductType] = '1'
AND ([OSDescription] <> 'Windows 10' or [OSDescription] IS NULL)
    Servus
    Winfried

    Gruppenrichtlinien
    HowTos zum WSUS Package Publisher
    WSUS Package Publisher
    HowTos zum Local Update Publisher
    NNTP-Bridge für MS-Foren

    • Proposed as answer by Steven_Lee0510 Sunday, October 11, 2015 10:34 AM
    • Marked as answer by Steven_Lee0510 Sunday, October 11, 2015 1:27 PM
    Wednesday, September 2, 2015 4:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Unfortunately this is a known issue, and the only options right now appear to be the database hack (which hasn't "stuck" for me), or to wait for an update.

    https://social.technet.microsoft.com/Forums/en-US/03ef4407-a055-49c0-a864-0b805963bb89/windows-10-computers-showing-on-wsus-server-2012-r2-as-windows-vista?forum=winserverwsus

    Thursday, September 3, 2015 12:04 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Hi,

    >>Any idea why WSUS flag Windows 10 as Vista?

    Microsoft has released a hot fix for this issue:

    https://support.microsoft.com/en-us/kb/3095113#/en-us/kb/3095113

    Best Regards.

    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Proposed as answer by Steven_Lee0510 Sunday, October 11, 2015 10:35 AM
    • Marked as answer by Steven_Lee0510 Sunday, October 11, 2015 1:27 PM
    Sunday, October 11, 2015 10:34 AM
  • Question
    Sign in to vote
    4
    Sign in to vote

    Hi,

    >>Any idea why WSUS flag Windows 10 as Vista?

    Microsoft has released a hot fix for this issue:

    https://support.microsoft.com/en-us/kb/3095113#/en-us/kb/3095113

    Best Regards.

    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    This hotfix appears to correct the issue on 2012 and 2012 R2 servers.  Will a similar hotfix be available for WSUS 3.0 (SP2) for networks still using WSUS on Windows 2008 servers?
    Wednesday, October 14, 2015 8:20 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    This hotfix appears to correct the issue on 2012 and 2012 R2 servers.  Will a similar hotfix be available for WSUS 3.0 (SP2) for networks still using WSUS on Windows 2008 servers?

    This would be very nice to know. We have this issue, too.

    Although - since the Mainstream Support ended for Windows Server 2008 (and R2), I don't have much hope.

    • Marked as answer by Steven_Lee0510 Monday, November 23, 2015 6:21 AM
    • Unmarked as answer by Steven_Lee0510 Monday, November 23, 2015 6:21 AM
    Thursday, November 12, 2015 10:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This hotfix appears to correct the issue on 2012 and 2012 R2 servers.  Will a similar hotfix be available for WSUS 3.0 (SP2) for networks still using WSUS on Windows 2008 servers?

    This would be very nice to know. We have this issue, too.

    Although - since the Mainstream Support ended for Windows Server 2008 (and R2), I don't have much hope.


    1+
    Friday, November 20, 2015 12:03 PM
  • Question
    Sign in to vote
    3
    Sign in to vote

    The hotfix states that it is only for server 2012.

    Is there a solution for server 2008 R2?

    Friday, November 20, 2015 12:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This hotfix appears to correct the issue on 2012 and 2012 R2 servers.  Will a similar hotfix be available for WSUS 3.0 (SP2) for networks still using WSUS on Windows 2008 servers?

    This would be very nice to know. We have this issue, too.

    Although - since the Mainstream Support ended for Windows Server 2008 (and R2), I don't have much hope.


    1+
    +1
    Friday, November 20, 2015 12:30 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Server 2008 R2 is no longer a feature supported platform, because it's in extended mode, it will never get this hotfix.

    http://blogs.technet.com/b/wsus/archive/2016/01/22/what-to-do-if-you-re-on-wsus-3-0-sp2-or-sbs-2011.aspx

    Friday, February 5, 2016 8:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did anyone have a solution for this for Windows 2008 R2 Server and WSUS 3.2?

    I don't care about the display but the Windows 10 updates are showing as "not applicable". We cannot upgrade the server due to PCI Compliance and we are patching Windows 10 IoT devices (LTSB 2016) But are showing as "not applicable" for all Windows 10 updates.

    lforbes

    Thursday, September 28, 2017 9:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    One can always upgrade to a newer platform in order to be PCI compliant.

    I would make sure that you've selected all Windows 10 categories as LTSB is a separate category of 10 updates.

    I've had to unjoin and rejoin a pc to the domain to get it to properly hook into WSUS.

    Friday, September 29, 2017 3:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    One can always upgrade to a newer platform in order to be PCI compliant.

    I would make sure that you've selected all Windows 10 categories as LTSB is a separate category of 10 updates.

    I've had to unjoin and rejoin a pc to the domain to get it to properly hook into WSUS.


    A different operating system would require paying for a brand new scan. It is very expensive and we just did it. There is no domain. We use WSUS for Windows 7 Embedded and the Windows IOT are showing up, just not finding any updates applicable. We have selected LTSB and Microsoft said the servers are supported until 2020 but it sounds like they are not.

    lforbes

    Saturday, September 30, 2017 6:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I would ensure that you select all of the Windows 10 categories.

    The only thing the older WSUS can't do is feature upgrades.  Quality updates can still be deployed by the older wsus

    Saturday, September 30, 2017 2:34 PM