Many client computers are not self-updating. %1 have been detected so far.

Details
Product: .NET Framework
Event ID: 13012
Source: Windows Server Update Services
Version: 2.0.50727
Symbolic Name: HealthClientsInstallUpdateAgentRed
Message: Many client computers are not self-updating. %1 have been detected so far.
   
Explanation
Clients need to install or upgrade the correct version of Windows Automatic Update software.
   
User Action
Update Agent Failure

Clients are not installing updates. This may be because of configuration issues.

Possible resolutions include:

  • Check the default DCOM impersonation level on the Windows 2000 client.
    1. Start dcomcnfg.exe (in the <windir>\system32 directory).
    2. The Distributed COM Configuration Properties window appears.
    3. Click the Default Properties tab.
    4. Make sure that Enable Distributed COM on this computer is selected.
    5. Make sure that Default Impersonation Level is set to Identify.
  • Check the default DCOM impersonation level on the Windows Vista or Windows XP client.
    1. Start dcomcnfg.exe (in the <windir>\system32 directory).
    2. Under Component Services, expand the Computers node.
    3. Right-click My Computer and click Properties.
    4. Click the Default Properties tab.
    5. Make sure that Enable Distributed COM on this computer is selected.
    6. Make sure that Default Impersonation Level is set to Identify.
  • Check the default DCOM access permissions.
    1. Open a command window.
    2. Type reg delete HKLM\SOFTWARE\Microsoft\Ole /v DefaultAccessPermission /f

Verify

Look for the corresponding error event.

  1. Open a command window.
  2. Type cd <WSUSInstallDir>\Tools
  3. Type wsusutil checkhealth
  4. Type eventvwr
  5. Review the Application log for the most recent events from source Windows Server Update Services and event id 13010.

Related:

The catalog was last synchronized successfully %1 or more days ago.

Details
Product: .NET Framework
Event ID: 10021
Source: Windows Server Update Services
Version: 2.0.50727
Symbolic Name: HealthCoreCatalogSyncYellow
Message: The catalog was last synchronized successfully %1 or more days ago.
   
Explanation
WSUS catalog synchronization depends on connectivity to the upstream server or Microsoft Update.
   
User Action
Old Catalog Synchronization

The last catalog synchronization happened some time ago or was never performed.

  1. This is a reminder to synchronize the server on a regular
    basis if the synchronization schedule is set to manual.
  2. Start WSUS 3.0: Click Start, click Administrative Tools, then click Microsoft Windows Server Update Services v3.0.
  3. Click Synchronization Results.
  4. In the Action pane, click Synchronize Now.

Verify

Look for the corresponding error event.

  1. Open a command window.
  2. Type cd <WSUSInstallDir>\Tools
  3. Type wsusutil checkhealth
  4. Type eventvwr
  5. Review the Application log for the most recent events from
    source Windows Server Update Services and event id 10020.

Related:

Client computers are installing updates with a higher than %1 percent failure rate. This should be monitored.

Details
Product: .NET Framework
Event ID: 13001
Source: Windows Server Update Services
Version: 2.0.50727
Symbolic Name: HealthClientsInstallUpdatesYellow
Message: Client computers are installing updates with a higher than %1 percent failure rate. This should be monitored.
   
Explanation
Updates need to be installed properly on client computers.
   
User Action
Failed to Install Updates

See How to
troubleshoot Windows Update, Microsoft Update, and Windows Server Update
Services installation issues
.

