This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 89%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETG%3C/text%3E%3C/svg%3E)
My SCOM2016/VMM2016 integration is no longer working. The reported error is 11823:
VMM Management group object cannot be found.
One or more of the Virtual Machine Manager objects monitored by Operations Manager could not be discovered. This might be caused by a missing or outdated version of the System Center Virtual Machine Manager management pack in Operations Manager.
As far as I can tell I've got the correct MPs imported, port 5724 is open between the VMM and SCOM server and the domain account for the connection is a local admin on both the VMM and SCOM servers.
Where else can I look for more detail of why this isn't working?
Hi @Tony Gedge ,
Have you followed the SCOM - VMM integration documentation step-by-step?
Integrate VMM with Operations Manager for monitoring and reporting
https://learn.microsoft.com/en-us/system-center/vmm/monitors-ops-manager?view=sc-vmm-2016
You can also refer to the documentation below which goes deeper into the error 11823:
https://learn.microsoft.com/en-us/troubleshoot/system-center/vmm/vmm-integration-error-11823
----------
(If the reply was helpful please don't forget to upvote or accept as answer, thank you)
Best regards,
Leon
Hi @Tony Gedge ,
This most probably indicates an unsupported config, please see the article Leon referenced.
In order to confirm this, please check the VMM debug log trace.
----------
(If the reply was helpful please don't forget to upvote or accept as answer, thank you)
Best regards,
Stoyan
Thanks for your reply.
I went through the integration document and I think all the requirements are met. I then removed the current connection and re-created it using the Wizard. The new error is:
Warning (25940)
One or more of Virtual Machine Manager objects could not be discovered. This might be caused by Operations Manager not monitoring one of the Hyper-V hosts or the Virtual Machine Manager Server. The detailed error is: "Exception of type 'Microsoft.VirtualManager.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceExceptionOM10' was thrown."
Not sure why this is happening as the agent is installed and healthy on all hypervisors and VMM server.
Not sure what precisely to look at next...
This error may be caused if one or more hosts under SCVMM management not having the SCOM agent installed and reporting to an Operations Manager server.
I don't think this is the case as all 8 hosts that are under SCVMM management (as reported by Get-SCVMHost) have an active agent in healthy state in SCOM (as reported by Get-SCOMAgent).
Any other ideas on where to look? Is there some log I can look at to see which object that VMM is looking for is missing?
I have just noticed that only two of the three clusters are listed as being monitored in SCOM, which I suspect may be the root cause. Unfortunately I've been unable to work out why this particular cluster isn't being monitored. SCOM knows about all the cluster nodes and that the cluster exists, it's just not listed as being monitored.
Hi @Tony Gedge ,
I had to deal with this exact same error a few weeks ago, but in my case I turned out to be a bug (VMM 2019 UR1 with SCOM 2019 UR1), so I assume we have another cause here. Here are some suggestions:
Integrating SCVMM 2016 with SCOM 2016 Error (25932)
SCOM Console Install on VMM Server Causes Service Crash
If you are not able to pinpoint the cause after those steps, I will recommend you to check the OperationsManager Event Logs on the SCOM Management Server, which you enter for the integration after and during a "Refresh" on the VMM side. Please post the related events here, maybe we can help you out.
----------
(If the reply was helpful please don't forget to upvote or accept as answer, thank you)
Best regards,
Stoyan
Thanks for your reply Stoyan. I think something is screwed up in my updating of the SCOM and SCOM agents. I had thought that applying the SCOM URs via WSUS handled this, but it doesn't appear to be the case.
According to SCOM, the VMM server and all Hypervisors managed by it have the same agent version (8.0.10918.0), which is the RTM version. However if I look on these servers directly, they all show the MMA UR9 patch installed, but the installed MMA agent information in add/remove programs still shows the RTM agent version.
The SCOM server shows a similar problem. The installed SCOM software in add/remove programs is 7.2.11719.0 (which is RTM) and Get-SCOMManagementServer also shows the same version. The console installed on the SCOM server shows 7.2.12265.0 (which is UR9) but there's no indication that the UR9 patch is installed in add/remove programs.
Clearly something isn't quite right here, so I need to work out what to do to fix it.
The Control Panel will always show the ”RTM” version, it does not show the correct version installed. The versions is something that has been a long-time issue in SCOM, however the versions are fixed and are shown properly in SCOM 2019 (latest update rollup). I would in your case strongly recommend using Kevin’s SCOM Management management pack to see the actual versions of your SCOM agents and Management Servers in your SCOM environment. It is a management pack that can help you with a lot of other things as well.
The agents never get updated automatically during an Update Rollup installation, the agents need to be updated from the Operations Console via the Pending Management pane, or manually.
Well it looks like I've fallen down the trap of trusting the existing SCOM agent version discovery, which apparently doesn't account for changes when a UR is installed.
I added Kevin Holmans scom-agent-version-addendum-management-pack which shows the UR level of the agent (basically it fetches the version from the OMAgentTraceTMFVer.Dll file instead of what is done by default). From this I can see all my agents are at 8.0.11049.0, which is UR9 and aligns with the installed patches on the machines themselves.
Now to find out whether the UR9 is actually installed on my SCOM management server. According to Windows Update it is, but I need to be sure.
Thanks Leon, I had come to that conclusion regarding reported SCOM versions as well :-)
I have installed Kevin’s SCOM Management management pack as you suggested and all VMM and Hypervisors are reporting 2016 UR9, as is the console and server UR level for the SCOM server. So it'd appear that my SCOM versions are correct.
GuatamR suggested that:
a BUG existed and was fixed in VMM 2016 UR8 & UR9 causing the Integration not to work as expected with a similar error what you are seeing.
Looks like I'll have to raise a case with MS to progress this further, which is a royal pain.