locked
WSUS 6 upstream server will support WSUS 3 SP2 downstream server or not RRS feed

  • Question

  • In our company WSUS upstream server operating system is windows 2012 r2. I would like to know can we install downstream server in windows 2008 r2 (WSUS 3.0 sp2) it will download approved patches from upstream server.

    WSUS 6 upstream server will support WSUS 3.0 SP2 downstream or not? 







    Sunday, December 7, 2014 7:06 AM

Answers

  • I installed kb2734608 in upstream, downsteam and synchronized, still below error showing when opening WSUS console & event viewer e.t.c.

    Well, I contributed to this confusion because I'd forgotten the original premise in the thread which was that your upstream server was running Windows Server 2012 R2, so KB2734608 is Not Applicable to that system so you could not have possibly installed it on the upstream server. My apologies for contributing to that confusion.

    So, assuming that KB2734608 was installed to your downstream server **BEFORE** synchronizing with the Windows Server 2012 R2-based upstream server, and assuming that the server was otherwise operational after installing KB2734608 ... except for the console not being able to connect.

    I'm inclined to believe that the installation of K2734608 actually was not successful.

    Take a look at this article (about KB2720211 issues) and rule out all known possibilities for issues known to occur when updating a WSUS v3 server.

    http://blogs.technet.com/b/sus/archive/2012/06/20/wsus-kb272011-common-issues-encountered-and-how-to-fix-them.aspx


    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.

    • Marked as answer by Steven_Lee0510 Monday, December 22, 2014 3:09 PM
    Monday, December 15, 2014 9:24 PM

All replies

  • In our company WSUS upstream server operating system is windows 2012 r2. I would like to know can we install downstream server in windows 2008 r2 (WSUS 3.0 sp2) it will download approved patches from upstream server

    Yes; however, it is absolutely required that you install KB2734608 to your WSUS v3 server before synchronizing with the WSUS v6 upstream server. As such, it will be necessary for you to NOT allow the launch of the "first synchronization" during the setup wizard, but rather exit the setup wizard, install the update, and then launch the first synchronization.

    WSUS 4.0 upstream server

    For the record, WSUS on Windows Server 2012 is Version 6. There is no such thing as WSUS v4.

    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.

    • Proposed as answer by DonPick Monday, December 8, 2014 8:04 AM
    • Marked as answer by mahmoodbalhaq Monday, December 8, 2014 9:12 AM
    • Unmarked as answer by mahmoodbalhaq Monday, December 8, 2014 9:12 AM
    Sunday, December 7, 2014 1:54 PM
  • After installing KB2734608 on my 2008r2 wsus3sp2 downstream server. Snap-in is not responding when opening wsus console below is the error:

    This snap-in is not responding.

    To return to MMC and check the status of the snap-in, click Cancel.

    If you choose to end the snap-in emmediately, you will lose any unsaved data. To end the snap-in now, click End Now.


    • Edited by mahmoodbalhaq Monday, December 8, 2014 9:16 AM After installing KB2734608 snap-in is not responding.
    Monday, December 8, 2014 9:12 AM
  • After installing KB2734608 on my 2008r2 wsus3sp2 downstream server. Snap-in is not responding when opening wsus console below is the error:

    Did you perform the required post-installation instructions documented in the KB article?

    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.

    Monday, December 8, 2014 1:27 PM
  • If i am wrong please collect me.

    No post-installation instruction in the KB article. Just i install kb2734608, please guide me how to fix snap-in is not responding.

    http://support.microsoft.com/kb/2734608


    Tuesday, December 9, 2014 6:27 AM
  • No post-installation instruction in the KB article.

    Then you should READ the article again. Let me help:

    How to apply this update



    We recommend that you synchronize all WSUS servers after you apply this update. If you have a hierarchy of WSUS servers, apply this update, and then synchronize your servers from the top of the hierarchy on down. To synchronize your servers in this manner, follow these steps:

    Note Before computers that are running Windows 8 or Windows Server 2012 can be updated by WSUS 3.2 servers, you must complete these steps.
    1. Start the process with WSUS 3.0 SP2 that synchronizes with Microsoft Update.
    2. Apply this update.
    3. Start a synchronization.
    4. Wait for the synchronization to succeed.
    5. Repeat steps 2 through 4 for each WSUS 3.0 SP2 server that synchronizes to the server that you just updated.

    Known issues with this update

    • If you have Windows 8 or Windows Server 2012 clients that synchronized with WSUS 3SP2 before you applied this update, wait for the update to be applied to the WSUS servers, and then follow these steps:
      1. On the affected client, open cmd.exe in elevated mode
      2. Type the following commands. Make sure that you press Enter after you type each command:

        Net stop wuauserv

        rd /s %windir%\softwaredistribution\

        Net start wuauserv

    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.

    Tuesday, December 9, 2014 3:33 PM
  • I think post-installation instruction in the KB article is telling How to apply this update for Upstream server (synchronize with Microsoft Update). I applied update in downstream server WSUS 3.0 SP2.

    Tuesday, December 9, 2014 5:47 PM
  • I think post-installation instruction in the KB article is telling How to apply this update for Upstream server (synchronize with Microsoft Update). I applied update in downstream server WSUS 3.0 SP2.

    You cannot apply this update to "just a downstream server". It must be installed to **ALL** WSUS Servers AND CONSOLES in the environment at the same time.

    The instructions apply to **ALL** WSUS Servers!!! Did you read the very first sentence?

    We recommend that you synchronize all WSUS servers after you apply this update.


    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.

    Wednesday, December 10, 2014 1:10 PM
  • I installed kb2734608 in upstream, downsteam and synchronized, still below error showing when opening WSUS console & event viewer e.t.c.

    This snap-in is not responding.

    To return to MMC and check the status of the snap-in, click Cancel.

    If you choose to end the snap-in immediately, you will lose any unsaved data. To end the snap-in now, click End Now.

    Monday, December 15, 2014 8:00 AM
  • I installed kb2734608 in upstream, downsteam and synchronized, still below error showing when opening WSUS console & event viewer e.t.c.

    Well, I contributed to this confusion because I'd forgotten the original premise in the thread which was that your upstream server was running Windows Server 2012 R2, so KB2734608 is Not Applicable to that system so you could not have possibly installed it on the upstream server. My apologies for contributing to that confusion.

    So, assuming that KB2734608 was installed to your downstream server **BEFORE** synchronizing with the Windows Server 2012 R2-based upstream server, and assuming that the server was otherwise operational after installing KB2734608 ... except for the console not being able to connect.

    I'm inclined to believe that the installation of K2734608 actually was not successful.

    Take a look at this article (about KB2720211 issues) and rule out all known possibilities for issues known to occur when updating a WSUS v3 server.

    http://blogs.technet.com/b/sus/archive/2012/06/20/wsus-kb272011-common-issues-encountered-and-how-to-fix-them.aspx


    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.

    • Marked as answer by Steven_Lee0510 Monday, December 22, 2014 3:09 PM
    Monday, December 15, 2014 9:24 PM