You must perform certain tasks to prepare a Linux machine for use as a desktop in a Horizon 7 deployment.
Before a Linux machine can be managed by Horizon 7, the machine must be able to communicate with Connection Server. You must configure networking on the Linux machine so that the Linux machine can ping the Connection Server instance using its FQDN (fully qualified domain name).
Open VMware Tools (OVT) are pre-installed on RHEL 7, CentOS 7, and SLED 12 machines. If you are preparing either of these machines for use as a remote desktop, you can skip steps 1 through 5 in the following procedure, which describe how to install VMware Tools by manually running the installer.
- Verify that a new virtual machine (VM) was created in vCenter Server and your Linux distribution was installed on the machine
- Familiarize yourself with the steps for mounting and installing VMware Tools on a Linux VM. See "Manually Install or Upgrade VMware Tools in a Linux Virtual Machine" in the vSphere Virtual Machine Administration document.
- Familiarize yourself with the steps for configuring your Linux machine to be resolvable through DNS. These steps vary for the different Linux distributions and releases. For instructions, consult the documentation for your Linux distribution and release.
- In vSphere Web Client or vSphere Client, mount the VMware Tools virtual disk on the VM.
- Right-click the VMware Tools installer file, VMwareTools.x.x.x-xxxx.tar.gz, click Extract to, and select the desktop for your Linux distribution.
The vmware-tools-distrib folder is extracted to the desktop.
- On the VM, log in as root and open a terminal window.
- Uncompress the VMware Tools tar installer file.
tar zxpf /mnt/cdrom/VMwareTools-x.x.x-yyyy.tar.gz
- Run the installer and configure VMware Tools.
The command might vary slightly in different Linux distributions. For example:
cd vmware-tools-distrib sudo ./vmware-install.pl -dUsually, the vmware-config-tools.pl configuration file runs after the installer file finishes running.
- For RHEL and CentOS, map the machine's host name to 127.0.0.1 in /etc/hosts.
This step is not necessary for Ubuntu because the mapping is there by default. This step is also not necessary when you bulk deploy desktops because the cloning process adds this mapping.
- For RHEL 7 and CentOS 7, verify that virbr0 is disabled.
virsh net-destroy default virsh net-undefine default service libvirtd restart
- Ensure that the View Connection Server instances in the pod can be resolved through DNS.
- Configure the Linux machine so that the default runlevel is 5.
The runlevel must be 5 for the Linux desktop to work.
- On an Ubuntu machine that was configured to authenticate with an OpenLDAP server, set the fully qualified domain name on the machine.
This step ensures that the information can be displayed correctly in the User field on the Sessions page in View Administrator. Edit the /etc/hosts file as follows:
# nano /etc/hosts
- Add the fully qualified domain name. For example:
127.0.0.1 hostname.domainname hostname.
- Exit and save the file.
- Edit /etc/nsswitch.conf and modify the
hostsentry as follows:
hosts: cache db files dnsThe default setting is
hosts: files dnsand might cause the Linux desktop to fail to recover from a temporary network outage. The desktop might lose communication with View Connection Server permanently and require a reboot to resolve the issue.
- For SUSE, disable Change Hostname via DHCP. Set the hostname or domain name.
- In Yast, click Network Settings.
- Click the Hostname/DNS tab.
- Deselect Change Hostname via DHCP.
- Enter the hostname and the domain name.
- Click OK.