VMware Workspace Portal 2.1 Release Notes
What's in the Release NotesThe release notes cover the following topics:
This release of VMware Workspace Portal 2.1 delivers the following new features.
VMware Workspace Portal 2.1 is available in the following languages:
VMware vCenter™ and VMware ESXi™ Compatibility
VMware Workspace Portal 2.1 supports the following versions of vCenter and ESXi.
Browser Compatibility for the Workspace Admin Console and other interfaces
The following Web browsers can be used to view the Configurator Web interface, Connector Web interface, and Workspace admin console:
For other system requirements, see Installing and Configuring VMware Workspace Portal on the VMware Workspace Portal landing page.
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 View.
Migrating to VMware Workspace Portal 2.1
You can migrate from Horizon Workspace 1.8.1, 1.8.2 and from Workspace 2.0 to Workspace 2.1.
Export Horizon Workspace Data-va Files before You Migrate
Beginning with VMware Workspace Portal 2.0, Horizon Files is no longer included. For customers who would like to continue utilizing an Enterprise File Sync & Share solution after migrating, the existing files from the data-va can be exported and imported into any EFSS system. See VMware KB article 2080325. .
To access the VMware Workspace Portal 2.1 documentation, go to the VMware Workspace Portal landing page.
Workaround. Log on to the cloned virtual machine's Connector Services Admin page and disable the resource from the appropriate page, either View Pools or Published Apps - Citrix.
Workaround: The Bind DN user used on the Workspace Directory page must be added to the Administrators group of the domain in which Domain Local group resides.
Workaround: When setting up a non Windows DNS, you can create a file domain_krb.properties in this path "/usr/local/horizon/conf/domain_krb.properties" and provide a list of the domain-to-host values. You create the list as AD Domain=Host:port. For example:
Change the ownership of the file.
chown horizon:www /user/local/horizon/conf/domain_krb.properties
In the krb5.conf file, update the realms section to include the KDC information at the end. For example, add as
kdc = examplehost.example.com, examplehost2.example.com
Workaround. Use the English locale to view the System Diagnostics Dashboard in the Workspace Admin Console.
Workaround. Copy the URL link from the document and paste it directly into the browser's address field.
Workaround: Add the example.domain.com entry to the /etc/hosts of the Workspace appliance on the 127.0.0.1 line.
Workaround. Create Universal groups for memberships that span across domains.
Workaround. Make sure that the Workspace VA short host name is no longer than 15 characters.
Workaround. Do not use UTF8 characters when you create the domain name.
Workaround: Name the folder that contains the later version of the ThinApp package such that it comes later than the earlier version of the ThinApp package. For example, if version 1 of a Thinapp package is inside a folder named ThinAppExample, name version 2 of the ThinApp package folder as ThinAppExample02.
Workaround: Do not create group names with special characters. Exclude the following special characters ! @ # $ % ^ & * ( ) + = | \ / ? " ' : ; ~ `
Workaround. For the first usage of the View desktop, users should connect to their View desktop from the Mac using the Remote Desktop Connection application bundled with Mac OS X. The password is then stored as a keychain login item on the Mac. The next time, they can launch their View desktop from their Workspace Apps Portal and they are not asked to authenticate again on the Mac.
Workaround: After migrating from 1.8.X, manually change all question marks to the correct characters. Search for this in the Directory and View Pool pages.
Workspace does not support using Internet Explorer 8 to launch a Citrix-based application.
Workaround: Users must upgrade to a newer version of Internet Explorer.