Potential issues with VMM 2012/OpsMgr integration

Potential issues with VMM 2012/OpsMgr integration

  • Comments 5
  • Likes

imageHi everyone, Alvin Morales here.  This article presents possible errors and issues you may encounter after setting Operations Manager integration with System Center 2012 – Virtual Machine Manager (SCVMM 2012).  Note that this can apply to System Center Operations Manager 2007 (OpsMgr 2007) as well as System Center 2012 – Operations Manager (OpsMgr 2012).

1. Error 11808 - Unable to set the Operations Manager root server in VMM because the Operations Manager is not installed on the Virtual Machine Manager management server.

Recommended action:

Install the Operations Console for System Center Operations Manger 2007 on the Virtual Machine manager server and then try the operation again.

NOTE This error message can be misleading as it applies to either version of OpsMgr even though it only specifically mentions OpsMgr 2007.  The console required has to match the version you are using on the Operations Manager server, so if you are integrating with OpsMgr 2012 you need to install the OpsMgr 2012 console on the SCVMM 2012 server.

=====

2. Error 25907 - The credentials used to connect to Operations Managers management group do not have the necessary permissions

Recommended Action:

Try operation again with different credentials or add the credentials to the OpsMgr Administrator Role

NOTE You will need to add either one of these to the OpsMgr built-in administrators group.  Add the account used for integration or add the machine name if local system was selected during integration.

=====

3. Error 10218 - Setup could not import the System Center Virtual Machine Manager Management pack into Operations Manger server because one or more required management packs are missing. The VMM management pack cannot be deployed unless the following components management packs are present in operations manager 2007…..

Recommended action:

To provide the missing component management packs, ensure that the following management packs cannot be deployed unless the following component management packs are present in operations manager 2007:…

NOTE The minimum required version of the Management Packs is 6.0.5000.0

=====

4. Error status in the operations manager settings.

Error Details:

Operations Manager discovery failed with error: "Exception of type 'Microsoft.virtualmanager.enterprisemanagement.common.dicoverydatainvalidrelationshipsourceexception0m10' was thrown.

NOTE This is caused by one or more hosts under SCVMM management not having the OpsMgr agent installed and reporting to an Operations Manager server. The new architecture in SCVMM 2012 requires that the Operations Manager agent be installed on all hosts so they can send VM information directly and not have to go through SCVMM.

=====

5. Error 25923 - PRO Diagnostics Target is not monitored

Recommended Action

Check if Operations manager agent is running on the computer running VMM management server

NOTE This is usually caused by the Operations Manager agent not being installed on the VMM server. It can also occur if the VMM server has the agent installed but it is not monitored (e.g. it there are problems with health agent).  Verify the operations manager console and make sure it is in a Healthy State.

Alvin Morales | Senior Support Escalation Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

 

 

 

OpsMgr 2007 SCOM 2007 SCOM 2012 OpsMgr 2012 VMM 2012

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hi J.C. I'm facing issue number four at a customer site. I have done that before and my lab also has everything working fine.

    All required MPs are there, the VMM imported MPs are the latest (from MP UR1), the credentials are fine (admin on both sides), all HV hosts (and Library servers, just in case) have agents.

    Have removed (everything, including MPs) once and removed the connection many times now, using the SCVMM account and creating specific one for the connection. Nothing seems to fix the Discovery exception issue.

    I heard a rumour about machines stored in the library could cause this. Is there any reference to that?

    Any other ideas?

  • Hi Jose, another workaround I've seen is to not check the Enable PRO box. Let the connector complete its work, and then when it has run successfully once it will have created the computer objects. Then you can safely check the box and rerun the connector.