VMware® Horizon Workspace™ 1.5 Release Notes
Horizon Workspace Server 1.5 | 10 SEP 2013 | Build 1318295
Horizon Workspace Client for Windows | 30 JUL 2013 | Build 1221212
Horizon Workspace Client for Mac | 30 JUL 2013 | Build 1221184
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: 11 SEP 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 release of Horizon Workspace:
- Management of VMware® Ready™ Android Devices. Added Android container management for VMware Ready devices.
- Oracle Support. Added Oracle and Oracle RAC as supported databases.
- Unified Policies. Made changes to the policy framework for consistency and flexibility. Added a policy previewer.
- Localized Support. Support for French, German, Japanese and Simplified Chinese localizations.
- Change in VMware® ThinApp™ licensing tracking. Added per-device licensing support for ThinApp packages.
- Customizable Getting Started Guide. A Word template with graphics that you can use to create a customized Horizon Workspace getting started guide to meet the unique needs of your end users. See the Getting Started ZIP file.
- Numerous Bug Fixes. Improved the stability, performance, and scale of Horizon Workspace by implementing a variety of bug fixes.
Horizon Workspace 1.5 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, and 5.1 U1
- ESXi 5.0 U2, 5.1, and 5.1 U1
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 Horizon Workspace 1.0 to Horizon Workspace 1.5, inform users that they must uninstall their Horizon Workspace 1.0 clients and install the Horizon Workspace 1.5 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, 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
Clients - Client for iOS
Clients - Client for Windows
- On iOS devices, Horizon Workspace users cannot preview any files when they are offline*
While online, Horizon Workspace users on iOS devices can preview their files. However, when they are offline, their files are not visible.
Clients - Switch
- 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 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.
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.
- When users unlink their Windows computers from Horizon Workspace, downloaded ThinApp packages are still present on the local disk*
When users unlink their Windows computers from Horizon Workspace, a message appears indicating that Windows applications captured as ThinApp packages are being removed. The Start Menu shortcuts are removed. However, the downloaded ThinApp packages are still present in the ProgramData\ThinAppCache folder, even though users cannot invoke them.
Workaround: If you need to recapture the disk space, you can safely delete unentitled ThinApp packages from the ProgramData\ThinAppCache folder.