check-circle-line exclamation-circle-line close-line

VMware Horizon Cloud Service with Hosted Infrastructure 18.4 Release Notes

VMware Horizon Cloud Service with Hosted Infrastructure 18.4 | 20 SEP 2018 

See Revision History below 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.1 | 16.11.2* | 17.1 | 17.1.1 | 17.2 | 18.1 | 18.3

What's in the Release Notes

The release notes cover the following topics:

Product Documentation

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.

New Features

Option to Migrate Dedicated Desktops Between Assignments

There is a new option to migrate dedicated desktops between dedicated desktop assignments within the same pod (desktop manager).

  • Selected VM(s) must meet the following requirements:

    • Have all users logged off.

    • Be domain joined.

    • Have the same domain and OU as the target assignment.

  • There is an option to rename the VM when you migrate it

  • You can view migration progress and status in Monitor > Activity.

This option is described in the Assignments section of the Administration guide.

Historical Session Data In User Card

The Sessions tab in the user card now shows both current and historical sessions. 

  • The list of sessions on the Sessions tab can now be adjusted to show historical data. By default, only current sessions are shown. There is a new drop-down menu on the tab that allows you to show historical data for up to seven days.
    Note: Since by default current sessions are shown, the Sessions tab will show a value of 0 at the top when there is no current session. When you adjust the display to show historical data, this number is updated to the number of sessions in the selected period.
  • When you click on a session, the Details sub-tab also now has an option to show real-time or historical data under User Experience Metrics. This option only appears if there is a current session.

New Active Directory Option for Automated Certificate Management

There is a new option called LDAP over TLS on the Active Directory registration page (Settings > Active Directory > Register) and Active Directory edit page (Settings > Active Directory > Edit). This option enables LDAP communication via TLS, which automates certificate deployment and management. It is disabled by default.

Note the following:

  • This setting is hidden by default and only appears if you have requested that VMware unhide it for you. 
  • To successfully disable this setting after enabling it, you need to both turn it off in the Administration Console and disable the "Require signing" policy on the Active Directory.

Outbound Proxy Configuration in Administration Console - Provides Access to Cloud Monitoring Service (CMS) 

You can now configure an outbound proxy in the Administration Console.

  • While this proxy may have other uses in the future, the initial capability it adds is access to Cloud Monitoring Service (CMS). Previously, if your firewall and network settings did not permit access to CMS, which is hosted on Amazon Web Services (AWS), you could not make use of CMS functions.
  • There is a new Outbound Proxy Options setting on the General Settings page (Settings > General Settings) that you can edit to configure the proxy. For more information, see the Settings section of the Administration guide.

Other Changes in This Release

DNS Server IP Edits for Domain Join Require Support Ticket

When editing an existing Active Directory Domain, you can no longer directly edit DNS Server IPs in the Administration Console. To change DNS Server IPs, file a ticket with VMware support.

Default Limit of 2,000 Desktops Per Pod

There is now a default limit of 2,000 VMs per pod, both in desktop assignments and in farms. This includes VMs created in earlier versions of the product, but does not include Utility or Imported desktops. When you are creating or editing an assignment or farm and the remaining capacity displayed appears to be too low, it may be because this limit has been reached. The default limit of 2,000 can be adjusted on request. For more information, contact your VMware representative.

Changes to Activity Page

The Activity page (Monitor > Activity) now functions as follows:

  • When the number of records is at or below a set threshold (by default 5,000), the system displays 1,000 records per page and the search function/bar is enabled.
  • When the number of records is above the threshold, the system displays 1,000 records per page and the search function/bar is disabled.
  • The threshold value may be changed by your VMware representative.
  • To see all records, use the export functionality.

Console Access Option No Longer Available in Helpdesk Console [Beta Feature]

