Skip to content
English
Submit a support ticket
Back to www.opslogix.com
  • There are no suggestions because the search field is empty.

Remove the VMware Management Packs

Uninstall the OpsLogix VMware collectors and remove all VMware Management Packs from SCOM with PowerShell.

Applies to: OpsLogix VMware Management Pack (all versions) · SCOM 2016 – 2025
Last updated: October 2026 · Reading time: 4 minutes

Goal

Remove the OpsLogix VMware Management Packs and the OpsLogix VMware Collector from SCOM completely, for example when you stop using the product or want to start again from scratch.

Note: removing the management packs removes all VMware objects from SCOM, with their health state, alerts, overrides and performance data in the operational database. To upgrade, don't remove anything; import the new version over the old one.

Prerequisites

  • A SCOM administrator account.
  • Access to a SCOM management server with the Operations Manager PowerShell module.
  • Administrator rights on the servers in the VMware resource pool, for the clean-up in step 4.

Step 1: Uninstall the collectors

Do this while the management packs are still installed, because the uninstall task is part of them.

  1. In the Monitoring workspace, go to OpsLogix > VMware > VMware Collector > State VMware Collector Service.
  2. Select all collector services and run OpsLogix Uninstall VMware Collector Task from the Tasks pane.
  3. Check the task output. On servers that aren't in the list, for example servers you removed from the resource pool earlier, uninstall OpsLogix VMware Collector in Programs and Features.

Step 2: Remove override management packs that depend on the VMware packs

SCOM can't remove a management pack while another one refers to it. Your own override management packs usually do. To list the unsealed packs that refer to the VMware packs, run:

Import-Module OperationsManager
Get-SCOMManagementPack | Where-Object { -not $_.Sealed -and ($_.References.Values | Where-Object { $_.Name -like 'OpsLogix.IMP.VM*' }) } | Select-Object Name, DisplayName

Ignore the OpsLogix packs in the result, such as the ransomware .Groups packs and OpsLogix.IMP.VMWare.CapacityAnalysis.Dashboards; the script in step 3 removes them. Everything else is yours, even if its name starts with Opslogix.

Export the ones you want to keep (Export-SCOMManagementPack), then delete them in Administration > Management Packs. If an override pack also contains overrides for other products, remove only the VMware overrides from it instead.

Step 3: Remove the management packs

Run this script on a management server as a SCOM administrator. It removes the packs in an order that respects their dependencies. Packs that aren't installed, such as packs from older versions, are skipped.

Import-Module OperationsManager

# Order matters: packs that depend on others are removed first
$Mps = "OpsLogix.IMP.VMWare.RansomwareVulnerability.Monitoring*.Groups",
       "OpsLogix.IMP.VMWare.RansomwareVulnerability.Monitoring*",
       "OpsLogix.IMP.VMWare.vSan.Dashboards",
       "OpsLogix.IMP.VMWare.Dashboards",
       "OpsLogix.IMP.VMWare.Reports",
       "OpsLogix.IMP.VMWare.Templates",
       "OpsLogix.IMP.VMWare.Monitoring.Groups",
       "OpsLogix.IMP.VMWare.Guest.Monitoring",
       "OpsLogix.IMP.VMWare.Appliance.Monitoring",
       "OpsLogix.IMP.VMWare.CapacityAnalysis.Dashboards",
       "OpsLogix.IMP.VMWare.CapacityAnalysis",
       "OpsLogix.IMP.VMWare.Hardware",
       "OpsLogix.IMP.VMWare.vSan",
       "OpsLogix.IMP.VMWare.Licensing.Monitoring",
       "OpsLogix.IMP.VMWare.ConfigurationDashboard",
       "OpsLogix.IMP.VMware.Collector",
       "OpsLogix.IMP.VMWare.Monitoring",
       "OpsLogix.IMP.VMWare"

foreach ($name in $Mps) {
    Get-SCOMManagementPack -Name $name | Remove-SCOMManagementPack
}

# Anything left?
Get-SCOMManagementPack | Where-Object { $_.Name -like 'OpsLogix.IMP.VM*' } | Format-Table Name, Version

The script doesn't remove OpsLogix.BaseLibrary and the OpsLogix licensing management pack, because other OpsLogix management packs use them too. If you don't use any other OpsLogix product, you can delete them afterwards in Administration > Management Packs.

Step 4: Clean up the servers

On each server that was in the VMware resource pool:

  • Delete the folder C:\Program Files\Opslogix\OpsLogix VMware Collector if it's still there. The uninstall leaves the license, license assignment and alarm filter files behind.
  • If you set registry values for the VMware Management Pack, delete the key HKLM\SOFTWARE\OpsLogix\VMware. See VMware Management Pack registry settings.

If you created your own resource pool for the VMware monitoring, delete it in Administration > Resource Pools. The OpsLogix Resource Pool for VMware Management Pack is removed together with the management packs.

Verify it worked

The last command of the script returns nothing, and OpsLogix VMware Collector no longer appears in Programs and Features on the pool members. If packs remain, run the command from step 2 again: an override pack that depends on them probably still exists.

See also