Horizon Cloud with Hosted Infrastructure 18.1 | 31 JAN 2018 

See Revision History below for additions and updates to these release notes.

Links to release notes for other versions: 16.6 (SP) | 16.6.1 (SP) | 16.11 (SP) | 16.11.1 (SP) | 17.1 (SP) | 17.1.1 (SP) | 17.2 (SP)

What's in the Release Notes

The release notes cover the following topics:

Product Documentation

  • To access the Service Provider documentation for this release, see the Horizon Cloud Hosted Service Provider documentation landing page. 

  • To access the user-facing product documentation for all deployment models of Horizon Cloud, see the VMware Horizon Cloud Service documentation landing page.

Compatibility Information

For the most recent information about compatibility between this product and other VMware products, see the VMware Product Interoperability Matrices.

Upgrade and New Installation Processes

  • Upgrade to version 18.1 is performed using automated processes in Rundeck. For more information, see the Griswold to Hagrid upgrade runbook Confluence page.

  • New installation of version 18.1 is performed using Jenkins jobs that replace the old manual procedure. For more information, see the DaaS Onboarding Runbook Confluence page.

New Features

Service Provider Features

There are no new Service Provider features in this release.

Tenant Administration Features


GPU support is now available in Horizon Cloud to support use cases requiring high graphics power for virtual desktops. This functionality is available for datacenters in the US, UK, Japan, and Germany.

You must obtain NVIDIA licenses directly from NVIDIA distribution partners (see NVIDIA Virtual GPU Packaging, Pricing and Licensing) and set up the License Server based on instructions from NVIDIA (see Virtual GPU License Server User Guide).

The table below shows all available configurations, including the new GPU options.

Capacity NVIDIA Card vCPU per unit vRAM per unit Storage per unit Video Memory per unit Configurations
Standard Capacity   1 2 GB 30 GB  
  • Value (1 unit)
  • Professional (2 units)
  • Premium (4 units)
  • Performance (8 units)
  • Hosted App Server (8 units)
Workstation Capacity (M10) M10 2 4 GB 30 GB 1 GB
  • Professional (1 unit)
  • Premium (2 units)
Workstation Capacity (M60) M60 4 16 GB 120 GB 2 GB
  • Professional (1 unit)
  • Premium (2 units)
  • Performance (4 units)

Single Installer for All Agents

The new Horizon Agents Installer contains the required agent software for the corresponding version of Horizon Cloud.

  • Horizon Agents Installer 18.1 is the version for Horizon Cloud with Hosted Infrastructure 18.1.
  • Any updates to Horizon Agents Installer can be applied to assignments or images in the administration console using the existing Update Agent Software feature.
  • When building your own template VM for images, you can download and run the Horizon Agents Installer instead of installing separate agents as was required previously.

Auxiliary Domain Join Account

You can now add an auxiliary domain join account to your Active Directory.

  • You can add this account either during domain registration or at a later time.
  • You can edit or delete the auxiliary account after adding it.
  • You can add only one auxiliary domain join account for each Active Directory. 

This feature is described in the Settings section of the Administration guide.

Traditional Image Duplication

You are now able to duplicate Traditional (non-Instant Clone) clone images on the Image page in the Horizon Cloud administration console.

This feature is described in the Images section of the Administration guide.

Task Cancellation

You are now able to cancel assignment-related tasks before they complete.

  • There is a new Cancel button on the Admins tab of the Activity page and on the System Activity tab of the assignment detail page.
  • If a task is currently able to be cancelled, you will be able to select the corresponding check box in the task list. If you select the 'select all' check box at the top of the list, all tasks that can currently be cancelled are selected.
  • Assignment expansion tasks are sometimes (not always) able to be cancelled when they have a status of Queued. They are never able to be cancelled when they have a status of Running. 
  • Assignment refresh (Push Updates) tasks are sometimes (not always) able to be cancelled when they have a status of Queued or Running.

Note: When the system has created an expansion task for a session desktop assignment automatically, the farm must be offline before you can cancel the task.

This feature is described in the Monitoring and Assignments sections of the Administration guide.

User Notifications

You can now have notifications sent to users regarding system issues such as AD connectivity and authentication failure. There is a new option under General Settings in the Administration Console that allows you enter email addresses for users you wish to notify.

