DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2734608 - Last Review: October 10, 2012 - Revision: 5.0

On This Page

Summary

Microsoft has released an update for Windows Server Update Services (WSUS) 3.0 Service Pack 2 (SP2). This article includes information about the contents of the update and how to obtain the update.

Issues that are fixed

This update lets servers that are running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012.

This update fixes the following issues:
  • Installation of update 2720211 may fail if Service Pack 2 was previously uninstalled and then reinstalled.
  • After you install update 2720211, health monitoring may fail if the WSUS server is configured to use SSL.

Additionally, this update includes the following fixes:
  • 2530678  (http://support.microsoft.com/kb/2530678/ ) System Center Update Publisher does not publish customized updates to a computer if WSUS 3.0 SP2 and the .NET Framework 4 are installed
  • 2530709  (http://support.microsoft.com/kb/2530709/ ) "Metadata only" updates cannot be expired or revised in WSUS 3.0 SP2
  • 2720211  (http://support.microsoft.com/kb/2720211/ ) An update for Windows Server Update Services 3.0 Service Pack 2 is available

Notes
  • Update 2720211 is included in this update and strengthens the WSUS communication channels.
  • The Windows Update Agent (WUA) on computers that are managed by this WSUS server will be automatically upgraded as needed after you apply this update. 
  • WSUS must be in a known, good working state for this update to work. If WSUS is configured to synchronize updates from Microsoft Update, make sure that WSUS can synchronize updates. And, clients must be able to communicate with the WSUS server.

    For more information about how to perform basic health checks on a WSUS server, go to the following Microsoft TechNet websites: 
    Reindex the WSUS Database (http://technet.microsoft.com/en-us/library/dd939795(v=ws.10))
    Use the Server Cleanup Wizard (http://technet.microsoft.com/en-us/library/dd939856(v=ws.10))

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 use the Local Publishing feature from a remote WSUS console, when your WSUS Server is updated with this update, the remote WSUS consoles must also be updated to make sure the API versions match.
  • If you have locally published updates, you will have to re-sign and republish all local updates after you apply this update. Be aware that a minimum of a SHA1, 1024 key-length certificate is required. For more information about how to do local publishing of updates, go to the following Microsoft Developer Network (MSDN) website:
    Local Publishing (http://msdn.microsoft.com/en-us/library/windows/desktop/bb902470(v=vs.85).aspx)
  • 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
  • Consider the following scenario:
    • You connect to Windows Update through a network proxy that uses HTTPS or SSL content inspection.
    • An intermediate server is between the SSL traffic of the client and Microsoft Update.

    In this scenario, you have to create exception rules in the HTTPS inspection server so that the Windows Update traffic is tunneled without inspection. For more information about how to create HTTPS inspection exceptions for Microsoft Forefront Threat Management Gateway (TMG), go to the following Microsoft website:
    Excluding sources and destinations from HTTPS inspection (http://technet.microsoft.com/en-us/library/dd441085.aspx)
    For a list of URLs and domains to exclude, click the following article number to view the article in the Microsoft Knowledge Base:
    885819  (http://support.microsoft.com/kb/885819/ ) You experience problems when you access the Windows Update Version 6 website through a server that is running ISA Server
  • If you install the executable file (.exe) manually, you will have to restart the computer to apply the update.
  • Remote Microsoft SQL Server administrators must download and install the update by using an account that has SQL Server Administrator permissions. SQL Server installation will always require manual installation.
  • To apply this update, you must be running Windows Internal Database or SQL Server.
  • The IIS and WSUS services must be stopped to prevent the database from being accessed while the Network Load Balancing (NLB) clusters are upgraded. For more information about how to upgrade NLB, see the "How to upgrade NLB on all computers" section.

How to upgrade NLB on all computers

  1. Shut down the NLB service on each node in the NLB cluster. To do this, at a command prompt, type the following command, and then press Enter: 
    nlb.exe suspend
  2. Shut down IIS and the WSUS service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
    iisreset/stop

    net stop wsusservice
  3. Make sure that no other services can access the database during the upgrade window. To do this, at a command prompt, type nlb.exe disable together with the appropriate additional parameters for the port or application:
    disable {vip[{:Port | :all}] | all[{:Port | :all}]} {Cluster[:{Host]| all {local | global}}}
    Note In this step and in the following steps, press Enter every time that you type a command at a command prompt.
  4. Back up your database. For more information about how to back up a SQL Server database, go to the following Microsoft website:
    How to: Back Up a Database (SQL Server Management Studio) (http://msdn.microsoft.com/en-us/library/ms187510(v=sql.105).aspx)
  5. Upgrade each front-end computer individually. To do this, follow these steps:
    1. Set up WSUS. To do this, at a command prompt, type one of the following commands, as applicable to your system:
      • WSUS-KB2734608-x64.exe /q C:\MySetup.log
      • WSUS-KB2734608-x86.exe /q C:\MySetup.log

      The update will install immediately, without any prompts.
    2. Review the setup log to verify that the upgrade was successful. To do this, at a command prompt, type C:\MySetup.log.
    3. Make sure that IIS and the WSUS service are stopped. To do this, at a command prompt, type the following commands:
      iisreset/stop

      net stop wsusservice
    4. Continue to the next computer.
  6. After all nodes are upgraded, start IIS and the WSUS service. To do this, at a command prompt, type iisreset, and then type net start wsusservice on each node in the NLB cluster.
  7. Start the NLB service on each node in the NLB cluster. To do this, at a command prompt, type nlb.exe resume.
  8. At a command prompt, type nlb.exe enable for all the ports or applications that you disabled in step 3.
Note You must restart the computer after you apply this update.

Update information

The following files are available for download from the Microsoft Download Center:

Update for Windows Server Update Services 3.0 SP2 (KB2734608)
Collapse this imageExpand this image
Download
Download the update package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=0260e193-2f15-46cb-a265-2618369491a9)
Update for Windows Server Update Services 3.0 SP2 for x64-based Systems (KB2734608)
Collapse this imageExpand this image
Download
Download the update package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=e13c25d6-e886-459b-9617-3abfb3765e8f)

Prerequisites

You must have Windows Server Update Services 3.0 SP2 installed to apply this update.

For more information about Service Pack 2 for Windows Server Update Services 3.0, click the following article number to view the article in the Microsoft Knowledge Base:
972455  (http://support.microsoft.com/kb/972455/ ) Description of Windows Server Update Services 3.0 Service Pack 2

Restart information

You must restart the computer after you apply this update.

Replacement information

This update does not replace a previously released update.

File information

Hash values
Collapse this tableExpand this table
File nameSizeSHA1 SHA2
WSUS-KB2734608-x86.exe30,431,944C6E9AC3F3F8B332990485CF17CC57D3A358E33CDAACCE64CD0375F35AE0FCAB6B9F77B9D7633ABD7BCE231514F3C542E9785CDD2
WSUS-KB2734608-x64.exe30,508,728E399B2DED2DC6540BF51585041063CFCA48DCC3210BB6394962E8230AC9C893200DF7DF9380291EA43C77D03DF89F922C8B155C5


References

For more information about Windows Server Update Services, go to the following Microsoft TechNet website:
General information about Windows Server Update Services (http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx)
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

Applies to
  • Windows Server Update Services 3.0 Service Pack 2
Keywords: 
kbfix kbbug kbupdate kbexpertiseinter kbsurveynew KB2734608
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support