VMware

Horizon Workspace 1.0 Release Notes

Horizon Workspace 1.0 | 04 MAR 2013 | Build 1020976
Horizon Workspace Client for Windows | 04 MAR 2013 | Build 1028171
Horizon Workspace Client for Mac | 04 MAR 2013 | Build 1028153
Horizon Workspace Client for iOS | 04 MAR 2013 | Build 1018486
Horizon Workspace Client for Android | 04 MAR 2013 | Build 1014635

Last Document Update: 10 JUN 2013

What's in the Release Notes

The release notes cover the following topics:

Feature Highlights

Horizon Workspace provides secure access to applications and data on any mobile device or computer, simplifying the end-user experience while reducing management costs.

User Features

  • Everywhere data access - In the office, at home, or on the road.
  • Full data collaboration - Policy-based file sharing with anyone, including external users. Allows users to version files and comment on files.
  • Provide users with secure access to Web, mobile and Windows (ThinApp packages) applications.
  • Access data and applications from anywhere - On Windows, Mac OS X, iOS, and Android operating systems and on all major browsers.
  • Access View Desktops with single sign on (SSO).

Administrative Features

  • Manage files, devices, applications and the Data service through a single management console.
  • Provision users with Active Directory and user Horizon Workspace to create custom user groups.
  • Easily manage a single catalog for Web, mobile and Windows applications, View pools, and the Data service.
  • Set individual and group-based policies to manage application access and govern the usage of data.
  • Manage device security - Perform remote wipe, set data access policies, and application enforce PIN code.

System Requirements and Installation

vCenter and ESXi Compatibility

Horizon Workspace supports the following versions of vCenter and ESXi:

  • vCenter 5.0 U2 and 5.1
  • ESXi 5.0 U2 and 5.1

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 8 or 9 (Exception: the Connector Web interface does not work on Internet Explorer on Windows XP or Windows 2003 operating systems.)
  • Safari (latest)

For other system requirements, see Installing Horizon Workspace on the Horizon Workspace landing page.

Documentation

The following Horizon Workspace documentation is available on the Horizon Workspace landing page:

Administrators

  • Installing Horizon Workspace
  • Horizon Workspace Administrator's Guide
  • Horizon Workspace Data CLI Guide
  • Horizon Workspace Backup Data Best Practices

Users

  • Horizon Workspace Getting Started
  • Horizon Workspace Web and Desktop User Guide
  • Horizon Workspace iOS User Guide
  • Horizon Workspace Android User Guide
  • Tips for Fixing Horizon Workspace Client Sync Errors

Known Issues

This section describes Known Issues in this release for the following subject areas:

Data Service

  • Concurrent editing of a file by multiple users might fail
    Examples:
    • When one user is on line working in a folder and another user is offline working on the same folder a conflict occurs when changing a file name, editing a file, moving a file or folder.
    • When a file has been changed by more than one user and the changes are synced at the same time, only one version of the file is saved. No conflict warning is displayed.

    Workaround: Users need to manually review their files.

  • When using Internet Explorer 10 on Windows 8, the previewer of the Data service does not display certain file types
    In this situation, when users attempt to view a .PPT, .XLS, or .DOC file in the previewer, no content appears..

    Workaround:
    Users can install the Adobe Reader plugin.
  • When the grantor of a shared folder changes the permissions to allow editing, the recipient might not be able to edit some of the files in the folder
    In this situation, the read-only flag does not disappear after the grantor updates the folder's permissions to allow editing.

    Workaround:
    1. When the grantor changes the share access to edit, the grantor notifies the recipient of the change.
    2. The recipient changes the permissions on the folder manually.
    • On Windows Systems
      1. Open the folder named Horizon.
      2. Right-click the shared folder and click Properties to open the dialog box.
      3. In the Attributes section, uncheck the Read-only box.
    • On Mac Systems
      1. Open the folder named Horizon.
      2. Select the shared folder and choose File > Get Info.
      3. Click the triangle next to Sharing and Permissions
      4. Change the privilege to Read and Write.
  • New: Documentation lacks required information for adding NFS volumes to multiple data-va virtual machines that are exported from the same NFS server
    In the Horizon Workspace 1.0 guide, Installing Horizon Workspace, the topic "Adding Network Attached Storage for Storage," does not include required information regarding the mounting of the NFS volume..

    Workaround:
    Determine if the following note, which is specific to step 7 of the topic, applies to your situation. If applicable, follow the instructions in the note as described.
    NOTE: If you add NFS volumes to multiple data-va virtual machines that are exported from the same NFS server, you must use a dedicated export target for each data-va virtual machine in order to avoid data loss and unpredictable effects. The full export qualifier must be unique, NFSserver.example.com:/path/to/export/folder. If you use the hostname as the folder name that you want to export, it guarantees the name’s uniqueness and ensures that the folder can be easily identified. For example, nfsserver.example.com:/export/data-va1, nfsserver.example.com:/export/data-va2, and so on.