Verify

  • You are offered an update for a product, but the update is not
    installed on your computer.
  • You are repeatedly offered an update, even if you have already installed it.
  • Installation fails for a particular update.
  • To verify the actual error:
    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent events from source Windows Server Update Services and event id 13000.
  • Related:

    Many client computers are not reporting their inventory. %1 have been detected so far.

    Details
    Product: .NET Framework
    Event ID: 13022
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: HealthClientsInventoryRed
    Message: Many client computers are not reporting their inventory. %1 have been detected so far.
       
    Explanation
    Clients report their software inventory to the server.
       
    User Action
    Client Inventory

    Client inventory collection is not working correctly.

    Possible resolutions include:

    • First, troubleshoot any issues with SQL Server before
      proceeding.
    • Troubleshoot any general issues with IIS.
    • Check permissions on the client Web service directory.
      1. Open a command window.
      2. Type cd <WSUSInstallDir>\Inventory
      3. Type cacls
      4. The following ACEs should be set:
        • NT AUTHORITY\NETWORK SERVICE:(OI)(CI)R
        • BUILTIN\Users:(OI)(CI)R
        • NT AUTHORITY\Authenticated Users:(OI)(CI)R
        • BUILTIN\Administrators:(OI)(CI)F
        • NT AUTHORITY\SYSTEM:(OI)(CI)F
    • Check the IIS configuration of the reporting Web service using the IIS script adsutil.vbs (or use the IIS Administration UI Tool).
      1. Open a command window.
      2. Locate the adsutil.vbs tool, which is typically in <InetpubDir>\AdminScripts.
      3. Locate WSUS virtual directories on the IIS server: type <InetpubDir>\AdminScripts\adsutil.vbs find path
      4. Find the path of the Inventory service (it will look like W3SVC/<WebSiteID>/ROOT/Inventory).
      5. Get the properties of the Web service: type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/<WebSiteID>/ROOT/Inventory
      6. Compare the output with typical values below (this is a partial list):
        KeyType : (STRING) “IIsWebVirtualDir”
        AppRoot : (STRING) “/LM/W3SVC/<WebSiteID>/ROOT/Inventory”
        AppFriendlyName : (STRING) “Inventory”
        AppIsolated : (INTEGER) 2
        Path : (STRING) “<WSUSInstallDir>\Inventory”
        AccessFlags : (INTEGER) 513
        AccessExecute : (BOOLEAN) False
        AccessSource : (BOOLEAN) False
        AccessRead : (BOOLEAN) True
        AccessWrite : (BOOLEAN) False
        AccessScript : (BOOLEAN) True
        AccessNoRemoteExecute : (BOOLEAN) False
        AccessNoRemoteRead : (BOOLEAN) False
        AccessNoRemoteWrite : (BOOLEAN) False
        AccessNoRemoteScript : (BOOLEAN) False
        AccessNoPhysicalDir : (BOOLEAN) False
        AspScriptErrorSentToBrowser : (BOOLEAN) False
        AspEnableParentPaths : (BOOLEAN) False
        AuthFlags : (INTEGER) 1
        AuthBasic : (BOOLEAN) False
        AuthAnonymous : (BOOLEAN) True
        AuthNTLM : (BOOLEAN) False
        AuthMD5 : (BOOLEAN) False
        AuthPassport : (BOOLEAN) False
        AppPoolId : (STRING) “WsusPool”
      7. Type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/1
      8. Compare output with typical values below. This is a partial listing. For more information, see “Appendix C: IIS Settings for Web Services” in the WSUS 3.0 Operations Guide at http://go.microsoft.com/fwlink/?LinkId=81072  KeyType:”IIsWebService” MaxConnections:4294967295 AnonymousUserName:”IUSR_<machinename>” AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:”DefaultAppPool” IIs5IsolationModeEnabled:False

    Verify

    Look for the corresponding error event.

    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent events from
      source Windows Server Update Services and event id 13020.

    Related:

    The Windows Server Update Server Service has stopped.

    Details
    Product: .NET Framework
    Event ID: 502
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: WsusServiceStopped
    Message: The Windows Server Update Server Service has stopped.
       
    Explanation
    The WSUS service must be running.
       
    User Action
    WSUS Service

    The WSUS service “Update Services” is stopped.

    Possible resolutions include:

    • The Update Services service has been manually stopped. Start the service.
    1. Open a command window.
    2. Type sc start wsusservice
  • The Update Services service is set to manual and is stopped.
    1. Open a command window.
    2. Type sc config wsusservice start= auto
    3. Type sc start wsusservice
  • The Update Services service failed to start. Review the NT event log for issues that occurred before this event (for example, the SQL database or IIS) and resolve them. Then start the service.
    1. Open a command window.
    2. Type sc start wsusservice

    Verify

    Look for the corresponding error event.

    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent events from
      source Windows Server Update Services and event id 501.

    Related:

    The Windows Server Update Server Service has started.

    Details
    Product: .NET Framework
    Event ID: 501
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: WsusServiceStarted
    Message: The Windows Server Update Server Service has started.
       
    Explanation
    The WSUS service must be running.
       
    User Action

    This message is for informational purposes only. No user action is required.

    Related:

    The Reporting Web Service is not working.

    Details
    Product: .NET Framework
    Event ID: 53534
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: HealthWebServicesReportingRed
    Message: The Reporting Web Service is not working.
       
    Explanation
    The Reporting Web Service collects information on the state of installations and update history from each client.
       
    User Action
    Reporting Web Service Configuration

    The Reporting Web service is not working correctly. This may be because of configuration issues.

    Possible resolutions include:

    • First, troubleshoot any issues with SQL Server before proceeding.
    • Troubleshoot any general issues with IIS.
    • Check permissions.
      1. Open a command window.
      2. Type cd <WSUSInstallDir>\WebServices\ReportingWebService
      3. Type cacls
      4. The following ACEs should be set:
        • NT AUTHORITY\NETWORK SERVICE:(OI)(CI)R
        • BUILTIN\Users:(OI)(CI)R
        • NT AUTHORITY\Authenticated Users:(OI)(CI)R
        • BUILTIN\Administrators:(OI)(CI)F
        • NT AUTHORITY\SYSTEM:(OI)(CI)F
    • Check the IIS configuration of the Reporting Web service using the IIS script adsutil.vbs (or use the IIS Administration UI Tool).
    1. Open a command window.
    2. Locate the adsutil.vbs tool, which is typically in <InetpubDir>\AdminScripts.
    3. Locate WSUS virtual directories on the IIS server: type <InetpubDir>\AdminScripts\adsutil.vbs find path
    4. Find the path of the ReportingWebService (it will look like W3SVC/<WebSiteID>/ROOT/ReportingWebService).
    5. Get the properties of the Web service: type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/<WebSiteID>/ROOT/ReportingWebService
    6. Compare the output with typical values below (this is a partial list): KeyType:”IIsWebVirtualDir” AppRoot :”/LM/W3SVC/<WebSiteID>/ROOT/ReportingWebService” AppFriendlyName:”ReportingWebService” AppIsolated:2 Path :”<WSUSInstallDir>\WebServices\ReportingWebService” AccessFlags:513 AccessExecute:False AccessSource:False AccessRead:True AccessWrite:False AccessScript:True AccessNoRemoteExecute:False AccessNoRemoteRead:False AccessNoRemoteWrite:False AccessNoRemoteScript:False AccessNoPhysicalDir:False AspScriptErrorSentToBrowser:False AspEnableParentPaths: False AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:”WsusPool” 
    7. type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/1
    8. Compare the output with typical values below  (this is a partial list).
    9. KeyType:”IIsWebServer” ServerState:2 ServerComment:”Default Website” ServerSize:1 ServerBindings:”:80:” SecureBindings:”:443:” ConnectionTimeout:180 DefaultDoc:”Default.htm,Default.asp,index.htm,iisstart.htm” AspBufferingOn:False LogPluginClsid:”{FF160663-DE82-11CF-BC0A-00AA006111E0}” Win32Error:0 AppPoolId:”DefaultAppPool”

    10. Type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC
    11. Compare output with typical values below. This is a partial listing. For more information, see “Appendix C: IIS Settings for Web Services” in the WSUS 3.0 Operations Guide at http://go.microsoft.com/fwlink/?LinkId=81072  KeyType:”IIsWebService” MaxConnections:4294967295 AnonymousUserName:”IUSR_<machinename>” AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:”DefaultAppPool” IIs5IsolationModeEnabled:False

    Verify

    Look for the corresponding error event.

    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent events from
      source Windows Server Update Services and

    Related:

    The DSS Authentication Web Service is not working.

    Details
    Product: .NET Framework
    Event ID: 12052
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: HealthWebServicesDssAuthRed
    Message: The DSS Authentication Web Service is not working.
       
    Explanation
    The Downstream Server Authentication Web service provides authentication of downstream servers.
       
    User Action
    DSS Authentication Web Service Configuration

    Downstream server authentication service is not working end to end. This may be because of configuration issues.

    Possible resolutions include:

    • First, troubleshoot any issues with SQL Server before proceeding.
    • Troubleshoot any general issues with IIS.
    • Check permissions.
      1. Open a command window.
      2. Type cd <WSUSInstallDir>\WebServices\DssAuthWebService
      3. Type cacls
      4. The following ACEs should be set:
        • NT AUTHORITY\NETWORK SERVICE:(OI)(CI)R
        • BUILTIN\Users:(OI)(CI)R
        • NT AUTHORITY\Authenticated Users:(OI)(CI)R
        • BUILTIN\Administrators:(OI)(CI)F
        • NT AUTHORITY\SYSTEM:(OI)(CI)F
    • Check the IIS configuration of the reporting Web service using the IIS script adsutil.vbs (or use the IIS Administration UI Tool).
    1. Open a command window.
    2. Locate the adsutil.vbs tool, which is typically in <InetpubDir>\AdminScripts.
    3. Locate WSUS virtual directories on the IIS server: type <InetpubDir>\AdminScripts\adsutil.vbs find path
    4. Find the path of the DssAUthWebService (it will look like W3SVC/<WebSiteID>/ROOT/DssAuthWebService).
    5. Get the properties of the web service: type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/<WebSiteID>/ROOT/DssAuthWebService
    6. Compare the output with typical values below (this is a partial list): KeyType:”IIsWebVirtualDir” AppRoot:”/LM/W3SVC/<WebSiteID>/ROOT/DssAuthWebService” AppFriendlyName:”DssAuthWebService” AppIsolated:2 Path: “<WSUSInstallDir>\WebServices\DssAuthWebService” AccessFlags:513 AccessExecute:False AccessSource:False AccessRead:True AccessWrite:False AccessScript:True AccessNoRemoteExecute:False AccessNoRemoteRead:False AccessNoRemoteWrite:False AccessNoRemoteScript:False AccessNoPhysicalDir:False AspScriptErrorSentToBrowser:False AspEnableParentPaths:False AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:WsusPool”
    7. Type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/1
    8. Compare the output with typical values below  (this is a partial list).
    9. KeyType:”IIsWebServer” ServerState2 ServerComment:”Default Website” ServerSize:1 ServerBindings:”:80:” SecureBindings:”:443:” ConnectionTimeout:180 DefaultDoc:”Default.htm,Default.asp,index.htm,iisstart.htm” AspBufferingOn:False LogPluginClsid:”{FF160663-DE82-11CF-BC0A-00AA006111E0}” Win32Error:0 AppPoolId:”DefaultAppPool”

    10. Type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC
    11. Compare output with typical values below. This is a partial listing. For more information, see “Appendix C: IIS Settings for Web Services” in the WSUS 3.0 Operations Guide at http://go.microsoft.com/fwlink/?LinkId=81072  KeyType:”IIsWebService” MaxConnections:4294967295 AnonymousUserName:”IUSR_<machinename>” AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:”DefaultAppPool” IIs5IsolationModeEnabled:False

    Verify

    Look for the corresponding error event.

    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent events from source Windows Server Update Services a

    Related:

    The SimpleAuth Web Service is not working.

    Details
    Product: .NET Framework
    Event ID: 12042
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: HealthWebServicesSimpleAuthRed
    Message: The SimpleAuth Web Service is not working.
       
    Explanation
    The Simple Web Authentication Service provides authentication between the upstream and downstream WSUS servers.
       
    User Action
    Simple Web Authentication Configuration

    Simple authentication for client-to-server synchronization is not working properly. Downstream servers will not able to synchronize catalog or content with this server.

    Possible resolutions include:

    • First, troubleshoot any issues with SQL Server before proceeding.
    • Check permissions.
      1. Open a command window.
      2. Type cd <WSUSInstallDir>\WebServices\SimpleAuthWebService
      3. Type cacls
      4. The following ACEs should be set:
        • NT AUTHORITY\NETWORK SERVICE:(OI)(CI)R
        • BUILTIN\Users:(OI)(CI)R
        • NT AUTHORITY\Authenticated Users:(OI)(CI)R
        • BUILTIN\Administrators:(OI)(CI)F
        • NT AUTHORITY\SYSTEM:(OI)(CI)F
    • Check the IIS configuration of the reporting Web service using the IIS script adsutil.vbs.
    1. Open a command window.
    2. Locate the adsutil.vbs tool, which is typically in <InetpubDir>\AdminScripts.
    3. Locate WSUS virtual directories on the IIS server: type <InetpubDir>\AdminScripts\adsutil.vbs find path
    4. Find the path of the SimpleAuthWebService (it will look like W3SVC/<WebSiteID>/ROOT/SimpleAuthWebService).
    5. Get the properties of the Web service: type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/<WebSiteID>/ROOT/SimpleAuthWebService
    6. Compare the output with typical values below (this is a partial list): KeyType:”IIsWebVirtualDir” AppRoot:”/LM/W3SVC/<WebSiteID>/ROOT/SimpleAuthWebService” AppFriendlyName:”SimpleAuth WebService” AppIsolated:2 Path:”<WSUSInstallDir>\WebServices\SimpleAuth WebService” AccessFlags:513 AccessExecute:False AccessSource:False AccessRead:True AccessWrite:False AccessScript:True AccessNoRemoteExecute:False AccessNoRemoteRead:False AccessNoRemoteWrite:False AccessNoRemoteScript:False AccessNoPhysicalDir:False AspScriptErrorSentToBrowser: alse AspEnableParentPaths:False AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTL:False AuthMD5:False AuthPassport:False AppPoolId:”WsusPool”
    7. Type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/1
    8. Compare the output with typical values below (this is a partial list).
    9. KeyType:”IIsWebServer” ServerState:2 ServerComment:”Default Website” ServerSize:1 ServerBindings:”:80:” SecureBindings:”:443:” ConnectionTimeout:180 DefaultDoc:”Default.htm,Default.asp,index.htm,iisstart.htm” AspBufferingOn:False LogPluginClsid:”{FF160663-DE82-11CF-BC0A-00AA006111E0}” Win32Error:0 AppPoolId:”DefaultAppPool”

    10. Type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC
    11. Compare output with typical values below. This is a partial listing. For more information, see “Appendix C: IIS Settings for Web Services” in the WSUS 3.0 Operations Guide at http://go.microsoft.com/fwlink/?LinkId=81072  KeyType:”IIsWebService” MaxConnections:4294967295 AnonymousUserName:”IUSR_<machinename>” AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:”DefaultAppPool” IIs5IsolationModeEnabled:False

    Verify

    Look for the corresponding error event.

    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent eve

    Related:

    Client computers are installing updates with a higher than %1 percent failure rate. This is not normal.

    Details
    Product: .NET Framework
    Event ID: 13002
    Source: Windows Server Update Services
    Version: 2.0.50727
    Symbolic Name: HealthClientsInstallUpdatesRed
    Message: Client computers are installing updates with a higher than %1 percent failure rate. This is not normal.
       
    Explanation
    Updates need to be installed properly on client computers.
       
    User Action
    Failed to Install Updates

    See How to
    troubleshoot Windows Update, Microsoft Update, and Windows Server Update
    Services installation issues
    .

    Verify

  • You are offered an update for a product, but the update is not
    installed on your computer.
  • You are repeatedly offered an update, even if you have already installed it.
  • Installation fails for a particular update.
  • To verify the actual error:
    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent events from source Windows Server Update Services and event id 13000.
  • Related: