Install the Omnissa Access OVA File

You deploy the Omnissa Access OVA file using the vSphere Web Client. You can download and deploy the OVA file from a local location that is accessible to the vSphere Web Client, or deploy it from a Web URL.

Prerequisites

Review Preparing to Install Omnissa Access.

Procedure

1. Download the Omnissa Access OVA file from Customer Connect.

2. Log into the vSphere Client.

3. Select File > Deploy OVF Template.

4. In the Deploy OVF Template wizard, specify the following information.

   Page	Description
   Source	Browse to the OVA package location, or enter a specific URL.
   OVF Template Details	Review the product details, including version and size requirements.
   End User License Agreement	Read the End User License Agreement and click Accept.
   Name and Location	Enter a name for the Omnissa Access virtual appliance. The name must be unique within the inventory folder and can contain up to 80 characters. Names are case sensitive. Select a location for the virtual appliance.
   Host / Cluster	Select the host or cluster in which to run the virtual appliance.
   Resource Pool	Select the resource pool.
   Storage	Select the storage for the virtual appliance files. You can also select a VM Storage Profile.
   Disk Format	Select the disk format for the files. For production environments, select one of the Thick Provision formats. Use the Thin Provision format for evaluation and testing. In the Thick Provision format, all the space required for the virtual disk is allocated during deployment. In the Thin Provision format, the disk uses only the amount of storage space that it needs for its initial operations.
   Network Mapping	Map the networks used in Omnissa Access to networks in your inventory.
   Properties	Timezone setting  Select the correct time zone.   Join the Omnissa Customer Experience Improvement Program This product participates in Omnissa's Customer Experience Improvement Program ("CEIP"). Details regarding the data collected through CEIP and the purposes for which it is used by Omnissa are set forth at the Omnissa Trust Center. If you prefer not to participate in Omnissa's CEIP for this product, uncheck the box. You can also join or leave the CEIP for this product at any time after installation. Note: If your network is configured to access the Internet through HTTP proxy, to send the data collected through CEIP to Omnissa you must adjust the proxy settings in the Omnissa Access virtual appliance. See Enabling Proxy Server Settings After Installation of Omnissa Access Host Name (FQDN)   Enter the host name to use. If this is blank, reverse DNS is used to look up the host name. Networking Properties To configure a static IP address for Omnissa Access, enter the address for the Default Gateway, DNS, IP Address, and Netmask fields. Note: You have a load balancer with a Virtual IP address (VIP) in front of the DNS servers, note that Omnissa Access does not support using a VIP. You can specify multiple DNS servers separated by a comma.  Important: If any of the four address fields, including Host Name, are left blank, DHCP is used.  To configure DHCP, leave the address fields blank.< Note: The  Domain Name and Domain Search Path fields are not used. You can leave these blank. (Optional) After Omnissa Access is installed, you can configure IP Pools. See (Optional) Add IP Pools to the Omnissa Access Virtual Appliance.
   Ready to Complete	Review your selections and click Finish.

Depending on your network speed, the deployment can take several minutes. You can view the progress in the progress dialog box that appears.

5. When the deployment is complete, click Close in the progress dialog box.

6. Select the Omnissa Access virtual appliance you deployed, right-click, and select Power > Power on.

   The virtual appliance is initialized. When the initialization is complete, the console screen displays the Omnissa Access version, IP address, and the URLs to log in to the Omnissa Access console and to complete the set up.

   Note: An error message might appear about the network not being detected. You can still access the https://WS1AccessHostnameFQDN:8443/cfg/ page to configure the Omnissa Access settings. Rebooting the Omnissa Access virtual appliance clears the error message.