Installation
  • After you enable the View, Web Applications, or ThinApp Packages modules, you cannot disable them from a Horizon Workspace Web interface
    Workaround: Log in to your postgres database and run the query to disable the respective module.
    To disable the View module, run the following query:
    update saas."Module" set "enabled"=FALSE where "moduleName"='View'
    To disable Web Applications module, run the following query:
    update saas."Module" set "enabled"=FALSE where "moduleName"='SaaS'
    To disable ThinApp packages module, run the following query:
    update saas."Module" set "enabled"=FALSE where "moduleName"='ThinApp'
  • 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 can filter out the Bind DN user account in the Connector when you select users.
    • You can 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.

    Workaround:
    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.

  • New: Documentation for creating a new data-va virtual machine is not accurate
    In the Horizon Workspace 1.0 guide, Installing Horizon Workspace, the topic "Creating a New data-va Virtual Machine" is inaccurate or unclear in two locations.

    For step 5d, the path to the zmupdateauthkeys utility is incorrect. The name of the utility without the path is sufficient to run the command. The correct full path is /opt/zimbra/bin/zmupdateauthkeys.

    For step 6, the instructions do not specify where to run the command.

    The other steps in the procedure are correct. Follow those steps as written.

    Workaround:
    The correct steps are as follows:
    • 5d: Run the zmupdateauthkeys command.
    • 6: Go to each gateway-va instance and restart memcached as the root user.
      /etc/rc.d/memcached restart
  • New: Documentation fails to specify that Horizon Workspace does not support multiple Active Directory forests

    In the Horizon Workspace 1.0 guide, Installing Horizon Workspace, the topic "Configuring a Multi-domain Active Directory Domain Service Forest" does not specify that Horizon Workspace does not support multiple Active Directory Domain Server (AD DS) forests.

    Workaround:
    Consider the following support information before establishing a connection between Horizon Workspace and Active Directory.
    • What is supported: Configuring Horizon Workspace with a single multi-domain AD DS forest.
    • What is not supported: Configuring Horizon Workspace with multiple domains in multiple AD DS forests.
Internationalization
  • The previewer of the Data service does not accurately display plain text files that do not use UTF-8 encoding
    When users open a file that does not use UTF-8 encoding, the content appears as broken non-ASCII characters.

    Workaround: Users should upload and preview plain text files with UTF-8 encoding.
ThinApp Packages
  • 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 from Application Manager 1.5.

    Workaround:
    1. 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.
    2. For the affected users, check their Windows systems for a ThinAgentLease.db file in their user profile.
    3. Delete the file if it exists.
  • New: Horizon Workspace 1.0 documentation about ThinApp package deployment mode is incorrect
    In the Horizon Workspace Administrator's Guide, the topic "Silently Deploy Horizon Workspace Client for Windows on Users' Windows Systems" is inaccurate in one location.

    The current instructions incorrectly state that when you create a script to silently install Horizon Workspace Client for Windows and do not specify the ThinApp package deployment mode, the default value of 0 applies. The default deployment mode is acutally 1.

    Workaround:
    Use the following corrected information when silently installing Horizon Workspace Client for Windows:

    The DOWNLOAD variable key enables you to select the ThinApp package deployment mode: 1 denotes download mode, 0 denotes streaming mode. If unspecified, the default value of 1, download mode, applies.

View Pools
  • When users using Internet Explorer 8.0 to access Horizon Workspace click a View Pool icon or select Launch by View Client, a security warning might appear

    Workaround
    Change the security level setting in Internet Explorer.
    1. Open Internet Explorer.
    2. Click Tools > Internet Options
    3. Click the Security tab.
    4. Click Custom level.
    5. Click Enable for the Display Mixed Content option.
    6. Click OK to change the settings.