VMware

VMware Workspace Portal 2.1.1 Release Notes

VMware Workspace™ Portal Appliance 2.1.1 | March 2015 | Build 2560245
VMware Workspace Portal for Windows 2.1.2 | March 2015 | Build 2540828
VMware Workspace Portal Integration Broker 2.1 | September 2014 | Build 2063882

Release date: March 12, 2015
Last updated: March 11, 2015

What's in the Release Notes

The release notes cover the following topics:

What's New Beginning with VMware Workspace Portal 2.1.1

This release of VMware Workspace Portal 2.1.1 delivers the following new features.

  • The ability to deploy Workspace in secondary data centers with active-active read-only capability. With Workspace 2.1.1, a secondary data center can be powered on and active with read-only access, which eliminates downtime during the fail-over. The read-only capability allows end users to view and launch their applications.
  • Each application or desktop pool in the View Pods or Citrix-based XenFarms is considered as a different resource in the Workspace catalog. To prevent duplication of resources in the Workspace catalog, a Do not sync duplicate applications feature has been added to View Pools and Published Apps configuration pages. When this check box is enabled, a resource only appears once in the catalog.

What's New Beginning with VMware Workspace Portal 2.1

This release of VMware Workspace Portal 2.1 delivers the following new features.

  • VMware Workspace Portal is delivered as a single Virtual Appliance (VA)
  • Users and resource analytics and system health dashboards are available from the Workspace Admin Console
  • Horizon DaaS desktops and applications are now integrated and appear in the Workspace Portal. Supported versions include DaaS 6.1.0, with patches 6.1.1 through 6.1.3.
    • Dynamic (floating VDI) desktop pools can be synced into and launched from Workspace.
    • Session-based (RDSH) app pools can be synced into and launched from Workspace.
    • Supported desktops and apps can only be launched via PCoIP using a locally installed Horizon Client.
  • End users can group apps in their Workspace Web app portal by
    • Marking apps as favorites
    • Filtering apps by category
  • End users can reset View desktops from their Workspace Web app portal
  • End users can use single-sign on (SSO) from their Workspace Web app portal to sign in to AirWatch Web Secure Content Locker and to enroll their devices (AirWatch MDM)
    • The AirWatch Secure Content Locker SAML app is pre-configured in the Workspace cloud application catalog
  • Workspace appliance performance improvements
    • Faster user entitlement calculations
    • Bulk upload users and groups more easily from Active Directory during initial Workspace configuration
  • Support for more flexible Active Directory configurations
    • Single AD domain
    • Multi-domain, single forest
    • Multi-forest with trust relationship
    • Multi-forest with no trust relationship

Internationalization

VMware Workspace Portal 2.1 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Simplified Chinese

Compatibility, Installation, and Upgrade

VMware vCenter™ and VMware ESXi™ Compatibility

VMware Workspace Portal 2.1 supports the following versions of vCenter and ESXi.

  • vCenter 5.0 U3, 5.1 U2, 5.5
  • ESXi 5.0 U3, 5.1 U2, 5.5

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.

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.

Upgrading to VMware Workspace Portal 2.1.1 from 2.1

Upgrading from Workspace 2.1 to Workspace 2.1.1 is the only supported upgrade path.

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

Documentation

To access the VMware Workspace Portal 2.1 documentation, go to the VMware Workspace Portal landing page.

Major Issues Resolved for 2.1.1

  • Office 365 Enhancements: Support AD account/password for active profile; users can enter their AD username and password to access Office 365. The "issuer_uri" attribute of Office 365 integration is globally unique. Office 365 integration now includes the ability to link to multiple domains.
  • The Forgot Password options in the Password Error Management page now includes the option to display a message to users with information about what to do when their password is forgotten.
  • Workspace 2.1.1 contains security fixes, including the fix to address SKIP attacks.

Known Issues

