VMware Pulse IoT Center is distributed as an Open Virtual Appliance (OVA) and can be deployed on a VMware vCenter instance through the vSphere Web Client. For supported versions of vSphere, see the VMware Product Interoperability Matrix at https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#interop

Perform the following steps to deploy a load balancer node using the OVA deployed on a VMware vCenter instance through the vSphere Web Client.


You must have a valid URL to the VMware Pulse IoT Center OVA.


  1. Log in to your vCenter environment with administrator privileges.
  2. Right-click any inventory object that is a valid parent object of a virtual machine, such as a data center, folder, cluster, resource pool, or host, and select Deploy OVF Template
    The Deploy OVF Template wizard opens.
  3. On the Select an OVF template page, specify the location of the source OVA template and click Next. The options available are as described in the below table:
    Option Action
    URL Type a URL to the OVA template on the Internet. Supported URL sources are HTTP and HTTPS.
    Local file Click Choose Files and select all the files associated with the OVA file. This includes files such as .ovf, .vmdk, and so on. If you do not select all the required files, a warning message is displayed.
  4. On the Select a name and folder page, enter a unique name for your virtual machine, select a deployment location, and click Next.
    Note: The default name for the virtual appliance is the same as the name of the selected OVA template. The default deployment location is the inventory object where you started the wizard.
  5. On the Select a compute resource page, select a resource where to run the deployed virtual appliance template, and click Next.
  6. On the Review details page, verify the version, required disk space on the datastore, and click Next.
  7. On the Select storage page, define where and how to store the files for the deployed OVA template.
    1. Select a disk format for the virtual machine virtual disks.
      Format Description
      Thick Provision Lazy Zeroed Creates a virtual disk in a default thick format. Space required for the virtual disk is allocated when the virtual disk is created. Data remaining on the physical device is not erased during creation, but is zeroed out later, on demand, on first write from the virtual machine.
      Thick Provision Eager Zeroed A type of thick virtual disk that supports clustering features such as Fault Tolerance. Space required for the virtual disk is allocated at the time of creation. In contrast to the flat format, the data remaining on the physical device is zeroed out when the virtual disk is created. It might take much longer to create disks in this format than to create other types of disks.
      Thin Provision
      Note: It is recommended to use the thin provision format.
      Use this format to save hard disk space. For the thin disk, you provision as much datastore space as the disk requires based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations.
    2. Select a VM Storage Policy. This option is available only if storage policies are enabled on the destination resource.
    3. (Optional) Enable the show datastores from Storage DRS clusters check box to select individual datastores from Storage DRS clusters for the initial placement of the virtual machine.
    4. Select a datastore for storing the deployed OVA template.
    The configuration file and virtual disk files are stored on the datastore. Select a datastore large enough to accommodate the virtual appliance and all associated virtual disk files.
  8. Click Next.
  9. On the Select networks page, select a source network and map it to a destination network. Ensure that you select the correct virtual machine network to set up the static IP/DHCP as defined by your network administrator. Click Next.
  10. On the Customize template page:
    1. Enter and confirm the Admin Password for Node Management and Initial root password. These text boxes are mandatory.
    2. If you select DHCP as your network type, leave the Pulse IoTC Hostname text box blank.
    3. If your network type is Static IP, scroll down to see the Network Properties.
    4. If you are deploying a load balancer node, leave the Join Pulse Instance text box empty.
  11. Scroll down and expand the Networking Properties drop-down menu and enter the details.
    Figure 1. Deploy Customize Template
    Deploy Customize Template.
  12. Click Next.
  13. Ready to complete page, review the configuration details of your VMware Pulse IoT Center virtual appliance and click FINISH.


A new task for creating the virtual machine appears in the Recent Tasks pane. The deployment time depends on your network speed and infrastructure setup. After the task is complete, the new virtual machine is created on the selected resource.


What to do next

  1. Power on the newly created node and start the web console.
  2. After the virtual machine is powered on, refresh the page and note the IP address of the virtual appliance.
  3. Use this IP address or DNS name/FQDN (if configured) to access the VMware Pulse IoT Center console.
  4. Log in to the VMware Pulse IoT Center Administration console to set up the load balancer node. See Set Up the VMware Pulse IoT Center Load Balancer Node.