VMware Horizon Cloud Service | 26 JAN 2017

As of February 7, 2017, the new brand name for VMware Horizon Air is Horizon Cloud with Hosted Infrastructure. In the current releases, customers will continue to find legacy references to previous names in the product documentation.

Release notes last updated on 14 NOV 2017

Check for additions and updates to these release notes.

Links to release notes for other versions (* indicates DaaS Agent): 15.3.2 | 15.3.3 | 16.6 | 16.6.1 | 16.6.2* | 16.11 | 16.11.2* | 17.1 | 17.1.1 | 17.2

What's in the Release Notes

The release notes cover the following topics:

New Features

Optional Filtering of Images Shown in the Administration Console

There is a new filtering feature that causes only images matching the disk size of the standard capacity assigned to the selected pod to be listed in the Horizon Cloud Service Administration Console.

  • This filter is applied whenever you are in an area of the interface listing available images (for example, when editing an assignment).

  • This is disabled by default, and can be enabled by your VMware representative if you request it.

Updates to the Helpdesk Console (Beta Feature)

The following updates have been made to the Helpdesk Console:

  • Microsoft Internet Explorer 10 and 11 are now supported for console access.

  • The Virtual Machines tab now shows logged-on sessions and VM operations for each VM.

  • The Remote Assistance tab now shows all sessions (only active desktop sessions are eligible for remote assistance). There is also a new session log-off capability.

  • Console access through the Access Point is now supported in vCenter-based deployments.

Other Changes in This Release

The following changes in functionality are also included in the 16.11.1 release.

  • When you create an applications assignment, you can now add individual users to it, in addition to user groups.

  • On desktop VMs, C:\ drives will no longer be flexible in size. For larger drives, you will need to use larger desktop models.

  • For utility VMs, only E:\ drives are supported, and in the following fixed sizes: 1, 2, 4, 8, 12 TB.

Best Practices

Instant Clone Images - Supported Operating Systems

Windows Server operating systems are not supported for Instant Clone assignments, so you should not create Instant Clone images from Windows Server template VMs. Although the image can be created with the Instant Clone Agent installed and desktops can be provisioned from it, the desktops will not launch successfully for users.

Assignment Capacity Less Than Expected

If you see that the capacity displayed for an assignment is less than you requested or is less than it was previously, recover the assignment by performing the following steps:

  1. On the Assignments page, select the affected assignment.

  2. Click the Recover button.

Active Directory - Distribution Groups Not Supported

When you are defining groups of users or administrators, always select 'Security' for the Active Directory group type, as Distribution groups are not supported.

Product Support Notices

DaaS Agent 16.11.1 Required

DaaS Agent 16.11.1 is required for all Horizon Cloud Service 16.11.1 installations.

Fixed Issues

  • When you had multiple domains registered, the Organizational Unit (OU) that you entered in the Image Defaults Configuration under General Settings was not applied to assignments for the domain as would be expected. This has now been remedied so that the setting is applied as expected.

  • Some customers have been experiencing domain registration failures. The 16.11.1 patch includes a new validation check to ensure that the domain controller is reachable and domain registration is successful before committing the change to the system's database. If the validation fails for any reason, the system produces an error, but the error does not provide any information. If this occurs, check the AD configuration, ensure the AD is reachable and that the bind credentials are correct, and retry.

  • When App Volumes is enabled, some users have experienced delays when editing and saving changes to application assignments. This has been remedied so that changes are saved in a timely manner.

Known Issues

  • Reducing the capacity of an assignment from 1000 to 0 on the assignments page results in a message indicating an internal error. Although there is an error in the system, it does not interfere with the reduction task, which is performed successfully in the background. If you see this error message, click the OK button in the error dialog and the system will display the edit setting page.

  • In rare cases, the agent state of a VM is reported as unknown after users log off of the desktop. The workaround for this is to perform a reboot on the desktop, which brings the agent back to an active state.

  • If you create a desktops assignment using an Instant Clone image and have Windows 7 or Windows 10 desktops in it, you may not see the correct number of vCPUs on the desktops. If this occurs, it is because a maximum of 2 vCPUs are supported for those operating systems. The workaround is to use a desktop model with 1-2 vCPUs. If you do not have an appropriately configured desktop model, you can request that your VMware representative make the necessary changes.

  • When Traditional Clone desktops running View Agent 7.0.2 with the Instant Clone component enabled – running a View Agent upgrade to View 7.0.3 can result in the desktops failing to launch. To workaround this problem, do one of the following:

    • Uninstall View 7.0.3, reboot, and reinstall View 7.0.3 from scratch (ensuring that View Composer is not selected for install).

    • Perform the following steps on the desktop:

      1. Add the following registry key:

        HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Node Manager\Use SVI DWORD

      2. Set the new key to 0.

      3. Reboot the desktop.


check-circle-line exclamation-circle-line close-line
Scroll to top icon