Note: Site24x7 integration must be completed for this feature to be functional.

Desktop Health Alert

On the Desktop Health report (Monitoring > Reports > Desktop Health), a Desktop Health alert now displays when one or more of the following parameters is outside of normal range: CPU usage %, memory usage %, and disk IOPS. The alert indicates which parameter(s) are out of range and what the current value(s) are.

Reset Agent Pairing Option

If agent pairing was performed successfully but later fails, you can reset the pairing using a new option on the following pages of the Administration Console:

  • Assignments - Assignment detail pages.

  • Farms - Server tab of farm detail pages.

  • Images - Main Images page and image detail pages.

  • Imported VMs

  • Utility VMs

For more information see the relevant sections of the Administration guide.

Top of Page

Other Changes in this Release

Desktop Portal Disabled by Default

Beginning in this release, the Desktop Portal will be disabled by default. If you want to enable it on your environment, you can request a hotfix from VMware that allows you to do this. If appliances were later upgraded or restored, the hotfix would need to be re-applied.

Best Practices

Knowledge of the following facts is useful before using Horizon Cloud.

[Service Provider] Workaround for Image Publish Failure With "Incorrect Session Ticket" Error

In multi-DM environments with Sync Gold Patterns enabled, when a user attempts to publish an image, the sync operation can fail with a "Incorrect Session Ticket" error thrown in RM logs. This is happening because the default timeout for session ticket is 60 seconds and in this case it not sufficient.

The workaround for this is to increase the default timeout to 120 seconds or more:

  1. Go to Administration > Vcenter Server Settings > Advanced Settings.
  2. Add the following two config parameters:
    Key Value Description
    vpxd.sessionTicket.expired 120

    Increases the ticket expiration period.

    vpxd.sessionTicket.timeoutSecs 120

    Increases the time for clearing the ticket cache.

[Service Provider] Specifying Datastores for Instant Clone Images

For Instant Clone images, if you do not specify any datastores for desktop storage, VMs may be placed on any connected writable datastore, which may not be the same datastore as the template VM. This can also cause performance issues for users.

Compatibility with other VMware Products

For the most recent information about compatibility between this product and other VMware products, see the VMware Product Interoperability Matrices.

Browser Experience

The Administration Console is compatible with recent versions of Google Chrome, Mozilla Firefox, Microsoft Internet Explorer, and Microsoft Edge. Even though you can try using Apple Safari, use of the Administration Console in Apple Safari is not supported in this release.

Infrastructure Requirements for Features

Some features have particular infrastructure requirements, as shown below.

Feature Requirements

Automated Upgrade


  • Hydra account required.

  • Sufficient capacity must be available for appliances.

  • Sufficient IPs must be available for appliances.

  • A configuration with multiple virtual data centers per vCenter is not supported and will cause the upgrade to fail.

  • Do not enable DHCP on the SP network. If DHCP is enabled, it can cause serious issues in your environment.

For additional information on Hydra account, capacity, and IP requirements, see the Ops Team Readiness to use Automation Confluence page.

Automated New Install


  • Hydra account required.

  • Sufficient capacity must be available for appliances.

  • Sufficient IPs must be available for appliances.

For details, see the Ops Team Readiness to use Automation Confluence page.

Cloud Monitoring Service


  • SP appliance must have internet access on port 443. 

    If an SP appliance cannot access internet directly, you can configure a proxy on the SP to access CMS services (in AWS). The proxy config is in the cloud_config table in the SP FDB.

  • Tenant appliances should also be able to access internet on port 443.

  • SP appliance need to be on-boarded.

For details, see the CMS Onboarding Confluence page. 

True SSO


  • An enrollment server must be installed on the customer’s network. (Ops do not have to install this; similar to AD server.)

  • A certificate authority server must be installed on the customer’s network. (Ops do not have to install this; similar to AD server.)

  • VPN access must be enabled from the datacenter to the Enrollment Server..

  • Port 32111 must be opened on the Enrollment Server for tenant appliance communication.

For details, see the "Configure True SSO for an Active Directory Domain" topic and related sub-topics in the user-facing Administration guide.


Known Limitations

