Horizon Cloud with On-Premises Infrastructure 1.3 Release Notes


Horizon Cloud with On-Premises Infrastructure | 20 APR 2017

Note: As of February 7, 2017, Horizon Cloud with On-Premises Infrastructure is made available as a deployment option with VMware Horizon® Cloud Service™.
You might see references to older names in the software user interface and documentation. These references will be updated in subsequent releases.
The product documentation that references previously released versions will continue to reflect the names they had at the times they were released.

Release notes last updated on: 14 SEP 2017

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

About Horizon Cloud with On-Premises Infrastructure

This section contains information about the Horizon Cloud with On-Premises Infrastructure deployment option of VMware Horizon Cloud Service.

For more information, see VMware Horizon Cloud Service Documentation.

Horizon Cloud with On-Premises Infrastructure is a hybrid cloud software service hosted by VMware that enables organizations to deliver VDI desktops and AppStack applications in those VDI desktops from on-premises infrastructure, while centrally managing it all from the cloud. Horizon Cloud with On-Premises Infrastructure allows you to leverage the best of both worlds: the economics and the simplicity of the cloud with the security and performance of on-premises infrastructure. Horizon Cloud with On-Premises Infrastructure consists of a cloud service, Horizon Cloud, which pairs with an on-premises component, Horizon Cloud Node.

Horizon Cloud – A control plane hosted in the cloud by VMware for central orchestration and management of virtual desktops and applications on on-premises infrastructure.
Horizon Cloud Node – Optimized hardware including VMware vSAN Ready Nodes and supported hyper-converged infrastructure that run on the organization’s premises, connected to the cloud control plane by way of integrated software.

Note: Horizon Cloud with On-Premises Infrastructure can be used to deliver VDI desktops and AppStack-based applications in those VDI desktops, using the VMware Just-in-Time Management Platform (JMP) technology. Horizon Cloud with On-Premises Infrastructure cannot be used to deliver Remote Desktop Services (RDS), RDS-based desktops, session desktops, remote (RDS-based) applications, or any other RDS-related capabilities.

What's New

The latest release adds the following enhancements:

  • Single consolidated virtual appliance for the Horizon Cloud Node.
  • Auxiliary domain bind account can be configured, used if the primary one is not operational.
  • New Enterprise Plus desktop model for desktop assignments, providing 8 CPUs and 16 GB memory.
  • Integration with cloud-hosted VMware Identity Manager™.
  • Ability to enforce end-user access through VMware Identity Manager.
  • Support for VMware Horizon smart policies.
  • Support for vSphere 6.5.

For detailed information about this release's features, see the Horizon Cloud with On-Premises Infrastructure 1.3 Documentation Center.

Before You Begin

Review this information as you prepare for adopting this version of Horizon Cloud with On-Premises Infrastructure:

Best Practices

Knowledge of the following facts is useful before using Horizon Cloud with On-Premises Infrastructure.

  • Compatibility with other VMware Products - For the most recent information about compatibility between Horizon Cloud with On-Premises Infrastructure and other VMware product, see the VMware Product Interoperability Matrices at https://www.vmware.com/resources/compatibility/sim/interop_matrix.php
  • Browser Experience – The Administration Console is compatible with recent versions of Google Chrome, Mozilla Firefox, Microsoft Internet Explorer, and Apple Safari. If you experience issues with the Safari, Edge, or Internet Explorer 11 browsers, use another browser, such as Firefox or Chrome, or another version of Internet Explorer and confirm if the issue persists.
  • Text Input – Follow these guidelines when entering characters.
    • Use only standard ASCII characters in path names, OVA file names, AppStack file names, user names and passwords, and for the password when downloading the DaaS SSL bootstrap file. If you use non-ASCII characters for these items, unexpected results might occur.
    • Do not use commas in user passwords.

Issues Resolved in This Release

  • The scroll feature does not work on the AppStacks screen until you refresh the page
    The AppStacks screen, which is accessible by selecting Settings > Storage Management, does not display a vertical scroll bar when you first access the page, preventing you from scrolling. This issue becomes apparent when the number of AppStacks extends beyond the bottom of the page. Using the browser scroll bar does not resolve the issue.

    This issue is resolved in this release.

  • Attempting to change the image name while creating an image in the Administration Console fails
    In the Administration Console, when you select Inventory > Images and click New to create a new image, edits to the auto-populated Image Name text box do not take effect.

    This issue is resolved in this release.

  • Attempts to create an assignment using special characters for the computer OU name might fail
    While creating an assignment, if you enter special characters in the Computer OU field and click Next, an error message appears with the following text. Unable to create assignment. The Computer OU entered in the Definition tab is invalid. Please enter a valid Computer OU and try again.

    This issue is resolved in this release.

  • After you push an image update to a desktop assignment, the assignment might display the wrong image version
    Updating an image and pushing the changes to an assignment updates the desktops based on the new image. Users who are logged into desktops at the time are skipped. After those users log out, the image version automatically updates. However, when you check the image version, for example by clicking Assign, clicking the assignment, and clicking Desktops, the image version on the Desktops page continues to display the old image version.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows:

Administration Issues

  • Installing the Horizon agent's scanner redirection feature in the master VM can result in unpredictable behavior in the virtual desktops.
    Due to a driver issue, when a master VM has the Horizon agent's scanner redirection feature installed, the virtual desktops that are cloned from that master VM experience unpredictable behavior.

    Workaround: Installing the Horizon agent's scanner redirection feature is not supported in this release. If you have installed the scanner redirection feature in your master VMs and the resulting desktops are experiencing unpredictable behavior, update your master VM to uninstall the scanner redirection feature.

  • AppStacks with names containing non-ASCII characters can fail to import successfully.

    Workaround: Rename the AppStack to include only ASCII characters.

  • If you do not delete the underlying writable volume using the Storage Management page after removing users or groups from a writable volume assignment, those users receive the writable volume when they next launch the associated desktops.

    Workaround: Use the Administration Console's Storage Management page to permanently delete the writable volume.

