Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)   View by Article ID

Selecting a subset of the vCenter Server inventory to monitor in vRealize Operations Manager Standard 1.0.x or Manager 5.x (1036195)


The licenses you have purchased determine the number of virtual machines that you can monitor with vRealize Operations Manager (formerly known as vCenter Operations Manager) Standard 1.0.x or vRealize Operations Manager 5.0.x. If the inventory of the vCenter Server system that you want to monitor has more virtual machines than your license allows, or if you want to monitor a subset of that inventory, you can reduce the number of objects to be monitored.


vRealize Operations Manager Standard and vRealize Operations Manager (formerly known as vCenter Operations Manager) monitor all the virtual machines that the collection user has read access to. To comply with the licensing terms and monitor a supported number of objects rather than the entire vCenter Server inventory, you can limit the permissions of the collection user to the set of virtual machines and other objects in one or more datacenters or clusters.
VMware supports providing access to all of the objects in a datacenter, cluster, or standalone host. You cannot provide access to individual virtual machines because selecting a subset of virtual machines that share the same underlying physical layer results in a mismatch of metric values. For example, if a host has two virtual machines and you provide access to only one of the virtual machines, the host workload does not match the sum of the virtual machine workload because the sum accounts for only one virtual machine. VMware recommends providing the collection user access to all of the datastores and networks that are visible to the selected datacenters, clusters, and standalone hosts. Do not share these datastores and networks with datacenters, clusters, or standalone hosts that the collection user does not have access to. 
As a best practice before you assign a collection user, verify that the user has read access to the objects that you want to monitor. As a security precaution, do not assign the vSphere Administrator user as the collection user.

Note: You should apply permission changes before initial discovery (installation), or the objects continue to be displayed in the interface and count towards the license limit. 

A new role needs to be created that includes the appropriate privileges. To add the new role:
  1. Use the vSphere Client to connect to the vCenter Server system that you want to monitor.
  2. Select Home > Roles.
  3. Right-click the Read-only role and select Clone.
  4. Rename the new role.
  5. Right-click the new role and select Edit Role.
  6. Expand Global and select the check box Health.
  7. Expand Profile-driven storage and select the check box Profile-driven storage view.

    Note: In older versions of vCenter Server, the Profile-driven storage item might not exist.

  8. Expand Storage Views and select the check box View.
  9. Click the OK button.
To provide access to a cluster:
  1. Use the vSphere Client to connect to the vCenter Server system that you want to monitor.
  2. Select Home > Inventory > Hosts and Clusters.
  3. Right-click the cluster and select Add Permission.
  4. Click Add to identify the user or group to assign a role and click OK.
  5. Select the new role from the Assigned Role drop-down.
  6. Select Propagate to Child Objects.
  7. Click OK to close the Assign Permissions dialog box.
  8. Select Home > Inventory > Datastores.
  9. On the Permissions tab for the datastores that are associated with the clusters to monitor, right-click the same user and click Properties.
  10. Select Read-only as the role and click OK.
  11. In the vRealize Operations Manager (formerly known as vCenter Operations Manager) Standard Administration page, assign the user with the Read-only role as the collection user and proceed to register vRealize Operations Manager Standard with the vCenter Server system.

    The URL format of the Administration page is https://IP/adminMain.action, where IP is the IP address or fully qualified host name of the vRealize Operations Manager (formerly known as vCenter Operations Manager) Standard virtual appliance.

    The URL format of the Administration page for vRealize Operations Manager is https://IP/admin/, where IP is the IP address or fully qualified host name of the vRealize Operations Manager virtual appliance.
You can follow a similar process to provide access to a datacenter. Granting access to a datacenter provides access to any datastores referenced by hosts within the datacenter. Note that the permission must be applied at the datacenter level and propagated to any child views (such as networking objects), as in the preceding procedure.
Note: The permissions have to be set in the Hosts and Clusters view and the Virtual Machines and Templates view for the collection to occur. The above information applies to the vRealize Operations Appliance which has not performed any discovery yet on the objects of the vCenter Inventory. When the appliance has discovered the objects, it continues to show up in the list of objects and consume licenses. Currently there is no supported method to remove these objects from vRealize Operations Manager (formerly known as vCenter Operations Manager) Standard/Advanced editions, either 1.x or 5.x. If you want to remove the objects once already discovered, the only supported method is to perform a reinstall. 

Additional Information

For translated versions of this article, see:

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 12 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 12 Ratings