VMware® Horizon Workspace™ 1.5.1 Release Notes
Horizon Workspace Server 1.5 | 10 SEP 2013 | Build 1318295
Horizon Workspace Client for Windows | 10 OCT 2013 | Build 1357204
Horizon Workspace Client for Mac | 10 OCT 2013 | Build 1357160
Horizon Workspace Client for Android (Application published on Google Play Store)
Horizon Workspace Client for iOS (Application published on Apple App Store)
Horizon Files for iOS (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.1 release:
Horizon Workspace 1.5.1 is available in the following languages:
- Simplified Chinese
Compatibility, Installation, and Upgrade
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 server 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.
To access the full set of Horizon Workspace 1.5 documentation which also applies to the 1.5.1 release, go to the Horizon Workspace landing page.
This release resolves the following issues in Horizon Workspace clients.
- On iOS devices, Horizon Workspace users cannot preview any files when they are offline
Fixed a problem in Horizon Files for iOS that while offline, Horizon Workspace users on iOS devices could not preview their favorite files. Files that are marked as favorites are visible in the Offline area of Horizon Files for iOS.
- When users unlink their Windows computers from Horizon Workspace, downloaded ThinApp packages are still present on the local disk even though a message states that packages are removed.
Fixed a message inconsistency that when a user unlinks their Windows system from Horizon Workspace, a message appeared indicating that Windows applications captured as ThinApp packages are being removed even though the packages remained in the ThinApp package cache location on the Windows system. With this fix, when a user unlinks their Windows system from Horizon Workspace, that action does not affect the cached ThinApp packages. The packages are kept there to save bandwidth usage in case the administrator re-entitles that user or another entitled user uses that Windows system. Even though the packages remain in the cache location, the user cannot run the applications if the user is not entitled to the ThinApp package in your Horizon Workspace system. To remove a user's ability to use a ThinApp package, you should remove that user's entitlement to that package using the Horizon Workspace Administrator Web interface. The message that appears when a user unlinks the Windows system is intended to describe what happens to the files and folders used with the Horizon Files service.
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
Clients - Client for Mac
- Client might stop working when the system's network proxy settings are configured to use automatic proxy settings and the Horizon Workspace server is not listed in the bypass proxy settings list*
Sometimes if the Mac system has its network proxies configured to use the Auto Proxy Discovery or Automatic Proxy Configuration protocol and is not also set to bypass proxy settings for your Horizon Workspace server, the client might cease to function.
- If you want to retain the automatic proxy settings, add the host name for your Horizon Workspace server to the bypass proxy settings list of hosts and domains.
- If you do not want to add the host name for your Horizon Workspace server to the bypass proxy settings list, disable the automatic proxy settings protocol that is selected in the network proxies. For those systems that require use of a proxy, you can specify an HTTPS proxy manually by selecting the Secure Web Proxy (HTTPS) protocol and specifying your secure web proxy server and port.
Clients - Client for Windows
- Client displays message that the entered URL is not a valid Horizon server address when there are problems with the Mac system's /etc/resolv.conf file*
If the resolv.conf file in the /etc folder on the Mac system has problems, the Horizon Workspace client cannot resolve the Horizon Workspace server URL and displays a message stating that the server address is invalid.
- On the Mac system, in a terminal window, create a symbolic link from /etc/resolv.conf to /var/run/resolv.conf using the ln -s command: sudo ln -s /var/run/resolv.conf /etc/resolv.conf
If there is already a resolv.conf file in /etc, before running the ln -s command, delete the existing resolv.conf file or rename it (sudo mv resolv.conf resolv.conf.bak).
Clients - Switch
- When the system's network settings are configured to use an automatic configuration script, and the auto-configuration script is incorrectly configured, cannot be located at the specified location, or is corrupted, problems with installing the client, running the client, and using ThinApp packages can occur.*
If the LAN settings in the Windows system's Internet Explorer browser have Use automatic configuration script for proxy detection, but the script file is not present at the specified location or is corrupt or otherwise invalid, the following symptoms can occur:
- When installing the Horizon Workspace client, the installer might appear hung at the Validating Horizon server step, and does not return either a success or failure message.
- While launching or running an installed client, the Horizon Workspace tray icon might become unresponsive: the tray menu does not appear when you click on it. Also, the user's workspace files and applications might stop syncing.
- ThinApp packages might stop syncing, and appear to be unresponsive.
- Ensure that a valid automatic configuration file is located at the address specified for the Use automatic configuration script network settings, and then stop and restart the Horizon Workspace application:
- End the HorizonWorkspace.exe process by opening the Windows Task Manager, locating the HorizonWorkspace.exe process in the list, right-clicking it, and selecting End Process.
- Launch either the Horizon Workspace installer, if the symptom occurred during installation, or the Horizon Workspace application.
- If you cannot restore the automatic configuration script to a valid state, or if the same symptoms persist, change the LAN settings in the system's Internet Explorer browser to automatically detect proxy settings. After changing the LAN settings, end the HorizonWorkspace.exe process using Windows Task Manager, and then re-launch the application.
- Users suddenly cannot access ThinApp packages
Some entitled users might not be able to access ThinApp packages in certain situations. For example, after the Client for Windows shuts down or after you upgrade the client.
- Check for PrepareSql errors in the horizon.log file.
The existence of such errors is an indication that a ThinAgentLease.db file might exist in user's profiles.
- For the affected users, check their Windows systems for a ThinAgentLease.db file in their user profile.
- Delete the file if it exists.
Users cannot use the embedded Chinese input method editor on VMware Ready Android devices
Chinese Pinyin IME for Android is the embedded Chinese input method editor (IME) for VMware Ready devices. When Horizon Workspace users attempt to use this embedded tool, they do not have access to a majority of the Chinese characters.
Workaround: To change the Chinese IME on the managed mobile workspaces of VMware Ready Android devices, perform the following steps:
- Import a preferred simplified Chinese IME Android application. See Horizon Workspace documentation for information about importing a mobile application in to your catalog.
- Entitle VMware Ready Android device users to the new Chinese IME application.
- Horizon View Client for Android 2.0.0 stops working while downloading a desktop view to Android devices
On VMware Ready Android devices, when Horizon View Client for Android 2.0.0 users attempt to download a desktop view to their devices, Horizon View stops unexpectedly.
- Import the Horizon View Client for Android 2.1.0 or higher application. See Horizon Workspace documentation for information about importing a mobile application into your catalog.
- Entitle VMware Ready Android device users to the new View client.
The VMware Switch client application ignores passcode policies that allow passcodes to be fewer than four characters
The Horizon Workspace Administrator Web interface allows you to set a policy to require a passcode with a minimum length of fewer than four characters. However, the Switch client application on VMware Ready Android devices requires users to create passcodes with at least four characters.
Workaround: Set passcode policies to require a minimum length of four characters.
- Documentation does not include a step that is required when you upgrade a Horizon Workspace 1.0 deployment with multiple service-va instances to Horizon Workspace 1.5
When your Horizon Workspace 1.0 deployment has more than one service-va instance and you upgrade to Horizon Workspace 1.5, the masterkeys.uber file is not the same on all the service-va instances. At that point, the masterkeys.uber file exists on each service-va instance, but with different content. This might result in Horizon Workspace log in issues.
When you upgrade a Horizon Workspace 1.0 deployment that includes multiple service-va instances to 1.5 follow the Upgrading Horizon Workspace guide while also implementing the following instructions:
- After running the updatemgr.hzn command in the configurator-va virtual machine as described in step 2 of "Upgrading Horizon Workspace to Version 1.5," access the command line of one of the service-va instances.
- Copy the /usr/local/horizon/bin/masterkeys.uber file from one of the service-va instances to all the other service-va instances in your deployment.
You can copy the file from any service-va instance as long as the masterkeys.uber file ends up being exactly the same on every service-va instance.
- Restart the appropriate servers.
- 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.
- 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.
Horizon Workspace Server
- The NFS issues a misleading error message when you attempt to add an NFS mount
When you attempt to add an NFS mount, the NFS issues the following message:
Error occurred: directory does not exist or is not writable: /opt/zimbra/store<XX>
The cause of this problem is related to NFS permissions on the server side, which is not clear from the wording of the message.
Workaround: If you see the preceding error, ensure that you have write permissions on the NFS server folder structure being exported.
- 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.