In my role as a VMware Certified Instructor I often find myself warmly recommending my students to try vCenter Operations Manager in their environments, either test and development or production ones. When I do so, I'm fully convinced they can very much benefit from the precious informations they can get out of it, regardless they are an SMB, a Corporate or a Service Provider.
During a recent course, in Oslo (NO), one of the attendees mentioned a strange issue he had when he tried to deploy vCenter Operations Manager:
The operation is not supported on the object.
It turned out to be a problem related to the lack of Distributed Resource Scheduler (DRS) support when deploying the vCenter Operations Manager vApp within a cluster.
vCenter Operations Manager is distributed as a vApp - using the Open Virtualization Appliance (OVA) format - that you can import and deploy to a virtualization platform, such as vSphere. A vApp has the same basic operation as a virtual machine, but can contain multiple virtual machines or appliances. The same vApp exists for the Foundation (available in vSphere 5.1), Standard, Advanced, and Enterprise Editions.
vCenter Operations Manager architecture consists of two virtual machines:
- The UI VM allows you to access the results of the analytics in the form of badges and scores using the Web-based application for the UI VM. It also allows you access to the Administration Portal in order to perform management tasks.
- The Analytics VM is responsible for collecting data from vCenter Server, vCenter Configuration Manager, and third party data sources, such as metrics, topology, and change events. Raw data is stored in its scalable File System Database (FSDB).
VMware Knowledge Base
According to the VMware Knowledge Base article number 2013695 explaining the issue mentioned above, since VirtualCenter Server 2.0 (back in 2006), DRS is required for the deployment of a resource pool in a cluster. DRS is also used to place the virtual machines in a vApp within a cluster. Hence, even if deploying vCenter Operations Manager 5.x on a standalone ESXi host does not require DRS, deploying it on a cluster does require DRS.
As vSphere DRS is only available on vSphere Enterprise and Enterprise Plus editions, it is now clear that deploying vCenter Operations Manager 5.x in any other vSphere license edition will require some additional step.
To deploy vCenter Operations Manager 5.x in a vCenter Server environment with an Essentials Plus or Standard cluster of three ESX hosts:
- Remove one of the ESXi hosts from the cluster so that it resides directly under the parent datacenter.
- On that ESXi host, deploy the vCenter Operations Manager vApp, specifying static IP addresses.
- Power on the vApp before moving the host back into the cluster to ensure IP settings are picked up.
- License the solution in vCenter.
- Move the ESXi host with vCenter Operations back into the cluster.
Source: VMware Knowledge Base article #2013695
Title: "Deploying vCenter Operations Manager 5.x with vSphere Essentials, Essentials Plus, or Standard"