I recently encountered an issue while configuring OpsMgr-to-VMM connection. The detailed error was as follows:
Error 10218
Setup could not import the System Center Virtual Machine Manager Management Pack into Operations Manager server because one or more required management packs are missing. The VMM Management Packs cannot be deployed unless the following component management packs are present in Operations Manager : Windows Server Internet Information Services 2003, Windows Server 2008 Internet Information Services 7, Windows Server Internet Information Services Library, SQL Server Core Library.
Recommended Action
To provide the missing component management packs, ensure that the following management packs have been imported into Operations Manager server: Microsoft Windows Server 2003 Internet Information Services Management Pack for OpsMgr 2012 (version 6.0.6278.0 or later), Microsoft SQL Server 2005 Management Pack(version 6.0.5000.0 or later), You can download the management packs from the System Center Operations Manager Catalog
While the error detail and proffered solution indicate that the problem has something to do with your management packs it’s not very helpful in actually remediating the issue.
Solution
I’ll assume that you have all of the pre-requisite management packs imported into SCOM. Review the required steps as this is the first thing you’ll need to confirm. After reviewing the pre-requisite management packs and the management pack versions, I determined that an older version of the VMM management pack, in my case, “Microsoft System Center Virtual Machine Manager 2007” had been imported into OpsMgr and this management pack along with the Microsoft Virtualization Core Library management pack which it depends on need to be removed from OpsMgr in order for the new Operations Manager connection from VMM to be successful.
Cheers!
Latest posts by Chiyo Odika (see all)
- Replicate Proximity Placement Group workloads in Azure - January 13, 2021
- Azure NetApp Files (ANF) – Deploy with JSON - October 9, 2020
- Addressing Critical ZeroLogon Vulnerability CVE-2020-1472 - September 26, 2020