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.
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 vCenter Operations Manager on such clusters.
Note: For vSphere Essentials, you must deploy the vApp on a standalone host.
- Remove one of the ESX hosts from the cluster so that it resides directly under the parent datacenter.
- On that ESX host, deploy the vCenter Operations Manager vApp, specifying static IP addresses.
- Power on the vApp before moving the host back into the cluser to ensure IP settings are picked up.
- License the solution in vCenter.
- Move the ESX host with vCenter Operations back into the cluster.
Note: Static IP addresses are required.
Warning: The steps above 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 vCenter 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. vCenter 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.