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

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.
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
  • 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:
      • BUILTIN\Users:(OI)(CI)R
      • NT AUTHORITY\Authenticated Users:(OI)(CI)R
      • BUILTIN\Administrators:(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  KeyType:”IIsWebService” MaxConnections:4294967295 AnonymousUserName:”IUSR_<machinename>” AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:”DefaultAppPool” IIs5IsolationModeEnabled:False


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.


Leave a Reply