VMware Horizon Cloud Service on IBM Cloud 19.1 | 21 MAR 2019 

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

Links to release notes for other versions: 19.3 | 20.2.0 | 21.1.0

Note: As of February 7, 2019, VMware Horizon® Cloud Service™ on IBM Cloud is the new brand name for what was formerly known as VMware Horizon® Cloud Service™ with Hosted Infrastructure. In the product documentation for current releases, customers will continue to find legacy references to previous names. These references will be phased out in subsequent releases. The product documentation for older releases will continue to reflect the names they had at the times they were released.

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 - Horizon Agent Installer 19.1.1 - Released August 2019

Horizon Agent Installer (HAI) 19.1.1 has been released.

  • Horizon Agent Installer 19.1.1 addresses a keyvault issue that can result in failures when attempting to upgrade from earlier agent versions.
  • For the Agent Auto-Update feature, Horizon Agent Installer 19.1.1 is now the supported agent for Horizon Cloud Service 19.1 tenants, replacing Agent Auto-Update's use of the 19.1.0 agent.

New Features

  • Import VMs in the Horizon Cloud Administration Console

    See the Imported VMs section of the Administration Guide.

  • Generate logs for VMs in assignments, as well as images and imported VMs

    See the Assignments, Images, and Imported VMs sections of the Administration Guide.

    Note: This feature requires Horizon Agent Installer 19.1.

  • Bulk assign images to multiple assignments/farms

    See the Images section of the Administration Guide.

  • Outbound proxy configuration 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. See the Settings section of the Administration guide.

  • Enhanced desktop migration

    VMs can now be moved between dedicated assignments on same or different Desktop Managers. See the Assignments section of the Administration Guide.

  • Domain security enhancements

    There are new settings to prevent sending Active Directory domain names to the Horizon clients and display of the names in the Horizon clients prior to end-user login.

    • To prevent communication of domain names to unauthenticated users, Horizon Cloud administrators can control whether domain-related information is sent to the Horizon clients before the end user logs in, and whether any sent information is displayed in the various Horizon clients' login screens. Use these settings to achieve your desired security level. For detailed information about these settings and the usage scenarios, see the Settings section of this release's Administration Guide. The choices for the end-user client experience are:
      • No domain information is displayed in the client login screen.
      • Only pre-defined text *DefaultDomain* is displayed in the client login screen. This choice is provided to support Horizon clients older than version 5.0.
      • Active Directory domain names are displayed in the client login screen (this is the legacy display behavior in previous releases).
    • With the availability of these security settings in this service release, the system defaults that are applied to your Horizon Cloud environment as of this service release depend on whether you have an existing customer account or a new account starting with this release:
      • New Horizon Cloud customer accounts are configured by default so that no domain information is sent to the client prior to end-user login and the domain field is displayed in the client login screen as *DefaultDomain*. For a new customer account having new pods, end users connecting to their pod-provisioned desktops will see this behavior unless you use the Administration Console's General Settings page to change the domain security settings. Important: This configuration sets requirements on how your end users specify their domain information in the client login screen, especially when using older clients and for environments configured with multiple Active Directory domains. For details, see this release's Administration Guide.
      • Existing Horizon Cloud customer accounts are configured by default to provide the legacy behavior as it was in the previous service level. In this case, Active Directory domain names are sent to the clients and end users connecting to your existing pod-provisioned desktops will see the names displayed in the client login screen. To control the behavior, all existing pods must be upgraded to this release.
      • Until all of your existing deployed pods are upgraded to this release, the new Domain Security Settings controls are not available in the Administration Console's General Settings page. If you have a mixed environment with existing non-upgraded pods and newly deployed pods at this release level, the new controls are not available. When all of the account's pods are upgraded, the settings are available in the Administration Console for adjusting to your desired behavior.

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.

Creating a Template Desktop VM

When you are creating a template VM, after you have finished configuring it run the following command in Windows PowerShell:

Get-AppxPackage|Remove-AppxPackage

This prevents a possible sysprep issue that leads to image publish failure.

Known Limitations

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.

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

Converting a Desktop to an Image

If you initiate converting a desktop to an image but cancel before the task finishes, a second attempt to convert the desktop to an image may fail. To avoid this issue, you should power off the desktop and power it on again before attempting to convert it to an image a second time.

Resolved Issues

The following issues have been resolved in version 19.1.

  • When you created a new image, then ran Publish on it and it reached Published status, then you ran Convert to Desktop on that image, then ran Publish again, the sysprep process that happens in the publishing workflow could fail. If you again converted the image back to an unsealed image, from that point on, the image might always fail the publishing workflow. This issue has been fixed so that these failures no longer occur. [1965320]

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:

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

    [1969172]

Images, Farms, Assignments - Known Issues

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

  • 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: Deactivate 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: Deactivate IPv6 for the image.  [2017500]

User Interface - Known Issues

  • The Administration Console displays as blank.

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

  • 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 MAR 2019
  • Initial release
02 AUG 2019
  • Known Limitation for Converting Desktop to Image
19 AUG 2019
  • Added HAI 19.1.1
check-circle-line exclamation-circle-line close-line
Scroll to top icon