none
Manage Windows 8.1/ Windows Server 2012 R2 on WSUS 3.0

    질문

  • If I try to manage Windows 8.1 client on WSUS 3.0, 

    On the WSUS admin console, Windows 8.1 client is not displayed as Windows 8.1, displayed as Windows +build #.

    To display Windows 8.1 on WSUS admin console, is there any plan to release hotfix or patch to resolve this issue?


    2013년 11월 1일 금요일 오후 11:21

답변

  • If I try to manage Windows 8.1 client on WSUS 3.0, 

    This is a known issue.

    WSUS v3 cannot currently manage Windows 8.1 or Windows Server 2012 R2 systems, for the same reason it couldn't manage Windows 8.0 or Windows Server 2012 systems when they were first released. Each time Microsoft releases a new operating system, WSUS needs to be updated to recognize those new versions.

    With Windows 7 and Windows Server 2008 R2 we got a WSUS Service Pack concurrent with the release of the operating systems.

    With two different builds of WSUS to support now, it seems that WSUS v3 is getting the short end of the stick regarding code updates to support new releases. Nonetheless, given how long it's been since 8.1/2012R2 was *RTM*, I'm really disappointed that we don't yet have a patch for WSUS v3 to support those systems. It's not like they didn't know way ahead of time that it was going to be an issue, as it had been with the release of all previous operating systems.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    2013년 11월 2일 토요일 오후 8:00
    중재자
  • I installed these updates:

    Update for Windows Server Update Services 3.0 SP2 for x64-based Systems (KB2720211)
    Update for Windows Server Update Services 3.0 SP2 for x64-based Systems (KB2734608)

    Then re-indexed the DB and ran Server Cleanup

    Solve my problem for Windows 8.X and Server 2012


    Gregory N. Brooks Secure Data Inc. gregory.brooks@securedatainc.com

    2013년 11월 21일 목요일 오후 6:53

모든 응답

  • If I try to manage Windows 8.1 client on WSUS 3.0, 

    This is a known issue.

    WSUS v3 cannot currently manage Windows 8.1 or Windows Server 2012 R2 systems, for the same reason it couldn't manage Windows 8.0 or Windows Server 2012 systems when they were first released. Each time Microsoft releases a new operating system, WSUS needs to be updated to recognize those new versions.

    With Windows 7 and Windows Server 2008 R2 we got a WSUS Service Pack concurrent with the release of the operating systems.

    With two different builds of WSUS to support now, it seems that WSUS v3 is getting the short end of the stick regarding code updates to support new releases. Nonetheless, given how long it's been since 8.1/2012R2 was *RTM*, I'm really disappointed that we don't yet have a patch for WSUS v3 to support those systems. It's not like they didn't know way ahead of time that it was going to be an issue, as it had been with the release of all previous operating systems.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    2013년 11월 2일 토요일 오후 8:00
    중재자
  • You can still manage the systems, even though they show up with the wrong name. There will be another update to WSUS v3 and on WS2012, and it will bundle together a variety of fixes.
    2013년 11월 3일 일요일 오후 6:18
    중재자
  • When? My 8.1 clients error out when trying to get updates from WSUS.

    Gregory N. Brooks Secure Data Inc. gregory.brooks@securedatainc.com

    2013년 11월 19일 화요일 오후 7:22
  • When? My 8.1 clients error out when trying to get updates from WSUS.

    Have you installed KB2734608 on the WSUS server and performed the required post-installation steps?

    What error(s) are you getting? Perhaps they're not related to this thread's question?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • 답변으로 제안됨 Adam Brook- 2014년 2월 11일 화요일 오후 1:34
    2013년 11월 21일 목요일 오후 6:14
    중재자
  • I installed these updates:

    Update for Windows Server Update Services 3.0 SP2 for x64-based Systems (KB2720211)
    Update for Windows Server Update Services 3.0 SP2 for x64-based Systems (KB2734608)

    Then re-indexed the DB and ran Server Cleanup

    Solve my problem for Windows 8.X and Server 2012


    Gregory N. Brooks Secure Data Inc. gregory.brooks@securedatainc.com

    2013년 11월 21일 목요일 오후 6:53
  • I have the same display issue, and nothing suggested here has fixed the discovery issue. I have a server with this definition in the AD object "Windows Server 2012 R2 Standard" Verson=6.3 (9600)

    WSUS server is running version 3.2.7600.256 on a 2008 R2 Standard OS x64 VM

    1. Installed the KB2734608 and KB2720211 patch on the WSUS server
    2. Reindexed the DB
    3. Ran Server cleanup
    4. Rebooted the WSUS server
    5. Deleted the WSUS record of the endpoint on the WSUS server
    6. Ran the post KB2734608 steps on the WSUS client
      - On the affected client, opened cmd.exe in elevated mode
      - Net stop wuauserv
      - rd /s %windir%\softwaredistribution\
      - Net start wuauserv
    7. Ran   wuauclt /resetauthorization /detectnow   to force the client to register itself with WSUS

    Still shows "Windows 6.3" as the OS

    On the positive side, WSUS seems to be updating the endpoint correctly, however I thought the solution posted here was said to fix the display issue of "Windows 6.3" in the console. Or was I mistaken in your post Gregory?

    2014년 1월 10일 금요일 오후 2:44
  • I have also done the same steps as Justin, but continue to see Windows 6.3.
    2014년 1월 10일 금요일 오후 3:16
  • WSUS server is running version 3.2.7600.256

    Your observations are absolutely correct.

    It's not a correctable issue at this time. It's a *COSMETIC* only issue.

    It will get fixed in the next update to WSUS v3.2.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    2014년 1월 10일 금요일 오후 5:22
    중재자
  • Question: Have you installed KB2734608 on the WSUS server and performed the required post-installation steps?

    Yes I did. See previous post.


    Gregory N. Brooks Secure Data Inc. gregory.brooks@securedatainc.com

    2014년 1월 10일 금요일 오후 8:17
  • Question to me: On the positive side, WSUS seems to be updating the endpoint correctly, however I thought the solution posted here was said to fix the display issue of "Windows 6.3" in the console. Or was I mistaken in your post Gregory?

    Answer: I am able to update now. I don't care about the display at this point, just that it works. It is updating.

    Thanks


    Gregory N. Brooks Secure Data Inc. gregory.brooks@securedatainc.com

    2014년 1월 10일 금요일 오후 8:19