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

No VMware instances are monitored in SCOM

Troubleshoot why vCenter servers, ESXi hosts and VMs don't appear in the SCOM console after you install the VMware Management Pack.

Applies to: OpsLogix VMware Management Pack (all versions) · SCOM 2019, 2022, 2025 · vCenter 7.0, 8.0, 9.0
Last reviewed: October 2026 · Reading time: 3 minutes

Symptom

You've installed the OpsLogix VMware Management Pack, but no VMware objects (vCenter servers, ESXi hosts, virtual machines or datastores) appear in the SCOM console.

Cause

This usually has one of these causes:

  • The OpsLogix Collector isn't installed on every member of the VMware monitoring resource pool.
  • VMware components were installed by hand on a pool member.
  • The monitoring account can't log on to vCenter or ESXi, or doesn't have the required role.
  • .NET Framework 4 is missing on a pool member.
  • The VMware environment isn't a supported version.

Resolution

Work through these checks in order.

  1. Check that the OpsLogix Collector is installed. On each member of the VMware SCOM resource pool, open Control Panel > Programs > Programs and Features and look for OpsLogix Collector. If it's missing on any member:
    1. In the SCOM Operations Console, go to Administration > OpsLogix MP Configuration > VMware IMP Configuration Dashboard. Select the connection that isn't monitored and click Check Connection.
    2. Restart the Microsoft Monitoring Agent service on all members of the pool.
    3. Go to Monitoring > Discovered Inventory and change the target type to SystemCenter.ManagementService. Select the management servers that need the collector and, in the Tasks pane, run OpsLogix Deploy VMware Collector. Wait for the task to finish and check that it completed without errors.
  2. Remove manually installed VMware components. Make sure no VMware components were installed by hand on the pool members.
  3. Check that the monitoring account can log on to your vCenter server or ESXi hosts.
  4. Check the monitoring account's role. It needs at least the Read-only role plus the Validate session privilege. See Set up a VMware monitoring account.
  5. Check that .NET Framework 4 is installed on all pool members.
  6. Check that your VMware versions are supported. See Which VMware ESXi and vCenter versions are supported?
  7. Check the event logs. On every pool member, open the Operations Manager event log and look for OpsLogix events.

Verify it worked

Discovery can take a while after a fix, especially in large environments (see How long does discovery take?). Then open the Monitoring workspace in the SCOM console and check that your vCenter servers, ESXi hosts and virtual machines appear.

If they still don't appear, enable debug logging, gather the support information and submit a support ticket.

See also