Scale out a vCenter connection
Spread the workload of one large vCenter server over several SCOM management servers.
Applies to: OpsLogix VMware Management Pack (all versions) · SCOM 2019, 2022, 2025 · vCenter 7.0, 8.0, 9.0
Last updated: October 2026 · Reading time: 5 minutes
Goal
Spread the monitoring workload of one large vCenter server over several servers in the VMware resource pool. You usually only need scale out for a single, large vCenter server. Read When you need scale out before you turn it on.
When you need scale out
The vCenter connection object in SCOM is the parent of everything below it: datacenters, clusters, ESXi hosts, VMs and so on. A SCOM resource pool balances parent objects over its members, and all child objects run on the same server as their parent. With one vCenter connection there's only one parent, so one server in the pool does all the VMware work while the others stay idle.
Example: you monitor one vCenter server with 200 ESXi hosts and 6,000 VMs, and you have 3 management servers in the resource pool. Without scale out, one of them does all the work.
Consider scale out when:
- one vCenter server has more ESXi hosts than one server can handle (about 150, see Sizing for the VMware Management Pack), or
- a gateway server manages the connection and the vCenter server has more than about 2,000 VMs (see Using a SCOM gateway server in the VMware resource pool).
How scale out works
- The scale out level (1 to 10) is the number of extra connection objects SCOM creates. They have the name of the connection followed by --GROUP01, --GROUP02 and so on, and you see them in SCOM next to the original connection.
- When you click Update on the Assign tab, the licensed ESXi hosts are spread evenly over these groups, by number of hosts. Each group discovers and monitors only its own hosts and their VMs. The Scale out group column on the Assign tab shows which group each host belongs to.
- The original connection keeps the shared objects, such as datacenters, clusters, datastores and networks, but no hosts.
- The resource pool spreads the groups over its members, so the work is spread too.
Things that work differently on a scaled-out connection:
- The groups forward only vCenter alarms of ESXi hosts, VMs and snapshots. See Change how vCenter alarms create SCOM alerts.
- The groups don't run the vCenter Server Appliance discovery; the original connection does.
- Scale out can only be set in VMware MP Configuration, not with the PowerShell module.
Prerequisites
- A resource pool with at least as many available servers as you want to spread the work over. See Configure the VMware resource pool.
- The vCenter connection is already added. See Add a vCenter or ESXi connection.
Turn on scale out

- Go to Administration > OpsLogix MP Configuration > VMware MP Configuration, open the Add/Remove Connections tab and select the vCenter connection.
- Under Scale out, select Enable scale out. If a warning appears, confirm it with Yes.
- Set Scale out level. Choose a level that keeps each group well within the limits above. Hosts are spread by number of hosts, not by number of VMs, so leave room for hosts with many VMs.
- Click Check Connection, wait for Connection was successful, and click Add/Update. SCOM creates the group objects.
- Open the Assign tab and click Refresh.
- Check that the right hosts are selected and click Update. If Update isn't available, clear one host and select it again first. This step is required: the hosts are only spread over the groups when you click Update.
Change or turn off scale out
- To change the level, repeat the steps with the new level. A lower level removes the highest groups; a higher level adds groups. Always finish with Update on the Assign tab.
- To turn scale out off, clear Enable scale out, click Check Connection and Add/Update. The group objects are removed. Then click Update on the Assign tab, so the hosts are assigned to the connection itself again.
- Before you remove a scaled-out connection, turn scale out off first. Remove only deletes the original connection object, not its groups.
Objects that move to another group are discovered again under that group. Their health state and history start fresh.
Verify it worked
The Scale out group column on the Assign tab shows a group for every licensed host. After the next discovery, which takes several hours, the VMware workload is spread over the servers in the resource pool.
See also
- Sizing for the VMware Management Pack
- Using a SCOM gateway server in the VMware resource pool
- Change or delete a vCenter or ESXi connection