Updating Images Using Console Access

Performing updates to images (such as updating agents) using console access without taking the image offline and then accessing it via the Helpdesk Console (beta feature) is not supported and can cause issues with the image and subsequent pools spun up using this image. Do not attempt to perform image updates this way. Always duplicate the image from the Admin Console and then update it using the HACA Console.

Resolved Issues

The following issues have been resolved in version 18.1.

Service Provider Issues

  • Tenant appliances were sometimes showing high swap usage and load average, resulting in symptoms like slow loading of UI pages. This has been fixed so the symptoms no longer occur. [1967087]

Tenant Administration Issues

  • During a farm's rolling maintenance, reduced availability for end user RDS session desktops and remote applications sometimes occurred. If there were no end user sessions on all of the farm's servers just before the maintenance window, all servers were shut down at the same time for maintenance. Then, if high demand occurred for user sessions to the RDS desktops and remote applications that were served by that farm right after the maintenance process began, the farm was not be able to accept even a single user session for a span of three to five minutes.   [1943984]

  • If you clicked the name of a farm on the Farms page and then clicked the Servers tab when power operations were ongoing for multiple servers on the farm, the tab was occasionally blank. This has been fixed so the page no displays as blank.  [1974580]

  • The formatting in the CSV files exported from the Desktop Health, Concurrency, and Session History reports did not precisely match the ones you saw displayed on the screen. For example, the column headings could be different, the CSV files had more columns of data than in the on-screen tables, and the Session History CSV file gave the last login time as the UNIX time in milliseconds. This has been remedied in the current version.  [1895363]

  • When the end user clicked the Reset menu action on their browser-based RDS desktop session, the Logoff action was temporarily disabled for up to 5 minutes. To reset a desktop meant to reboot the desktop's underlying VM. For RDS desktops where there were multiple users with sessions using the same server, the system appropriately prevented a single user from performing the reset action. However, due to a known issue, when the end user clicked the Logoff action after clicking Reset, a message said the desktop could be logged off. This issue has been fixed so that the logoff action works as expected.  [1974704]

  • When you clicked Test Pairing during the True SSO setup process, the system sometimes reported that the pairing failed even though it did not.This issue has been remedied so that this symptom no longer occurs.  [1973565]

  • When using the Administration Console in Microsoft Internet Explorer 11, you saw placeholders instead of the actual text strings. This issue was due to static content being cached in the browser. This has been fixed in this release so that the text appears as expected.  [1977016]

Known Issues

Service Provider Issues

  • In Horizon Cloud 18.1, after you upgrade VMware Identity Manager Connector from version 2017.8.1.0 to version 2017.12.1.0, the sync operation may fail. 

    Workaround: Save the virtual app collection again by re-entering the Admin password for the tenant and then perform sync.   [2041300]

  • When adding a vCenter host manager during the Service Provider install process, a list of all clusters managed by the vCenter server will be displayed. One or more clusters can be selected, but after this the user will only be prompted for setting the type and overallocation ratios of one cluster.

    Workaround: Edit the compute resources that were skipped over during the install process by using the Service Grid interface; this will allow configuration of the cluster type and overallocation ratios.  [1884191]

  • In the rare case where (1) the tenant has stand-alone DM pairs in addition to the main tenant appliances and (2) the DM pair of appliances is down or unreachable, an attempt to restore one of the primary TA appliances fails at the slonychk step.

    Workaround: Ensure all appliances in the tenant organization are running and reachable prior to performing the restore.  [1890917]

  • If you restore a primary tenant appliance running Horizon Cloud 17.1, desktop launches may fail after the restore is complete because JMS has not initialized properly.

    Workaround: Restart the JMS service by running service daasJms restart. If the restart fails silently, you will need to check the status by running service daasJms status and restarting the service again if the status is not active and running. [1894607]

  • In multi-DM environments with App Volumes enabled, when you upgrade or restore a desktop manager appliance that has compute resource(s) assigned to it, AppStacks can fail to mount at desktop launch.

    Workaround: Reinstall the NGINX conf files. For an upgrade, copy the files from the BLUE desktop manager appliance located in /etc/nginx/conf.d/ and /etc/nginx/upstream/ and place them in the GREEN desktop manager appliances. For a restore, copy the files from the other desktop manager appliance. [2046651]

