Upgrade Guide

Upgrade guide for OpsLogix VMware Management Pack V 20.9.2060.0 for System Center Operations Manager

This guide describes the upgrade path from previous versions of the to the latest version of the VMware management pack.

Please read the release notes found here before upgrading.

Software Prerequisites

  • The OpsLogix VMware Management Pack requires Microsoft System Center Operations Manager 2012 SP1, 2012 R2, 2016, 180x or 2019.
  • The OpsLogix VMware Management Pack makes use of Microsoft .NET Framework 4.5. It is required that Microsoft .NET Framework 4.5 is installed on all SCOM Management Server and Gateway Servers that are resource pool members in the resource pool used for VMware monitoring.
  • The Management Pack can be upgraded from of VMware Management Pack version V1.3.8.x

VMware Compatibility

The OpsLogix Management Pack for VMware supports the following VMware versions:  



VMware vCenter 5.0 or Higher

VMware ESXi Host 5.0 or Higher

VMware ESX Host 5.0 or Higher

Upgrade Steps

The steps below show the upgrade process for OpsLogix VMware Management Pack. 



The OpsLogix VMware Management Pack requires top level read permissions on the vCenter or ESX(i) host for the monitoring. The user used for the monitoring account should have at least the privileges below:

  • Top level read only
  • Validate session

Please see installation manual “SETTING UP THE VMWARE MONITORING ACCOUNT” to configure the monitoring account.

2. Import the new Management Packs

Import all the management packs contained in this release. It is not necessary to uninstall any of the previously imported OpsLogix management packs before importing the current version. If the Operations Manager Console shows errors during the import and the “Install” button is disabled, check if there are management packs already imported with the same version or higher, if this is the case, remove these management packs from the import list. The “OpsLogix IMP - Base Library”, “OpsLogix IMP - Licensing UI for OpsMgr 2012” and “OpsLogix Generic Reports” frequently cause the issue described above.

IMPORTANT :  If you are on V1.3.1724.0 or lower than before importing this release you will need to remove the management packs below from SCOM using the SCOM operations console -> Administration -> management packs -> Delete :

  • OpsLogix IMP - Licensing UI for OpsMgr 2012
  • OpsLogix IMP - VMware Full Monitoring Groups

After removing you can continue to import this release including the just removed management packs .

3. Restart the SCOM Console

After importing restart the SCOM console to reload the special UI components.

4. Install the VMware Collector

Notice: Do the actions below once for every vCenter/ESX host connection you have setup in each unique SCOM resource pool.

In this version of the VMware management Pack the VMware monitoring data is collected by a collector service called “OpsLogix VMware Collector”. After importing this version, you will have to do a connection test for all the configured VMware vCenter connections using the “Check Connection” in the “VMware MP Configuration” dashboard. During this check the OpsLogix Collector will be installed on all the members of the selected SCOM VMware resource pool. If you have several connections configured then you will have to do this step above only once for every unique resource pool.

 If the service is not deployed, some common causes are:

  • You have added a new member to the pool and did not do the “Check Connection”
  • You use a SCOM Gateway Server as a resource pool member. Using a gateway is supported, however, in some cases the deployment of the collector service fails. Most of the time due to security issues.
  • Microsoft .Net Framework 4.5 is not installed on the SCOM Management Server or SCOM Gateway Server.
  • A virus scanner is preventing the deployment of the install package.                     

If the collector service fails to deploy automatically it needs to be installed manually by following the steps below:

  • On all pool members (SCOM Management Servers and Gateway Servers) that are member of the resource pool used for monitoring VMware, navigate to “Control Panel\Programs\Programs and Features” and check if the “OpsLogix Collector” software is installed.
  • If the program “OpsLogix Collector” is not installed then logon to the SCOM member server(s) to install the “OpsLogix VMware Collector” manually by copy from an ‘other’ working member server the file in directory “….\Operations Manager\Server\Health Service State\Resources\*” named “VMware.MP.RestBase.Server.NTService.Installer.exe” and execute this on the new member host(s). You can continue using all default setting.

5. Assign a license to the host

After you have imported all the management packs - and you have checked that the VMware collector is installed on all the resource pool members - you need to assign a license to every host you would like to monitor using the “VMware MP Configuration” dashboard. See installation manual chapter “ASSIGN A LICENSE TO THE HOSTS”.

6. Restart the SCOM Agents

On all the SCOM MS servers that are member of the SCOM resource pool you use for the VMware monitoring restart the SCOM agent to reload the new modules and trigger the discovery.