Known Issues from 2.1.1

  • Running the hznAdminTool command to manage the fail over order of View and Citrix-based resources in a multi-data center environment does not work. When you run this command, you get an error message.
  • Workaround. Before you can execute the hznAdminTool command, run the command

    export HZN_TOOL_OPTS="-Dehcache.replication.rmi.remoteObject.port=0"

    as root user from the Workspace appliance.

  • When distributed cache is configured for Workspace in a multi-data center environment, if the appliances are configured with the IP addresses within the same subnet, the multicast group address is the same in both data centers. Any cache set up as replicated in the Workspace cluster will be made available for discovery across all Workspace appliances in each data center. When data centers access different databases, this distributed cache configuraiton can cause potential issues in the Workspace data centers.
  • Workaround: Reconfigure the multicast group address to provide a unique address for each data center that accesses a different database. You must edit the runtime-config.properties files for each Workspace appliance in the data center to change the multicast group address.

    • Change the multicast group address value in
      datastore.ehcache.multicast.group.address
      to be different in each data center. The default address is 230.0.0.1.
    • If necessary, change the port that is used for discovery in
      datastore.ehcache.multicast.group.port
    • Change the port that is used for replication in
      datastore.ehcache.replication.tcp.port
      This can be either 40002 or 40003.

Known Issues from 2.1

  • When a Workspace appliance is cloned, the View and Citrix Published Apps configurations are not disabled.
  • 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.

  • When multi-forest Active Directory is connected to Workspace, membership of Domain Local groups that are from domains in a different forest might not be synched into Workspace.
  • 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.

  • Using non-Microsoft Windows Domain Name Service (DNS) when configuring Workspace Directory can cause the Workspace Directory sync to fail.
  • 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:

    example.com=examplehost.example.com:636, examplehost2.example.com:389

    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

  • The diagnostics information, including the date format in the System Diagnostics Dashboard in the Workspace Admin Console, is not localized.
  • Workaround. Use the English locale to view the System Diagnostics Dashboard in the Workspace Admin Console.

  • Sometimes URLs pointing to resources in applications integrated with Workspace fail to launch.
  • Workaround. Copy the URL link from the document and paste it directly into the browser's address field.

  • In a Workspace deployment, when the domain name changes on a domain join operation, Workspace stops functioning properly. An example is when the DNS name of the Workspace virtual appliance is example.domain.com but the domain it joins is domain.local
  • Workaround: Add the example.domain.com entry to the /etc/hosts of the Workspace appliance on the 127.0.0.1 line.

  • Workspace cannot resolve group memberships for domain local groups with members from another domain in the same forest.
  • Workaround. Create Universal groups for memberships that span across domains.

  • DNS host names that are too long cause syncing of ThinApp packages to fail.
  • Workaround. Make sure that the Workspace VA short host name is no longer than 15 characters.

  • UTF-8 encoded characters display for the domain name when logging in with non-ASCII user store.
  • Workaround. Do not use UTF8 characters when you create the domain name.

  • ThinApp package updates might not work even though you have 2 versions of a ThinApp package in your share. You might not see the latest version in Workspace.
  • 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.

  • Group names that contain special characters such as ampersand (&), cause sync failures.
  • Workaround: Do not create group names with special characters. Exclude the following special characters ! @ # $ % ^ & * ( ) + = | \ / ? " ' : ; ~ `

  • From the Workspace App Portal on Mac OS X, when connecting to a View Pool that implements Remote Desktop Protocol (RDP) via the Horizon Client, users must reenter their password to access their View desktop.
  • 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.

  • Non-ASCII characters in Base DN and Bind DN might be displayed as question marks in the Connector Admin Service pages after you migrate. After migrating from 1.8.x, the Base DN and Bind DN in the Connector Directory page display question marks for non-ASCII characters.
  • 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.

  • 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: Users must upgrade to a newer version of Internet Explorer.

  • Known issues in Workspace with Horizon DaaS:
    • Session-based apps are currently not available past Horizon DaaS version 6.1.3 or in Horizon Air 15.3.
    • App icons do not sync to Workspace. Workaround: Admins must upload and associate icons to each app.
    • Horizon Air resources do not work for users with non-ASCII names.
    • Some end user options are not yet implemented such as Reset and Reboot desktops.
    • Resource entitlements might not appear on an individual and instead appear on the group for which they are a member.
    • Session-based (RDSH) and Static (dedicated VDI) desktop pools are not supported at this time.
    • HTML5 Access is not supported. (HW-34839)