How To
      Back to home
      1. Knowledge Base | OpsLogix
      2. VMware Management Pack
      3. How To

      Upgrade Guide for VMware Managment Pack v24.6.4301.0

      Upgrade guide for Opslogix VMware Management Pack V 24.6.4301.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.

      NOTICE: Please read the 

      This guide describes the upgrade path from previous versions of the to the latest version of the VMware management pack. release notes found here before upgrading.

      Starting from of version 21.4.2426.0 or higher you will need to upgrade your license key before continuing to implement this version. This key upgrade is free for all subscribed users. Please go to https://portal.opslogix.com/ download the new license and apply it following the steps described here : Update the license   

      Software Prerequisites

      • The Opslogix VMware Management Pack requires Microsoft System Center Operations Manager 2012 R2, 2016, 2019 or 2022.
      • The Opslogix VMware Management Pack makes use of Microsoft .NET Framework 4.x. It is required that Microsoft .NET Framework 4.x 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 V22.3.2731.0

      VMware Compatibility

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

      Version

      VMware vCenter 6.5 or Higher

      VMware ESXi Host 6.5 or Higher

      VMware ESX Host 6.5 or Higher

      Upgrade Steps

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

      vmware_mp_upgrade_1

      1. SETTING UP THE VMWARE MONITORING ACCOUNT

      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 the knowledge base article Setup a VMware Monitoring Account to configure the monitoring account. You may skip this step if you have already set this up.

      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.

      NOTICE: The new Ransomware Vulnerability Monitoring management packs are located in software package at subfolder "Management Packs\Ransomware Vulnerability Monitoring". Please read the KB: Ransomware Vulnerability Monitoring before importing

      NOTICE: 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.

          3. Restart the SCOM Console

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

          4. Install the VMware Collector

          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. 

          NOTICE: 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.x 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 the knowledge base article Assigning 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.