The option to launch a console for a VM in the Help Desk Console (https://<Hostname>/haca) is no longer available. You can launch consoles for VMs in the Administration Console by using the Launch Console option on the Desktops tab of the Assignments page (Assign > Desktops), the Servers tab of the Farms page (Inventory > Farms > Servers), the Imported VMs page (Inventory > Imported VMs), or the Utility VMs page (Settings > Utility VMs).

Note: The option to launch VM consoles from the Helpdesk Console is still available for tenants running a version lower than 18.4 in a staggered environment, but may not function on those tenants.

Best Practices

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

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.

Known Limitations

Agent Upgrade to HAI 18.4 Requires Use of BAT File

When you upgrade from an older agent build to the HAI 18.4 using the HAI user interface, the installer creates the HAI-upgrade.bat file and then interrupts the upgrade, prompting you to close the user interface and complete the upgrade using the BAT file.

When the upgrade is complete, the VM will be rebooted automatically. You can prevent this reboot by doing either of the following:

  • Update the command-line options in the HAI user interface before the BAT file is generated, adding /norestart at the end of the command.
  • Manually update the generated HAI-upgrade.bat file, adding /norestart at the end of the command.

Note: The VM must be rebooted some time after the upgrade in order for the Agent to be usable.

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.

Copying and Pasting Between Client System and VM With HTML Access

Copying and pasting text between a client system and a VM is supported by default when the user is connected via the Horizon Client. When the user is connected via HTML Access, however, you must configure this feature before the customer can use it. For more information, see the VMware Horizon HTML Access documentation.

Users Still Able to Log Into Dedicated Desktops After Being removed From User Group

If a user is in an Active Directory group that is assigned to a dedicated desktop assignment, once the user has logged into a particular desktop they will be able to continue logging into that same desktop until until the user is unassigned from that desktop in the Administration Console, unless either the user is removed entirely from the Active Directory or the desktop is deleted.

Wait Time for Generating Admin Activity Report

When you initiate an export on the Admins tab of the Activity page (Monitor > Activity > Admins), there is an interval of time as the system generates the report, during which you are not able to perform other tasks in the Administration Console. Depending on the number of records, this interval can be several minutes long. For the maximum report size (50,000 records), the wait time is approximately 10 minutes.

Data Sorting in Exported User Activity Report

When you export data from the Users tab of the Activity page (Monitor > Activity > Users), the data in the generated .csv file is not sorted by date. There are two options for correcting this:

  • Open the .csv file in Excel and set the date format for the cells containing dates to mm/dd/yy hh:mm AM/PM (e.g. 3/14/12 1:30 PM).
  • Create a new blank Excel workbook and then use the data import wizard to import the .csv file.

Time Interval Before Changes to Settings Take Effect

When you change one of the following settings, it can take up to 15 minutes for the change to take effect.

  • General Settings page (Settings > General):
    • Session Timeout - Client Heartbeat Interval, Client Broker Session, Client Idle User
    • HTML Access - Cleanup credentials when tab is closed
    • Pool/Farm Options - Enable Client Retry
  • Identity Management page (Settings > Identity Management):
    • Select item and click Configure - Force Remote Users to Identity Manager

Resolved Issues

The following issues have been resolved in version 18.4.

  • If you logged into the Administration Console as a Help Desk Administrator or Help Desk Read Only Administrator and then logged out and logged in again as Super Administrator within the same browser session, the options displayed were not correct. This has been fixed in the current release. [2139808]

  • Creating an Instant Clone image could fail with an error similar to the following. This error no longer occurs in this situation.

    Converting to an image - Error
    Unable to send message=‹xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx› SEAL QUICK_PREP, all sender types have been exhausted.

      [2140570]

  • When updating agents for an assignment, if there were desktops that had not been upgraded because they had active user sessions the Upgrade task and the Agent Upgrade status popup on the Assignments page indicated that the upgrade had failed, even though a subset of the desktops had upgraded successfully. This has been remedied so that it no longer occurs.  [2139713]

  • You could not edit the number of sessions per RDSH server once a farm was created. This issue has been addressed, so you can now edit the number of sessions per RDSH server as expected. [1932001]

Known Issues

Issues that are new in this release are in bold.

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.

    Workarounds:

    [1969172]

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

Images, Farms, Assignments - Known Issues

  • When you publish a Windows 7 image with Image Sync enabled, the new image may be in 'offline' state on the Images page, even though the publish and sync tasks are shown as successful.

    Workaround: Contact your VMware representative, who can resolve this issue for you. [2197017]

  • When you attempt to update the agent on an image, the convert-to-image task may fail on the cloned VM. 

    Workaround: Delete the clone VM (not the original image) and retry. The clone VM will appear in Utility VMs. If the retry is unsuccessful, save the clone VM, perform the steps below to get the DCT logs, and then contact your VMware representative.

    1. On the clone VM, browse to C:\Program Files\VMware\VMware View\Agent\DCT and open the file 'support.bat'.

      A cmd prompt window opens and prints several messages stating which logs are currently being gathered. This process may take a few minutes to complete.

    2. When prompted to collect dump files enter 'n' unless VMware has requested that you gather dump files.

      A zip file is placed on the desktop containing collected logs.

    For more information on obtaining logs, see the following KB: https://kb.vmware.com/s/article/1017939.

    [2202387]

  • When you use the Update Agent feature from an agent version earlier than 18.2.2, the update process can hang on desktops that have a 'run once' pending.

    Workaround: Perform the agent update, adding the following command line argument on the Command Line tab of the Agent Update wizard:
    VDM_SUPPRESS_RUNONCE_CHECK=1

    [2191312]

  • When you have two dedicated desktop assignments associated with the same group of users, the following issue can occur. If a user opens a desktop from one of the assignments using the Horizon Client and then a user attempts to open a desktop from the other assignment with the Horizon Client, the second attempt fails with an error indicating the user is not entitled to the desktop.

    Workaround: Open the desktop in the second assignment using the browser instead of Horizon Client. [2201599]

  • When you create a new image, then run Publish on it and it reaches Published status, then you run Convert to Desktop on that image, then run Publish again, the sysprep process that happens in the publishing workflow can fail. If you again convert the image back to an unsealed image, from that point on, the image might always fail the publishing workflow.

    Workaround: None. If you find the image is always failing the publishing workflow, it is prudent to start fresh and make a new base image. [1965320]

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

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

    • PXE-E53 : No boot filename received
    • PXE-MOF: Operating System not Found.
  • 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]

  • 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

  • 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]

  • 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]

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
20 SEP 2018
  • Initial release
26 SEP 2018
  • Added New Feature - Proxy Config in Admin Console
28 SEP 2018
  • Added Known Issues 2202387 and 2197017