VMware® Horizon Workspace™ 1.5.2 Release Notes
This Horizon Workspace 1.5.2 release is a client-only release. The Horizon Workspace Server version is 1.5. The Horizon Workspace client versions 1.5.1 and 1.5.2 are compatible with Horizon Workspace Server 1.5.
Horizon Workspace Server 1.5 | 10 SEP 2013 | Build 1318295
Horizon Workspace Desktop Clients 1.5.2 | 03 DEC 2013 | Build 1444866
Horizon Workspace Client for Android 1.5.2 (Application published on Google Play Store)
Horizon Workspace Client for iOS 1.5.2 (Application published on Apple App Store)
Horizon Files for iOS 1.5.2 (Application published on Apple App Store)
VMware Switch (Application published on Google Play Store)
Last updated: 17 DEC 2013
What's in the Release Notes
The release notes cover the following topics:
The following information describes some of the enhancements available in this Horizon Workspace 1.5.2 release:
- Updated Horizon Workspace clients.
In this release, the following client applications are updated:
- Horizon Workspace Client for Windows
- Horizon Workspace Client for Mac
- Horizon Workspace Cilent for Android
- Horizon Files for iOS
Horizon Workspace 1.5 and later is available in the following languages:
- Simplified Chinese
Compatibility, Installation, and Upgrade Horizon Server 1.5
VMware® vCenter™ and VMware ESXi™ Compatibility
Horizon Workspace supports the following versions of vCenter and ESXi:
- vCenter 5.0 U2, 5.1, 5.1 U1, and 5.5
- ESXi 5.0 U2, 5.1, 5.1 U1, and 5.5
Browser Compatibility for the Administrator Web Interfaces
The following Web browsers can be used to view the Configurator Web interface, Connector Web interface, and Administrator Web interface:
- Mozilla Firefox (latest)
- Google Chrome (latest)
- Internet Explorer 9 or 10
- Safari (latest)
For other system requirements, see Installing and Configuring Horizon Workspace on the Horizon Workspace landing page.
Horizon Workspace Component Compatibility
VMware Product Interoperability Matrix provides details about the compatibility of current and previous versions of VMware products and components, such as VMware vCenter Server, VMware ThinApp and VMware® Horizon View™.
Upgrading from Horizon Workspace 1.0
If you upgrade your Horizon Workspace 1.0 system to Horizon Workspace 1.5, inform users that they must uninstall their Horizon Workspace 1.0 clients and install the latest Horizon Workspace clients to access the updated server. Therefore, users must update the following clients: Horizon Workspace Client for Windows, Horizon Workspace Client for Mac, Horizon Workspace Client for Android, Horizon Workspace Client for iOS.
For additional information about system requirements and installation and upgrade instructions, see Installing and Configuring Horizon Workspace and Upgrading Horizon Workspace.
Adding Workspace Desktop Installers to Horizon Workspace
To enable users to download the desktop clients and to automatically update the desktop client for Windows with a new version, you must add the desktop clients installer files to the downloads directory and to the auto-update directory on the data-va virtual machines.
For automatic update, the Horizon Workspace desktop client for Windows polls the Horizon Workspace server every two hours for a new version. When a new version is found, the desktop client is automatically updated.
Users must have administrator privileges on their computers to install and automatically update the desktop client.
IMPORTANT: If the Horizon Workspace Client for Windows application is installed on your floating (non-dedicated) Horizon View Desktops, first, update the Horizon Workspace Client for Windows app on the Horizon View floating pool master image to 1.5.2. Before you add the installer to the master image, make sure that auto-update is disabled in the installer file for Windows. See Better Performance with Horizon Workspace Client for Windows in View Desktop Pools in this release note for more information. After the master image is updated, follow the steps below to add the 1.5.2 installers to the Horizon Workspace data-va virtual machines. If you update the data-va virtual machine before you update the floating pool master image, it can lead to unpredictable results in the floating pools.
Add Desktop Client Installer Files to Data-va Virtual Machines
You copy and install a zip file that includes the desktop client files for Windows and Mac computers from the VMware downloads page to each data-va virtual machine that is configured. You run the check-client-updates command on each data-va virtual machine to deploy the installer files and restart the data-va virtual machines.
- Download the Horizon Workspace desktop client zip file from the VMware website https://my.vmware.com/web/vmware/downloads
- Copy the zip file to a temporary location on the data-va virtual machine. scp clients-n.n.n-nnnn.zip root@yourDataServer.com:/tmp/
- Log in to the data-va machine as the root user.
- To unzip and install the new clients to the downloads directory and to the directory that automatically updates users clients and restart the data-va virtual machine, type /opt/vmware-hdva-installer/bin/check-client-updates.pl --install --clientfile /tmp/clients-n.n.n-nnnn.zip
This script unzips the file and copies the desktop clients installer files for Windows and for Mac computer to the /opt/zimbra/jetty/webapps/zimbra/downloads directory and for the automatic updates to the /opt/zimbra/jetty/webapps/zimbra//public/cds directory, and updates the URL parameter value for the downloads link. The data-va virtual machine is restarted.
- Run steps 1 through 4 on each data-va virtual machine in your environment
Users can now download the desktop clients from their Horizon Workspace accounts and Horizon Workspace Client for Windows user's desktop clients are automatically updated.
To access the full set of Horizon Workspace 1.5 documentation which also applies to the 1.5.2 release, go to the Horizon Workspace landing page.
The known Horizon Workspace issues added in the most recent release are marked with the * symbol. Other known issues have been carried forward from previous releases. This section describes known issues for the following subject areas:
Clients - Client for Android
- If you perform this workaround after you upgraded to Horizon Workspace 1.5, issue the following command in each service-va instance to which you copied the file to restart the front-end Web application:
service horizon-frontend start
- If you perform the upgrade as part of this workaround, complete the rest of the steps in the procedure, which includes powering off and on the vApp.
- Documentation does not mention that you can specify the IP addresses the gateway includes in the X-Forwarded-For header
The Horizon Workspace documentation should indicate that you can specify IP addresses the gateway uses for client identification on the X-Forwarded-For page. The Horizon Workspace gateway uses the X-Forwarded-For header to identify source IP addresses from the browser client and determines which Connector to log in to based on this IP address. You must add the IP addresses for any load balancer or gateway between the Horizon Workspace gateway and the end user to the X-Forwarded-For page. The IP addresses that you add on the X-Forwarded-For page are automatically populated to all the gateways in your environment.
Workaround: Add the IP addresses for any load balancers or gateways between the Horizon Workspace gateway and the end user via the X-Forwarded-For page in the wizard during setup or after setup in the Horizon Workspace Configurator’s X-Forwarded-For tab.
- Documentation does not specify that a user's Windows system must be joined to the domain to sync with Windows applications captured as ThinApp packages
The Horizon Workspace documentation should indicate that for Horizon Workspace users to access Windows applications captured as ThinApp packages, the Horizon Workspace Client for Windows must be installed on a Windows system that was joined to the domain. If the machine is not joined to the domain, ThinApp packages cannot sync with the client.
Workaround: If you want to provide Horizon Workspace users with access to ThinApp packages, ensure that their Windows systems, with the Horizon Workspace Client for Windows installed, are joined to the domain.
- Documentation correction required for high availability topic
In the Installing and Configuring Horizon Workspace for Horizon Workspace 1.5, the topic "Setting Up VMware High Availability Monitoring for the data-va Virtual Machine" requires corrections to step 6. What the step refers to as the "default heartbeat timeout" should be the "Failure interval" and the setting of "200 seconds or greater" should be "300 seconds or greater."
Workaround: Use the following instructions for step 6 instead of the instructions currently in the guide: Configure the Failure interval setting to 300 seconds or greater.
- Documentation correction required for external database requirements
In the Installing and Configuring Horizon Workspace for Horizon Workspace 1.5, the topics "System and Network Configuration Requirements", "Using the Configurator to Configure Horizon Workspace to Use an External Database", and "Configuring a PostgreSQL Database" list specific versions of VMware vFabric PostgreSQL and Oracle databases. However, the listed versions in those topics are incomplete and do not match the Solution/Database Interoperability information in the VMware Product Interoperability Matrix.
Workaround: Use the VMware Product Interoperability Matrix as the official list of the external database requirements.
Horizon Workspace Server
- Documentation correction required for configuring redundancy/failover topic
In the Installing and Configuring Horizon Workspace for Horizon Workspace 1.5, the topic "Configuring Redundancy/Failover for Horizon Workspace Virtual Machines" requires a correction. The topic states that a base snapshot must exist before creating a new connector-va. Actually, when you run the hznAdminTool addvm command, it takes a snapshot of the first connector-va and a full clone is created based on that.
- The Connector Web interface issues an incomplete error message about the characters an attribute name can contain
When you attempt to enter an invalid attribute name, the Connector Web interface displays an error message that does not indicate that blank spaces are also allowed in the name.
If you encounter the following error message when providing an attribute name in the Connector, be aware that it is incomplete;
Invalid horizon name. The horizon name must contain only alphanumeric (A-Z, a-z, 0-9), period (.), underscore (_), hyphen and at sign (@).
Note that in this situation, the following message is actually correct:
Invalid horizon name. The horizon name must contain only alphanumeric (A-Z, a-z, 0-9), period (.), underscore (_), hyphen , at sign (@), and blank space.
- Horizon Workspace returns an incomplete list when search results exceed 1,000 users and groups
When you search for users or groups with the Administrator Web interface, the maximum number of results Horizon Workspace returns is 1,000.
Workaround: Use a more restrictive search to find all matching records.
- The Connector allows you to remove the Bind DN user account that has administrative access to Horizon Workspace
Initially, only the Active Directory user associated with the Bind DN user account has administrative access to Horizon Workspace. The following actions can result in you unintentionally removing the Bind DN user account from Application Manager:
- You filter out the Bind DN user account in the Connector when you select users.
- You make the Bind DN user account invalid for directory synchronization by making a user attribute a required attribute while the Bind DN user account does not have that attribute.
At the next directory synchronization, following one of the preceding actions, Horizon Workspace receives changes from Active Directory, which includes the removal of the Bind DN user account. At this point, you can no longer log in to Horizon Workspace as an administrator. While you can add the Bind DN user account back, the account will no longer have administrative privileges.
Login to Horizon Workspace (https://HorizonWorkspaceFQDN/SAAS/login/0) using your non-Active Directory administrator account and promote the Bind DN user account to the Administrator role.
Better Performance with Horizon Workspace Client for Windows in View Desktop Pools
When Horizon Workspace Client for Windows is installed in a
non-dedicated (floating) Horizon View desktop, you need to make changes to the
Horizon Workspace client for Windows installer program so that the client
desktop does not try to download the ThinApp packages or Horizon Files app every
time a new View pool session is created.
Because non-dedicated desktops are inherently stateless and
new sessions can be created when the desktops are recomposed or the user is given
a new desktop from the pool, if the Horizon Workspace Client for Windows
configuration is not modified, end user will notice slow or bad performance
when using these applications.
Beginning with Horizon Workspace Client for Windows 1.5.2, you
can modify the client installer program to make the following modification before
the View administrator installs the client to the View template.
- Turn off auto-updates of the Windows client. ENABLE_AUTOUPDATE=0
- If you are using ThinApp packages, enable streaming mode for ThinApp. INSTALL_MODE=RUN_FROM_SHARE
- If end users do not need to sync Horizon Files in these desktops,
disable the Files application. ENABLE_DATA=0
- If you plan to support Horizon Files in these desktops, redirect the
files to a network share that can be accessed from these desktops.
Where #: is a mapped network drive or UNC path. To set the path so that it is appropriately created
and mapped for each user, escape the environment variables. (that is with "^"
escape characters) in the key-value pair used in the command.
IMPORTANT: In Release 1.5.2, when you implement these changes, inform your end users that they should not change their Horizon Workspace settings. In a future release the Unlink this computer setting and the ability to change the directory path for their Horizon Folder will be disabled.
Download the EXE file for the Windows client installer program to a Windows system to make these changes.
The following is an example of the command where auto-updates is disabled, streaming mode for ThinApp packages is enabled and the Horizon Files folders are saved to a network shared drive that users can access.