End User Issues

  • For a virtual desktop from a dedicated pool desktop assignment, after the user's first login to that desktop and then the user disconnects from that desktop, the user is not able to reconnect to that desktop by clicking the link on the Recent page in the Horizon Client.

    Workaround: This issue occurs only after the first login and disconnect of such a desktop. The user can reconnect to that desktop by selecting the desktop from the client's main list, or by closing and relaunching the Horizon Client and then using the Recent page. Subsequent launches of that desktop do not exhibit this problem.

  • Client drive redirection does not work with Horizon Agent installed on a 32-bit Windows 10 operating system.

    Workaround: None. This is a Microsoft Windows operating system issue.

  • When launching applications, a message "The specified path does not exist" might appear or the application might prompt you to enable the application as default or to set the default settings.
    This issue results when you use an AppStack application that requires customization or that makes use of user profile settings for customization. In previous releases, that AppStack application could be used with the UIA + Profile option for user writable volumes. However, that option is not available in this release. In this release, you use the User Environment Manager software to achieve application customizations.

    Workaround: To prevent the application from prompting the user to set the application as default, the administrator must use the User Environment Manager Application Profiler to customize the application settings and use the User Environment Manager Management Console's Personalization > Applications choice to apply the customization to the user. For a description of the role that User Environment Manager plays in your Horizon Cloud with On-Premises Infrastructure environment, see Creating Applications for Use in a Horizon Cloud with On-Premises Infrastructure Environment topic in the Administration guide and the document titled VMware App Volumes with Horizon Cloud Application Delivery Best Practices and Operations Procedures at vmware.com.

Previous Known Issues


This section lists known issues previously reported in the Release Notes for versions prior to version 1.3 that might continue to exist in the product.

Set Up and Configuration

  • After you create an image, install agents, and restart the virtual machine, a harmless error message appears
    As an administrator, after you install the App Volumes Unified Installer and restart the virtual machine as prompted, logging back in causes a connection error message to appear. The error message appears because the App Volumes Unified Installer cannot connect to the App Volumes Manager with which it is configured. The connection issue is caused by an access restriction of the local administrator user because the local administrator user is not joined to the domain and, therefore, not entitled to access the App Volumes Manager.
    Workaround: Ignore the error message. This issue does not block any functionality.

End User Issues

  • The Disconnect and Log Off option might fail to log off the desktop session
    If a session is established to a desktop or clone a significant period of time after the creation of the clone, selecting the Disconnect and Log Off option in the Horizon Client might fail to log off the desktop session. In such a case, the session goes into a disconnected state.
    Workaround: Perform one of the following procedures to log out of the desktop session.
    • Log off or sign out of the session by logging off of the Windows guest operating system.
    • In the Administration Console, select the disconnected clone or session and log out. This operation kills the session and the clone is resynchronized.
    • As a user, log in to the disconnected session using the Horizon client. Then select the Disconnect and Log Off option.
  • When you capture Microsoft Office suites in separate bundles and assign two or more together, a dialog box appears the first time users launch applications from the bundles
    Deploying multiple Microsoft Office bundles concurrently, initiates a permanent behavior where a harmless reconfiguration dialog box appears and soon disappears during the initial launch of an application from the bundles. After the dialog box disappears, users can access and use the application.
    Workaround: To prevent the dialog box from appearing, enable one bundle containing Microsoft Office applications at a time or in a bundle include all of the Microsoft Office suites.
  • When you attempt the initial log off of a dedicated desktop assignment from the Horizon Client menu, the logoff fails
    The first time you log on to a dedicated desktop assignment, attempts to log off of the desktop from the Horizon Client fail.
    Workaround: To work around the issue, for the initial log on, use the Windows Menu item to log off, not the log-off buttons in the Horizon Client. After implementing the workaround, future log-off attempts succeed, regardless of if you use the Horizon Client or the Windows log-off button.
  • After logging into a desktop using the Horizon Client, locking the desktop does not disable single sign-on
    The following functionality exists in Horizon 7, but not in Horizon Air Hybrid-Mode. When you lock a remote Windows desktop session, the Horizon Client does not allow you to reconnect to that desktop, or any other desktop to which you are entitled, unless you reauthenticate. Therefore, implement the workaround that follows to ensure that single sign-on is disabled in Horizon Air Hybrid-Mode.
    Workaround: Inform users of the following best practice. Close the Horizon Client or disconnect from Horizon Air Hybrid-Mode when you leave the client desktop or mobile device unlocked.

Administration Issues

  • When you publish an image, clones do not reflect the selected time zone
    Setting the time zone as you publish an image has no effect. The time zone of the client is configured in the clone and might not match the time zone selected when you publish the image.
    Workaround: Change the master time zone to the desired setting.
  • When you rename an image, an error message appears
    When you select Inventory > Images, rename an image, and click Save, the following error message appears.
    Unable to update name due to internal server error. Please try again.
    Regardless of the error message, the operation might succeed. In such a case, the image is renamed. If the operation fails, the image is not renamed.
    Workaround: Manually inspect the image to determine if it is renamed. If the renaming operation fails, most likely the name is already in use. Therefore, verify that you have a unique name for the image and attempt to rename the image again. For your information, the renaming operation completes in a few seconds.