Hi everyone!

Just finsihed upgrading VMM 2008 R2 SP1 to VMM 2012 and successfully integrating VMM 2012 with SCOM 2012 (VMM 2012 management pack version 3.0.6019.0).  We are now getting the following SCOM alert from all our VMM 2012 managed Hyper-V hosts...

Alert: "The VMM agent status is Not Monitored on [HOST]" - Monitor: "System Center 2012 Virtual Machine Manager VMM Agent Monitored By OpsMgr"

SCOM 2012 agent is installed and working as expected on our Hyper-V hosts.

Any help or guidance would be apprecaited!

Regards,

JJ

Hi

This is a known issue and will be addressed in a future release. If all your agents are already being monitored, for now, a workaround to is to disable the monitor.

thanks,
Chetan

OK, thanks Chetan!  :-)

• Edited by IM5FOOTNOTHIN Tuesday, June 12, 2012 8:06 PM

OK, thanks Chetan!  :-)

• Edited by IM5FOOTNOTHIN Tuesday, June 12, 2012 8:06 PM

OK, thanks Chetan!  :-)

• Edited by IM5FOOTNOTHIN Tuesday, June 12, 2012 8:06 PM

OK, thanks Chetan!  :-)

• Edited by IM5FOOTNOTHIN Tuesday, June 12, 2012 8:06 PM

OK, thanks Chetan!  :-)

• Edited by IM5FOOTNOTHIN Tuesday, June 12, 2012 8:06 PM

OK, thanks Chetan!  :-)

• Edited by IM5FOOTNOTHIN Tuesday, June 12, 2012 8:06 PM

OK, thanks Chetan!  :-)

• Edited by IM5FOOTNOTHIN Tuesday, June 12, 2012 8:06 PM

Chetan, I am also having a similar issue with this.  Was this fixed in Roll up 1, or is it still broken?  I am currently running SCOM 2012 RU1 and VMM 2012 RU1. It appears the issue is that VMM is looking for the FQDN for the Windows Computer Object, but Clustered resources only get discovered with NetBIOS name (for the Windows Computer Object).  I'm not sure why this is, but I haven't been able to get any Cluster Member to discover with FQDN, only NetBIOS.  I see this behavior for all Cluster Members.

Unfortunately, it hasn't been fixed in Upgrade Rollups.

Thanks for info.  Any plans to get this fixed in Rollup 3 or SP1?

We get this too.Please fix.  Making overrides then having to remember to have to undo later when it is fixed...meh :p

Do you guys still have a problem with this?

I'm running SCOM 2012 SP1 Update Rollup 2 and I'm getting these alerts.

No, it has never been fixed that I'm aware of, coming up on a year for this post... :-(  

I'm not one to complain but the VMM 2012 management pack is and continues to be riddled with bugs (e.g. this issue as well as broken diagram views just to name a few) none of which were fixed in the SP1 or UR2 updates.

Regards,

JJ

ok, I'm got it working however I get alot of these "The VMM agent status is Not Monitored on ***" alerts often so it seems to be unstable

And guess what?

It's still not fixed in SCOM 2012 R2 / SCVMM 2012 R2.

Can confirm too that this is not fixed in 2012 R2 release. Surprised this is still an issue after such a long time.

Same problem here.... SCOM 2012 R2 / VMM 2012 R2.

Everything was working fine, but since yesterday, from nowhere, this alerts started showing....

Same issue since CU3 installed on SCOM 2012 R2 and VMM 2012 R2 while agents are running on Hyper-V 2012 R2. On servers running Hyper-V 2012 (not R2) no issues so far...

• Edited by PRND Tuesday, August 19, 2014 5:45 AM

Same issue since CU3 installed on SCOM 2012 R2 and VMM 2012 R2 while agents are running on Hyper-V 2012 R2. On servers running Hyper-V 2012 (not R2) no issues so far...

• Edited by PRND Tuesday, August 19, 2014 5:45 AM

Same issue since CU3 installed on SCOM 2012 R2 and VMM 2012 R2 while agents are running on Hyper-V 2012 R2. On servers running Hyper-V 2012 (not R2) no issues so far...

• Edited by PRND Tuesday, August 19, 2014 5:45 AM

Same issue since CU3 installed on SCOM 2012 R2 and VMM 2012 R2 while agents are running on Hyper-V 2012 R2. On servers running Hyper-V 2012 (not R2) no issues so far...

• Edited by PRND Tuesday, August 19, 2014 5:45 AM

Same issue since CU3 installed on SCOM 2012 R2 and VMM 2012 R2 while agents are running on Hyper-V 2012 R2. On servers running Hyper-V 2012 (not R2) no issues so far...

• Edited by PRND Tuesday, August 19, 2014 5:45 AM

Same issue since CU3 installed on SCOM 2012 R2 and VMM 2012 R2 while agents are running on Hyper-V 2012 R2. On servers running Hyper-V 2012 (not R2) no issues so far...

• Edited by PRND Tuesday, August 19, 2014 5:45 AM

Same issue since CU3 installed on SCOM 2012 R2 and VMM 2012 R2 while agents are running on Hyper-V 2012 R2. On servers running Hyper-V 2012 (not R2) no issues so far...

• Edited by PRND Tuesday, August 19, 2014 5:45 AM

Can't help but laugh, 2+ years and going and still no fix.  Makes you wonder how Microsoft actually tests their management packs? ...or do they?

Yes, laughing seems to be the only way to cope with it.

I searched the MPs for the monitor's definition.

UnitMonitorType has only Scheduler as DataSource ! So there is no probing , checking...nothing.

And that seems to be the case for most of these monitors.

Who has written the MP ? That is really ridiculous ...

If the other parts are of same quality, I'm thinking of the PRO enabled MPs, ...why should I install the SCVMM 2012 R2 MPs ?

Would be great if a Microsoft engineer could answer.

Btw: This costs us hours (!) to investigate, searching the forums.

Actually i have installed the UR3 Release on my Scom 2012 R2 environment and the problem Remains. I have re-searched almost the Ops Mgr forums and no solutions. Only disable the monitor... Just Great... 

Still seems to be there with SCOM 2012 R2 UR4....

This has just appeared in my environment after going to UR5

Same here, after UR5 the alerts came. In UR3 no problems. Any fix yet instead of disabling the monitor?

I've even tested this in SCOM/SCVMM 2016 TP3 and it still occurs. It is very disappointing that Microsoft doesn't improve their own product integration issues.