Search the VMware Knowledge Base (KB)
View by Article ID

Deploying VMware vRealize Operations Manager 5.x with vSphere Essentials, Essentials Plus, or Standard (2013695)

  • 27 Ratings


  • When attempting to deploy vRealize Operations Manager, the operation fails.
  • You see the error:

    The operation is not supported on the object.


Since vCenter Server 2.0 Distributed Resource Schedule (DRS) is required for deployment of a resource pool in a cluster, DRS is used to place the virtual machines in a vApp in the cluster.

Deploying vRealize Operations Manager 5.x on a standalone ESX host does not require DRS, but DRS is required to deploy vRealize Operations on a cluster.

vSphere Essentials and Essentials Plus kits support up to three ESX hosts. Essentials Plus supports vMotion and HA for clustering, but without DRS. The Standard kit supports eight processors and vMotion and HA for clustering, but also without DRS. This article provides a workaround if you want to use vRealize Operations Manager on such clusters.

Note: For vSphere Essentials, you must deploy the vApp on a standalone host.


To deploy vRealize Operations Manager in a vCenter Server environment with an Essentials Plus or Standard cluster of three ESX hosts:
  1. Remove one of the ESX hosts from the cluster so that it resides directly under the parent datacenter.
  2. On that ESX host, deploy the vRealize Operations Manager vApp, specifying static IP addresses.
  3. Power on the vApp before moving the host back into the cluster to ensure IP settings are picked up.
  4. License the solution in vCenter Server.
  5. Move the ESX host with vRealize Operations back into the cluster.
Note: Static IP addresses are required.

Warning: The preceding steps dissolve the vApp container and an error is displayed. Disregard the error message and continue moving the host into the cluster.

Moving the ESX host with the vRealize Operations vApp back into the cluster results in the addition of the two virtual machines (the UI virtual machine and the Analytics virtual machine) to the cluster, without the vApp container. vRealize Operations Manager 5.x continues to function normally when this happens.

  • If you want to change the IP address of the virtual machines in the future, run a repair in the UI virtual machine because the vApp structure no longer exists in vCenter Server.
  • Because the vApp structure no longer exists, you must power off the UI virtual machine, wait for 10 minutes, and then power off the Analytics virtual machine.
  • To power on the virtual machines, first power on the Analytics virtual machine, wait for 10 minutes, and then power on the UI virtual machine.

Additional Information

See Also

This Article Replaces


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.


  • 27 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)

Please enter the Captcha code before clicking Submit.
  • 27 Ratings