vRealize Operations Manager consists of one or more nodes, in a cluster. To create nodes, you use the vSphere client to download and deploy the vRealize Operations Manager virtual machine, once for each cluster node.

Do not deploy vRealize Operations from an ESXi host. Deploy only from vCenter Server.

For effective backup, deploy a high availability replica node on different hardware from the master node.

Verify that you have permissions to deploy OVF templates to the inventory.

If the ESXi host is part of a cluster, enable DRS in the cluster. If an ESXi host belongs to a non-DRS cluster, all resource pool functions are disabled.

From your network administrator, reserve a static IP address for the virtual machine, and know the associated domain name server, default gateway, and network mask values.

Plan your domain and machine naming so that the deployed virtual machine will not contain an underscore character (_) in its host name or anywhere in the fully qualified domain name (FQDN).

Download the vRealize Operations Manager .ova file to a location that is accessible to the vSphere client.

If you download the virtual machine and the file extension is .tar, change the file extension to .ova.

Verify that you are connected to a vCenter Server system with a vSphere client, and log in to the vSphere client.


Select File > Deploy OVF Template.


Enter the path to the vRealize Operations Manager .ova file.


Follow the prompts until you are asked for the node name.


Enter a node name. Examples might include Ops-Master or Ops-Data.

Do not include underscore characters (_) in node names.

Use a different name for each vRealize Operations Manager node.


Follow the prompts until you are asked to select a configuration size.


For the configuration size, select any size option.

Default disk space is allocated regardless of which size you select. If you need additional space to accommodate the expected data, add more disk after deploying the vApp.


Follow the prompts until you are asked to select the disk format.



Thick Provision Lazy Zeroed

Creates a virtual disk in a default thick format.

Thick Provision Eager Zeroed

Creates a type of thick virtual disk that supports clustering features such as Fault Tolerance. Thick provisioned eager-zeroed format can improve performance depending on the underlying storage subsystem.

Select the thick provisioned eager-zero option when possible.

Thin Provision

Creates a disk in thin format. Use this format to save storage space.

Snapshots can negatively affect the performance of a virtual machine and typically result in a 25–30 percent degradation for the vRealize Operations Manager workload. Do not use snapshots.


Click Next.


From the drop-down menu, select a Destination Network, for example, Network 1 = TEST, and click Next.


In Properties, under Application, Timezone Setting, select your time zone or leave the default of UTC.

Use UTC if cluster nodes will be distributed across different time zones.


Under Networking Properties, leave the entries blank for DHCP, or fill in the default gateway, domain name server, static IP address, and network mask values.

The master node and replica node require a static IP. A data node or remote collector node may use DHCP or static IP.


Click Next.


Review the settings and click Finish.


If you are creating a multiple-node vRealize Operations Manager cluster, repeat Step 1 through Step 13 to deploy each node.

Use a Web browser client to configure a newly added node as the vRealize Operations Manager master node, a data node, a high availability master replica node, or a remote collector node. The master node is required first.


For security, do not access vRealize Operations Manager from untrusted or unpatched clients, or from clients using browser extensions.