VMware® Workspace™ Portal 2.0 Release Notes
Formerly "VMware Horizon Workspace"
VMware Workspace Portal Server 2.0 | June 2014 | Build 1885638
Workspace for Windows 2.0 | June 2014 | Build 1887286
VMware Workspace Integration Broker 2.0 | June 2014 | Build 1788871
Last updated: June 11, 2014
What's in the Release Notes
The release notes cover the following topics:
What's New Beginning with VMware Workspace Portal 2.0
This release of VMware Workspace Portal 2.0 delivers the following new features.
- Support for VMware Horizon 6 with View Hosted Applications
To launch View Hosted apps in Horizon 6, Horizon Client version 3.0 or later must be installed.
- Workspace is simplified to provide exclusively identity and app management features
- Horizon Files feature is removed
- Horizon Switch device management is removed
- Support for multiple View pod instances from the same Active Directory
- ThinApp 5.0 64-bit support is now native in the Windows Agent (works out of the box)
- ThinApp 5.0.1 support
- Improved audit log reporting using Elasticsearch
- Enhanced reporting of users' activity and application utilization
- More extensive custom branding controls
- Improved entitlement and directory sync performance
- Support for multiple DNS servers in Workspace vApp
- Updated to the OPENSSL library version openssl-1.0.1h where necessary to address CVE-2014-0224, CVE-2014-0198, CVE-2010-5298, and CVE-2014-3470
VMware Workspace Portal 2.0 is available in the following languages:
- Simplified Chinese
Compatibility, Installation, and Upgrade
VMware® vCenter™ and VMware ESXi™ Compatibility
VMware Workspace Portal 2.0 supports the following versions of vCenter and ESXi:
- vCenter 5.0 U2, 5.1, 5.1 U1, 5.5, and 5.5 U1
- ESXi 5.0 U2, 5.1, 5.1 U1, 5.5, and 5.5 U1
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:
- Mozilla Firefox 28 or later for Windows and Mac systems (latest)
- Google Chrome 34.0 or later for Windows and Mac systems
- Internet Explorer 10 and 11 for Windows systems
- Safari 6.1.3 or later for Mac systems
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™.
Upgrading to VMware Workspace Portal 2.0 from Horizon Workspace
Upgrading from Horizon Workspace 1.8.2 to Workspace 2.0 is the only supported upgrade path. You must
upgrade to Horizon Workspace 1.8.2 before you start the 2.0 upgrade.
Export Horizon Workspace Data-va Files before You Upgrade
VMware Workspace Portal 2.0 no longer utilizes Horizon Files. For customers who would like to continue utilizing an Enterprise File Sync & Share solution after upgrading, the existing files from the data-va can be exported and imported into any EFSS system. See VMware KB article 2080325
Procedure for Upgrading to VMware Workspace Portal 2.0
During the upgrade, you run the upgrade command from the command line on the configurator-va virtual machine. During the upgrade, all Workspace services are stopped, so plan the upgrade with the expected downtime in mind.
Before you start an upgrade, verify that all virtual machines are powered on and the system is functioning.
- Go to the configurator-va virtual machine and log in as the root user to check for Workspace upgrades
- Run the updatemgr.hzn command to check for the available upgrades online
- Run the updatemgr.hzn command.
Messages that occur during the upgrade are saved to the update.log file at
- Restart the vApp from vCenter.
See the VMware Workspace Portal Upgrade Guide for additional information about preparing to upgrade and configuring Workspace after an upgrade.
Procedure to Upgrade without an Internet Connection
Prepare Workspace as described in Prepare a Local Web Server. Note that the zip file names have changed from the example. If you use a proxy server to connect to the Internet, see Configure the Proxy Server Settings upgrade topic.
- Run the updatelocal.hzn command on the configurator-va virtual machine to configure an upgrade repository to use a local Web server.
/usr/local/horizon/lib/menu/updatelocal.hzn seturl -update20 http://yourwebserver/repopath
NOTE: To reset back to the default online URL run the following command:
To access the full set of VMware Workspace Portal 2.0 documentation, go to
the VMware Workspace Portal landing page.
The Workspace issues added in the most recent release are marked with the * symbol. Other known issues have been carried
forward from previous releases.
- * Upgrade of a vApp with multiple service-vas causes Elasticsearch configuration to be lost.
Workaround: Enable multicase on each clustered service-va. Log in to each service-va as root and run
hznAdminTool configureElasticSearch -ES_MULTICAST_ENABLED true
- *Non-ASCII characters in Base DN and Bind DN might be displayed as question marks in Connector after upgrade. After upgrading from 1.8.x, the Base DN and Bind DN in the Connector Directory page display question marks for non-ASCII characters.
Workaround: After upgrading from 1.8.X, manually change all question marks to the correct characters (Directory and View Pool pages).
- *Internet Explorer 11 does not work with locale zh-Hans or zh-Hant.
Workaround: In Internet Explorer, users should use zh_CN instead of zh-Hans and zh-Hans-CN, use zh_TW instead of zh-Hant and zh-Hant-CN, and use zh_HK instead of zh-Hant-HK to access their user portal.
- * ThinApp package names that contain non-ASCII characters cannot be downloaded using HTTP Download.
Workaround: To allow ThinApp package names that have non-ASCII characters:
- Log in to the connector-va as root.
- In the /etc/init.d/tcserver-c2 file, add the line
export LC_TYPE=en_US.UTF-8" .
- Restart tcserver-c2. Type /etc/init.d/tcserver-c2 restart
- Repeast steps 1 and 2 on all connector-va servers in your deployment.
This message is incorrect. Users can use their Citrix apps from their mobile devices.
- * Documentation Issue. The Office 365 documentation in the VMware Workspace Portal Administrator's Guide incorrectly states as a prerequisite that you must run the Microsoft Powershell Convert-MsolDomanToFederated cmdlet which is not needed.
Instead, follow the procedure to run the Set-MsolDomainAuthentication cmdlet.
Citrix-based applications cannot be launched in Internet Explorer 8.
Workspace does not support using Internet Explorer 8 to launch a Citrix-based application.
Workaround: Tell users to upgrade to a newer version of Internet Explorer.