Tenant Administration Issues

The known issues are grouped as follows:

Active Directory - Known Issues

  • If you add the same group to the Super-Administrator role and the Demo-Administrator role, users in that group will not have full access to all expected functions.

    Workaround: Do not add the same group to the Super-Administrator role and the Demo-Administrator role.  [1963653]

  • It takes up to 15 minutes for the Administration Console to reflect a lockout or unlocked state of the primary bind domain account.

    The system's connection object to Active Directory is cached for 15 minutes. As a result, it might take 15 minutes from the time point when the primary bind account goes to locked state and the system raises the notification to the administrator. Conversely, after the administrator clears the locked-out condition of the account, it might take up to 15 minutes for the system to stop notifying about the now-cleared account.

    Workaround: None.  [2009434]

  • Reusing the same farm name with a different domain in the same Active Directory forest can lead to domain join failures due to duplicate service provider names (SPNs). Due to a new feature for domain controllers in Microsoft Windows Server 2012 R2 and higher, a duplicfate SPN check on the domain controller causes domain join failures. See the Microsoft KB article 3070083.


    • Avoid reusing farm names.
    • As described in that Microsoft KB article, disable duplicate SPN checks in the Active Directory domain.


  • If a logged-in user running commands as an administrator (using runas) attempts to update environment variables, the system's environment variables become corrupted.

    Workaround: The user can be added to the administrators group, allowing them to perform the modification of environment variables without running commands as an administrator. [1974388]

Images, Farms, Assignments - Known Issues

  • Image creation in the Getting Started wizard is not functional.

    Workaround: Create the image on the Images page of Administration Console. [2040608]

  • If you change the name of a farm or VDI desktop assignment, it takes an hour for the Desktop Health report's Assignment drop-down menu and Assignment column to reflect the new name.

    Workaround: Wait an hour before expecting the new name to appear in the report. [1756889]

  • When you push updates for a traditional clone assignment, a small number of VMs may enter a PXE boot error state. For example:

    • PXE-E53 : No boot filename received
    • PXE-MOF: Operating System not Found.

    Workaround: This is a NetApp issue, so there is no workaround in Horizon Cloud.  [1969642]

  • When attempting to create a new assignment or expand an existing assignment, you may see an error indicating that there is not enough capacity to complete the operation, even though you have confirmed that there is sufficient capacity. This occurs because the system sometimes fails to detect additional capacity being consumed by Instant Clone functionality.

    Workaround: Contact your VMware representative to remedy this issue.  [1956345]

    Note to service providers: You can remedy this issue by increasing the over-allocation ratio.

  • When you uninstall AppCapture from the Control Panel in a non-English environment, the text in the 'Delete program data?' screen of the uninstall wizard will appear in English.

    Workaround: None.  [1965376]

  • When a user is entitled to a dedicated desktop assignment, that assignment appears under Assignments in the user detail information shown when you click on the user's name in the Administration console. However, after the user launches a desktop from the assignment, it no longer appears in the user detail information.

    Workaround: None.  [1958046]

  • Shrinking an Instant Clone assignment can sometimes fail to delete one of the VMs, which then goes to a powered off state.

    Workaround: Power on the VM. When it is powered on and visible in the assignment, shrink the assignment again. [2027097]

  • You cannot edit the number of sessions per RDSH server once a farm is created.

    Workaround: None.  [1932001]

  • The Administration Console reports a farm's servers' DaaS agents are active and their VMs are in success state several minutes before the VMs are actually ready to use for assigning RDS session desktops and applications using that farm. Due to this known issue, after you create a farm and the Administration Console indicates the farm's servers are ready for you to start assigning RDS session desktops or remote applications using that farm, when you navigate to Assignments screens, you see on-screen messages about needing RDSH servers or farms out of capacity. These symptoms result from the Administration Console reporting the farm's servers are ready several minutes before the connection broker to the Horizon agent on the server VMs is completely ready.

    Workaround: To avoid this issue, delay creating assignments using a farm for at least 15 minutes after the user interface indicates the farm is ready. [1941076]

  • In a URL redirection customization, URL patterns with uppercase letters do not result in redirecting the URLs for the end users.

    Due to this issue, when you use uppercase letters, or mixed-case letters, in a URL pattern, even though the system saves the information, redirection for the end users does not actually occur. For example, URL redirection does not occur for URL patterns specified as *GOOGLE.com and *Google.com, even though the pattern *google.com is redirected.

    Workaround: Use all lowercase letters when specifying URL patterns. [2029396]

  • If you attempt to create a farm using a Windows Server 2016 image, the VMs may hang at the customization stage.

    Workaround: Disable the tiledatamodelsvc service on the Windows Server 2016 image and then create the farm.   [2010914]

