VMware Management Pack Update Release (20.11.2156.0)
by Jonas Lenntun, on 25-Jan-2021 10:10:00
Our first release for 2021 of the OpsLogix VMware Management Pack for Operations Manager is now released. This version includes mostly fixes to issues reported since the previous release but also a new PowerShell function to manage your licenses.
Important: In our previous release we also simplified the configuration and licensing experience and moved everything under the administration pane. This will require you to remove the old Licensing UI Management Packs before upgrading from older versions then 20.5.1899.0.
And once again, we fully support the new version of VMware vSphere 7 and vSAN.
The new version (20.11.2156.0) is available for download in our customer download area. If you are upgrading, please read the upgrade manual for a complete step-by-step guide to ensure a trouble free experience.
Manage vCenter connections/licenses by using PowerShell
In some situations you may need to manage many vCenter or Esx Hosts connections. Ordinarily you would use the "Opslogix VMware Configuration Dashboard" for adding and removing connections, however this can be very time consuming using the GUI.
Since V20.11.x.x we have shipped a Powershell module to manage connection. By using the Opslogix VMware powershell module you can add and remove connections and you are able to assign host licenses. All examples are based on adding or modifying 1 connection. But you can easily change the script to handle multiple connections if needed.
If you upgrade from a older version then 20.5.1899.0, please review the following.
- We refactored and moved the Licensing console to the Administration part in the SCOM console for a better end-user experience.
- Before importing this release, please remove the "OpsLogix IMP - Licensing UI for OpsMgr 2012" management pack.
- Before importing this release, please remove the "OpsLogix IMP - VMware Full Monitoring Groups" management pack.
- After importing you will have to re-assign the hosts licenses using the console OpsLogix VMware MP -> assign tab
- We changed the version numbering to [Year].[Month].[BuildNr].[PatchNr] to get better release insights
After removing the Management Packs above, you can continue to import this release including the new versions of the previously removed MPs.
- You can now add and maintain vCenter connections/licenses by using a PowerShell module
- When using a split connection vSAN components and VM snapshots were not correctly discovered
- The OpsLogix license is valid monitor reports an incorrect warning state
- The VC alert backlist csv file would be overwritten during a collector update
- Various small spell typos
- Guest OS monitoring was reporting the powerstate in the alert message instead of the OS guest state
- Incorrect vSAN label on the disk group throughput performance rule
- Incorrect vSAN performance scale for latency and throughput monitors and performance rules
- In some scenarios the warning state of the ESX Host RAM Disk monitor was incorrect
- Using the Alert template with target types 'Datacenter' and 'Resource Pool' will fail to save
- The VC alarm filter was broken
- The interval for the VC alert collection rule is changed from 5 to 2 minutes
- Formatted the ESX Host RAM Disk task output
- Updated 'Learn more' urls
- If you have imported the 2 vSAN management packs please remove before importing the new version
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