I can connect the remote servers with wbemtest using the scom action account,  query is correct returns the results I want, however all the servers report Module was unable to connect to cimv2 on my wmi performance rules.  I must be missing something because I don't see too much on this, and I have checked all the tips I am at a lost.  I have an all 2012 environment. Please help.

Can someone please help me with this.  I am in a serious block here.  What would cause me to be able to complete the full query using wbemtest from the scom server as the scom action account to all my remote server however SCCM throws the above error when i create a wmi rule.   I must be missing something please help, everyone is skipping my post today.

Hi 

is you monitoring is agent less ? as you are querying remote server using wmi.. if yes have you enabled agent proxy on the agent server ? 

also can you post xml configuration of rule and Discovery and error details.

refer below link for agent less monitoring

http://www.ms-opsmgr.eu/?p=332 

http://blog.tyang.org/2012/01/27/scom-process-performance-collection-rule-for-services/

Regards

I am not totally sure what you are needing help with, and your second reply does not help as you mention "SCCM throws the above error when I create a wmi rule" when you first ask about a WMI performance rule in SCOM.

So which product do you have a question about, SCCM, or SCOM, and what specifically are you having problems with? A SCOM rule to collect WMI Performance or a SCCM collection problem?

If it is SCCM, I'll be glad to move this thread to the SCCM area.

Thank you,
Scott Moss

Sorry my mistake the product is SCOM.  Its a wmi rule.  The rule is running against a agent managed win 2012 server.  The scom action account has administrator privilege on that server.  I can run the wmi query remotely from the scom server to target with no issues using the scom action account.  however scom server reports the error in the subject.

Alert context

Time window start	7/21/2015 7:28:33 PM
Time window end	7/21/2015 8:28:32 PM
Time First	7/21/2015 7:28:33 PM
Time Last	7/21/2015 7:39:30 PM
Count	3

Context

Date and Time: 7/21/2015 7:39:30 PM Log Name: Operations Manager Source: Health Service Modules Event Number: 10353 Level: 2 Logging Computer: DATA.techninja.local User: N/A

Description: Module was unable to connect to cimv2 This has happened 145 times since this instance was loaded. Error: 0x8004100e One or more workflows were affected by this. Workflow name: MomUIGeneratedRule7808a3993d3d429f9bf68fe7aacd9afa Instance name: DATA.techninja.local Instance ID: {7A37EAC5-9001-946C-51CD-F4F14157AD16} Management group: Ninja Monitor

Event Data:

< DataItem type =" System.XmlData " time =" 2015-07-21T19:39:30.0237093-04:00 " sourceHealthServiceId =" 2A56B99C-6490-A768-BA63-A87379586170 " > < EventData >   < Data > Ninja Monitor </ Data >   < Data > MomUIGeneratedRule7808a3993d3d429f9bf68fe7aacd9afa </ Data >   < Data > DATA.techninja.local </ Data >   < Data > {7A37EAC5-9001-946C-51CD-F4F14157AD16} </ Data >   < Data > cimv2 </ Data >   < Data > 145 </ Data >   < Data > 0x8004100e </ Data >   </ EventData >

  </DataItem >

  Thank you so much for assisting I am in a bind here.

• Edited by bigbluestar 7 hours 17 minutes ago

Sorry my mistake the product is SCOM.  Its a wmi rule.  The rule is running against a agent managed win 2012 server.  The scom action account has administrator privilege on that server.  I can run the wmi query remotely from the scom server to target with no issues using the scom action account.  however scom server reports the error in the subject.

Alert context

Time window start	7/21/2015 7:28:33 PM
Time window end	7/21/2015 8:28:32 PM
Time First	7/21/2015 7:28:33 PM
Time Last	7/21/2015 7:39:30 PM
Count	3

Context

Date and Time: 7/21/2015 7:39:30 PM Log Name: Operations Manager Source: Health Service Modules Event Number: 10353 Level: 2 Logging Computer: DATA.techninja.local User: N/A

Description: Module was unable to connect to cimv2 This has happened 145 times since this instance was loaded. Error: 0x8004100e One or more workflows were affected by this. Workflow name: MomUIGeneratedRule7808a3993d3d429f9bf68fe7aacd9afa Instance name: DATA.techninja.local Instance ID: {7A37EAC5-9001-946C-51CD-F4F14157AD16} Management group: Ninja Monitor

