Setting Up for Linux Desktops

n
For RHEL/CentOS 6.x and SLED 11 SP3/SP4, for the SSO login session to use KDE, remove all the
desktop startup files, except for the KDE startup file, from the /usr/share/xsession directory. Use
the following set of commands as an example.
# cd /usr/share/xsessions
# mkdir backup
# mv *.desktop backup
# mv backup/kde*.desktop ./
After the initial setup, the end user must log out or reboot their Linux desktop to make KDE as the
default desktop in their next SSO session.
If you disabled SSO on a Linux desktop that has multiple desktop environments installed, you do not
need to perform any of the previously described steps. The end users have to select their desired desktop
environment when they log in to that Linux desktop.
Network Requirements
VMware Blast Extreme supports both User Datagram Protocol (UDP) and Transmission Control Protocol
(TCP), and their performances are affected by the network condition. To receive the best user experience,
select UDP or TCP based on the network condition.
n
Select TCP if the network condition is good, such as in a local area network (LAN) environment.
n
Select UDP if the network condition is poor, such as in a wide area network (WAN) environment with
packet loss and time delay.
Use a network analyzer tool, such as Wireshark, to determine whether VMware Blast Extreme is using
TCP or UDP. Use the following set of steps, which use Wireshark, as a reference example.
1 Download and install Wireshark on your Linux VM.
For RHEL/CentOS 6:
sudo yum install wireshark
For Ubuntu 14.04/16.04:
sudo apt install tshark
For SLE 11/12:
sudo zypper install wireshark
2 Connect to the Linux desktop using VMware Horizon Client.
3 Open a terminal window and run the following command, which displays the TCP package or UDP
package used by VMware Blast Extreme.
sudo tshark -i any | grep 22443
Setting Up Horizon 7 for Linux Desktops
VMware, Inc. 17