Ask a questionAsk a question
 

QuestionClient does not report Windows updates status

  • Friday, October 30, 2009 2:15 PMPeter Kavelaars Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have a couple of servers, they do not report their software updates list to the SCCM Site. It looks like a WMI problem, because when installing the SCCM client, I get a number of WMI warnings in the Event Viewer, see below:

    Event ID: 63

    A provider, SMSDiskInstProvider, has been registered in the WMI namespace, root\cimv2\sms, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

    Event ID: 5603

    A provider, BcdProv, has been registered in the WMI namespace, root\wmi, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.

    When I searching the SCCM client logs, I found the next messages:

    Execmgr.log:

    Software Distribution Site Settings for the client are missing from WMI.

    InventoryAgent.log:

    Collection: Class "Win32_PatchState_Extended" does not exist out.

    I rebuild WMI but it did not help. Please help

All Replies

  • Friday, October 30, 2009 3:48 PMSherry KissingerMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Those events are ok; just notifications about security rights.  NBD

    execmgr.log: on a new client install, settings missing from WMI are expected and normal, because policies haven't arrived yet (telling the client to enable SW Distribution for example).

    InventoryAgent.log: win32_patchstate_extended : as a ConfigMgr client, you'll never get data in there anymore.  That's legacy for ITMUv2 or ITMUv3.  It's still in the mof in case you have SMS2003 clients in your hierarchy, which would use ITMUv3 to report patch state.  You don't use ITMU anymore for ConfigMgr clients--you use Software Update Management.  Which isn't reported via traditional hinv / inventoryagent.log

    Forget any reports you may have using the PatchstateEX views from SMS2003 (if you have any).  Confirm you have Software Update Points enabled, and WSUS settings enabled.  That's what you need to use for your ConfigMgr clients; and then check the reports for Software Updates.
    Standardize. Simplify. Automate.