Event Data:

< DataItem type =" System.XmlData " time =" 2015-07-21T19:39:30.0237093-04:00 " sourceHealthServiceId =" 2A56B99C-6490-A768-BA63-A87379586170 " > < EventData >   < Data > Ninja Monitor </ Data >   < Data > MomUIGeneratedRule7808a3993d3d429f9bf68fe7aacd9afa </ Data >   < Data > DATA.techninja.local </ Data >   < Data > {7A37EAC5-9001-946C-51CD-F4F14157AD16} </ Data >   < Data > cimv2 </ Data >   < Data > 145 </ Data >   < Data > 0x8004100e </ Data >   </ EventData >

  </DataItem >

  Thank you so much for assisting I am in a bind here.

• Edited by bigbluestar Tuesday, July 21, 2015 11:54 PM

Sorry my mistake the product is SCOM.  Its a wmi rule.  The rule is running against a agent managed win 2012 server.  The scom action account has administrator privilege on that server.  I can run the wmi query remotely from the scom server to target with no issues using the scom action account.  however scom server reports the error in the subject.

Alert context

Time window start	7/21/2015 7:28:33 PM
Time window end	7/21/2015 8:28:32 PM
Time First	7/21/2015 7:28:33 PM
Time Last	7/21/2015 7:39:30 PM
Count	3

Context

Date and Time: 7/21/2015 7:39:30 PM Log Name: Operations Manager Source: Health Service Modules Event Number: 10353 Level: 2 Logging Computer: DATA.techninja.local User: N/A

Description: Module was unable to connect to cimv2 This has happened 145 times since this instance was loaded. Error: 0x8004100e One or more workflows were affected by this. Workflow name: MomUIGeneratedRule7808a3993d3d429f9bf68fe7aacd9afa Instance name: DATA.techninja.local Instance ID: {7A37EAC5-9001-946C-51CD-F4F14157AD16} Management group: Ninja Monitor

Event Data:

< DataItem type =" System.XmlData " time =" 2015-07-21T19:39:30.0237093-04:00 " sourceHealthServiceId =" 2A56B99C-6490-A768-BA63-A87379586170 " > < EventData >   < Data > Ninja Monitor </ Data >   < Data > MomUIGeneratedRule7808a3993d3d429f9bf68fe7aacd9afa </ Data >   < Data > DATA.techninja.local </ Data >   < Data > {7A37EAC5-9001-946C-51CD-F4F14157AD16} </ Data >   < Data > cimv2 </ Data >   < Data > 145 </ Data >   < Data > 0x8004100e </ Data >   </ EventData >

  </DataItem >

  Thank you so much for assisting I am in a bind here.

• Edited by bigbluestar Tuesday, July 21, 2015 11:54 PM

The wmi error could be caused by this https://support.microsoft.com/en-us/kb/281888 check that first on one of the agent machines, and let us know the results.

Thanks again for the help, however both scom, and the target servers all have this value set correctly.  I would like to add that I have about 6 servers in this environment, and all report the same error, including the scom servers local client.

I also noticed that the frequency is set to 10 seconds on your wmi rule, which should only be used for testing. set it for every few minutes when you move it to production.

Will do.  I just hope I can find a solution to this problem I am really impressed with the product and just needs this hurdle removed to really start using it.  Is there any additional logging I can enable to get more details into what is going on. So far event viewer provides the same details as above.....

Not sure if this will address your problem, but following Kevin Holman Example, from his blog http://blogs.technet.com/b/kevinholman/archive/2008/07/02/collecting-and-monitoring-information-from-wmi-as-performance-data.aspx

your Value should be $Data/Property[@Name='FreeSpace']$

The query I used,SELECT FreeSpace FROM Win32_LogicalDisk WHERE DeviceID='C:'

try that out and let us know.

Thanks very much your suggestion worked.  I was able to see the error of my ways by going through the guide. I was creating a alert generating rule, when I needed to create a performance based.  I will need to look into it more to see what the true reasoning behind it is, but it works now, and I am getting the results I was looking for.  Thanks much.