https://community.hpe.com/t5/server-management-systems/wbem-issues/m-p/4505543#M39043 On a couple of our servers, the discovery process does not discover WBEM as a protocol running on the servers. These are G4 -360 &amp; 380 models. I have verified the systems are running the latest WBEM providers. In fact the system management home pages are working with WBEM as the data source. I cannot find any documentation that can help me with this one.<BR /> Wed, 30 Sep 2009 11:10:49 GMT Sven_11 2009-09-30T11:10:49Z https://community.hpe.com/t5/server-management-systems/wbem-issues/m-p/4505543#M39043 On a couple of our servers, the discovery process does not discover WBEM as a protocol running on the servers. These are G4 -360 &amp; 380 models. I have verified the systems are running the latest WBEM providers. In fact the system management home pages are working with WBEM as the data source. I cannot find any documentation that can help me with this one.<BR /> Wed, 30 Sep 2009 11:10:49 GMT https://community.hpe.com/t5/server-management-systems/wbem-issues/m-p/4505543#M39043 Sven_11 2009-09-30T11:10:49Z https://community.hpe.com/t5/server-management-systems/wbem-issues/m-p/4505544#M39044 update:<BR /><BR />I found these error messages in the wbemess.log:<BR /><BR />Unable to activate event filter with invalid class name 'HP_AlertIndication' (error 80041002). The filter is not active<BR /><BR />Could not activate filter select * from HP_AlertIndication in namespace //./root/CIMV2. HR=0x80041010<BR /><BR />Aso, in the windows application event log were a couple of these messages with different provider names:<BR /><BR />A provider, HPWMIFCA_InstProv, has been registered in the WMI namespace, root\HPQ, 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.<BR /> Wed, 30 Sep 2009 11:38:23 GMT https://community.hpe.com/t5/server-management-systems/wbem-issues/m-p/4505544#M39044 Sven_11 2009-09-30T11:38:23Z