Reports - Known Issues

  • On the Desktop Health tab of the Reports page, the Bandwidth and Latency metrics for VDI desktops are incorrectly showing a value of 0.

    Workaround: None.  [1966410]

  • When CPU usage on a desktop is very high--for example, when an application is using 100%--the Desktop Health alert notification does not display on the Desktop Health tab of the Reports page.

    Workaround: None.  [2015486]

  • When IPv6 is enabled on an image, the abnormal IP notification may not display on the Desktop Health tab of the Reports page.

    Workaround: Disable IPv6 for the image.  [2017500]

User Interface - Known Issues

  • The memory usage percentages reported for desktop health reports and used for the desktop health alerts are based on percentage of committed memory, which equals physical memory plus pagefile size, and not on percentage of only physical memory.

    Committed memory for a desktop VM is calculated as physical memory plus pagefile size. When calculating the percentage of memory usage in a desktop, the system takes the percentage used of that total (physical memory plus pagefile size). Both the desktop health alerts and the memory usage report in the destop health reports use that percentage calculation. However, when you log into a desktop VM and open the Windows Task Manager to view the memory usage in the desktop's Windows operating system, the Windows Task Manager displays percentage based on physical memory only. As a result, the memory usage percentage that the desktop's Windows Task Manager displays does not match the memory usage percentage displayed in the Desktop Health reports or in the desktop health alert.

    Workaround: Keep in mind this difference if you decide to make a comparison between the memory usage percentage reported by a desktop's Windows Task Manager and the memory usage percentage reported in the Administration Console's Desktop Health report and desktop health alerts for that desktop. [2015772]

  • In workflows that result in the system creating VMs, such as creating farms, images, and assignments, if you have entered a name that is longer than 12 characters, the name in the system is truncated. As a result, unexpected results might occur from the truncated name.

    Workaround: Limit entered names to 12 characters or less. [1966118]

  • Some pages in the Administration Console do not display correctly in the Safari browser.

    Workaround: Use a different browser to access the Administration Console. [1956356]

App Volumes - Known Issues

  • AppStacks with names containing multi-byte characters do not import correctly.

    Workaround: Do not use multi-byte characters in the names of your AppStacks.  [1968208]

  • After the App Volumes agent is installed on an image VM, the App Volumes agent is not able to communicate with the App Volumes Manager until the DaaS agent pairing process is completed. The following error message is displayed: "Connection Error, Unable to contact App Volumes Manager. Virtualization is disabled".


    1. Prior to installing App Volumes agent, ensure that the DaaS agent pairing process is completed.
    2. If DaaS Agent pairing occurs after the App Volumes agent is installed, ignore the connection error and click OK. If the DaaS agent is paired later, the connection is set up automatically.


  • You may see the following error message at login on the machine where the Tectia Client application is installed with the App Volumes agent: "Failed to initialize conversion library" along with a list of dlls.

    Workaround: Click OK to dismiss the message and continue to use the application.  [1984350]

Localization - Known Issues

  • When non-ASCII or high-ASCII characters are used in the True SSO template name, retrieving the template fails and True SSO cannot be configured successfully.

    Workaround: Use only ASCII characters in the names of your True SSO templates.  [1957829]

  • Some text on the Desktop Health tab of the Reports page is not being localized.  

    Workaround: None   [2019363]

Revision History

Date Description
31 JAN 2018
  • Initial release
08 JUN 2018
17 SEP 2018
  • Added Known Limitations - Updating Images Using Console Access
22 FEB 2019
  • Fixed link in NVIDIA section
check-circle-line exclamation-circle-line close-line
Scroll to top icon