VMware Horizon Cloud on Microsoft Azure 1.5

VMware Horizon Cloud on Microsoft Azure 1.5

Release Notes

About VMware Horizon Cloud Service on Microsoft Azure

With VMware Horizon Cloud Service on Microsoft Azure, your end users can securely access their Remote Desktop Service (RDS) desktops and remote applications from any device. The environment combines the management simplicity of the Horizon Cloud control plane with the economics of Microsoft Azure. The overall environment consists of the VMware-hosted cloud service, your provided capacity in the Microsoft Azure cloud, and VMware software deployed into that capacity. You connect your Microsoft Azure subscription to Horizon Cloud to manage and deliver virtual RDS-enabled Windows servers and remote applications. Setting up the environment involves deploying the required VMware software into your Microsoft Azure capacity. The deployed VMware software creates an appropriately configured entity, called a Horizon Cloud node, which pairs with the control plane. After the node is deployed, then you use the control plane to create RDSH farms and entitle remote desktops and applications to your end users.

What's New

The VMware Horizon Cloud Service on Microsoft Azure 1.5 release includes the following new features. For details, see this release's Administration Guide.

• Schedule-based power management for RDSH servers in a farm. This new feature provides the ability to schedule the shutdown of a farm's servers on weekends, holiday, and non-working hours. Scheduled shutdowns can optimize cost savings. The feature also provides the ability to schedule a higher minimum server count to address times when you know your end-user demand will be higher and you want to ensure the number of powered-on servers will be available to meet that demand.
• Support for using Microsoft Windows Server 2016 with GPU NV6-sized VMs for the master NV6-sized server images.
• Support for running more than 20 sessions on GPU-enabled RDS desktop servers, when Microsoft Windows Server 2016 is used.
• Enhanced Unified Access Gateway configuration, including support for RADIUS-based two-factor authentication. Unified Access Gateway enables access to the node's desktops over the Internet, for users outside of your corporate network.
• Ability to use the Administration Console to update the agents on sealed images and on those RDSH farm servers based on updated images.
• Ability to use the Administration Console to update the deployed node's software to the latest version.
• Expanded assignment types now include a customization type. The previous URL redirection assignment type has been reimplemented as a customization assignment.
• Ability to add an auxiliary domain-join account that Horizon Cloud can use for domain-join-related tasks if the primary domain-join account is inaccessible.
• Ability to use the Administration Console to duplicate an existing sealed image. Duplicating the sealed image results in an unsealed image with a new name, configured identical to the existing image, and ready to be sealed.
• Ability to cancel some types of farm-related tasks before they complete.
• Expanded alerts and monitoring capabilities in the Administration Console:
  • Alerts displayed when the health of desktop virtual machines (VMs) goes beyond default thresholds for CPU, memory, and disk IOPS.
  • Alerts displayed when the system detects the primary domain-bind account is locked out.
  • Additional information about a farm's RDSH servers, such as server IP address, agent status, DNS name, and operating system details.
• When manually configuring a master VM, a new single unified Horizon Agents Installer is available for installing the required Horizon and DaaS agents into master VMs. Previously, two installers were required, one per agent.

Before You Begin

Review this information as you prepare to deploy this release of VMware Horizon Cloud Service on Microsoft Azure.

• Set-Up Prerequisites: Review the set-up prerequisites before you start creating a Horizon Cloud node in your Microsoft Azure cloud. See the following documents:
  • VMware Horizon Cloud Service on Microsoft Azure Requirements Checklist
  • Getting Started with VMware Horizon Cloud Service on Microsoft Azure
• Software Downloads: Review the software downloads you might want for your environment from My VMware®. Even though these downloads are optional to have before you get started with your deployment, you might want to review them prior to deploying. See the VMware Horizon Cloud Service on Microsoft Azure 1.5 download page.
• User Settings Persistence: You can provide persistence of user profiles using VMware User Environment Manager™ with folder redirection. You can download the User Environment Manager software that is supported for use with this release from the VMware Horizon Cloud Service on Microsoft Azure 1.5 download page.

Best Practices

Knowledge of the following facts is useful before using VMware Horizon Cloud Service on Microsoft Azure.

• 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.
• Subscriptions and Number of Nodes: Be mindful about the number of nodes you deploy into a single subscription, especially if you plan to have each node running at a large scale. Even though multiple nodes can be deployed into a single Microsoft Azure subscription, whether all into one region or spread across multiple regions, Microsoft Azure imposes certain limits within a single subscription. Because of those Microsoft Azure limits, deployment of a large number of nodes into a single subscription increases the likelihood of hitting those limits. Numerous variables, and combinations of those variables, are involved in reaching those limits, such as the number of nodes, the number of farms and assignments within each node, the number of servers within each node, the number of desktops within each assignment, and so on.
  If you plan to have nodes running at a large scale, consider adopting the approach of having multiple subscriptions with those multiple subscriptions under one Microsoft Azure account. Microsoft Azure customers can, and often prefer, this approach because it provides some benefits for ongoing management of the subscriptions. Using this approach, you would deploy a single node per subscription, roll up those subscriptions in a single "master" account, and avoid the chances of hitting the Microsoft Azure limits that are imposed on a single subscription.

Product Documentation and Additional Helpful Resources

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

Visit the community site for helpful tips and to ask any questions. White papers are also available in the Resources section of the Horizon Cloud product page.

Known Limitations

• The service is currently available in the following three Microsoft Azure cloud environments:
  • Microsoft Azure (standard global regions)
  • Microsoft Azure in China
  • Microsoft Azure Germany
• Outbound Internet access is required on the Microsoft Azure Virtual Network (VNet) that is connected to the node's temporary jumpbox VM and node manager VM. Proxy-based authentication is not supported in this release.
• Login authentication into the Horizon Cloud Administration Console relies on My VMware account credentials. If the My VMware account system is experiencing a system outage and cannot take authentication requests, you will not be able to log in to the Administration Console during that time period. If you encounter issues logging in to the Administration Console's first login screen, check the Horizon Cloud System Status page at https://status.horizon.vmware.com to see the latest system status. On that page, you can also subscribe to receive updates.
• During the ten-minute process of updating a node from an earlier software level to the latest one, end users who have connected sessions to the updating node will have those active sessions disconnected. No data loss will occur — except for the case where the RDSH farm serving the sessions has the Logoff Disconnected Sessions set to Immediately. For such farms, the disconnected sessions are also logged off immediately and in-progress user work is lost in those conditions.
  After the update process is complete, those users can reconnect.
• In this release, each node configured with Unified Access Gateway instances needs its own unique fully qualified domain name (FQDN).
• Your authenticated (logged in) session into the Administration Console will time out after 60 minutes. In most cases, when the 60 minutes is up, the system will automatically explicitly log you out and present a message that you must log back in. However, sometimes the system ends your authenticated session and does not explicitly log you out. When that happens, when performing certain tasks in the Administration Console, error messages might be displayed which do not accurately reflect the current state, such as the Farms page reports no node is available in which to create a farm and error messages stating "No service_sessions of type identity_node were provided". If you start to see such behavior and you have been using the Administration Console for an hour or more, manually log out and then log back in.
• The Administration Console is not supported in the Apple Safari browser. Some user interface features might not work correctly. In a Mac OS, instead of Apple Safari, you can use Chrome or Firefox browsers.
• For GPU-enabled master images, Microsoft Windows Server 2016 is recommended to avoid limiting the number of end user sessions. Due to an NVIDIA driver limitation on Windows Server 2012 R2, the maximum number of sessions for each RDS desktop server is 20.
• In a multi-node environment, re-using the same farm names in different nodes under a single Microsoft Azure subscription is not supported. Due to a known issue, when a farm in one node has the same name as a farm in another node, and those nodes are associated with the same subscription, the farm server VMs lose their domain credentials. To avoid this situation, either do not reuse farm names between nodes or, if you need to reuse farm names, use different subscriptions for those nodes.
• When you deploy a Horizon Cloud node in Microsoft Azure after you have already configured True SSO for previously deployed nodes, the system does not automatically pair the new node with the Enrollment servers. You must manually repeat the steps to export the pairing bundle and import it into the Enrollment servers. For the steps, see the VMware Horizon Cloud Service on Microsoft Azure Administration Guide.
• Follow these rules when entering characters in the Administration Console:
  • Use only standard ASCII characters in 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.
  • When entering names for imported images, farms, assignments, and other assets that result in creating a VM in Microsoft Azure, do not enter more than 12 characters for the name.
  • Do not use commas in user passwords.
  • When using the Import wizard to create a master VM from the Microsoft Azure Marketplace:
    • Enter a username and password that adheres to the Microsoft Azure requirements for VM admin usernames and passwords. See the Microsoft Azure FAQ page for details.
    • Do not enter a name for the image that ends with a hyphen (-).
    • Do not include an underscore character (_) in the image name.

Known Issues

Active Directory Related Known Issues

• If you add the same Active Directory user group to both the Super Administrator role and Demo Administrator role, those users experience unexpected restricted behavior in the Administration Console.
  The Super Administrator role is intended to grant all the permissions to perform all management actions in the Administration Console, and the Demo Administrator role is a read-only role. However, due to this known issue, if you add the same user group to both roles, those users do not receive the permissions of the Super Administrator role. Their actions are restricted in the Administration Console, which might prevent availability of full management of your environment.
  Workaround: Do not assign the same user group to both roles.
• Primary bind account lockout is not detected until you perform an action involving Active Directory in the Administration Console.
  Due to this issue, an administrator logged into the Administration Console will not see a primary bind account lockout notification until an action involving Active Directory is performed in the user interface, such as when searching Active Directory to add users to assignments. The node services only detect a locked-out service account when they make a request to talk to Active Directory for either authenticating or searching (user or group).
  Workaround: None.
• 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.
• 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 duplicate 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, disable duplicate SPN checks in the Active Directory domain.

Images, Farms, Assignments Related Known Issues

• When publishing (also known as sealing) an imported VM, the process might result in a timeout.
  After you click Convert to Desktop on an imported VM to make it a published (sealed) image, a number of operations are performed on the VM. One of the operations involves shutting down and then powering off the VM. However, sometimes the VM might fail to completely shut down. As a result, the conversion process times out. On the Activity page, you see a message similar to "Timeout Error Waited 20 minutes for virtual machine to power off."
  Workaround: On the Images page, use the Convert Image to Desktop action on the image. When the Activity page indicates converting the image to a desktop is successful, navigate to the Imported VMs page. On the Imported VMs page, select the VM and click Convert to Image to run the publishing process again.
• When names that the system uses when creating virtual machines (VMs) are longer than 12 characters, unexpected results might occur.
  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.
• You cannot edit the number of sessions per RDSH server once a farm is created.
  Due to this known issue, a farm's number of sessions per server cannot be changed after the farm is created. If you want to change the number of sessions per server, the farm must be deleted and recreated with the new setting, or create another farm with the setting you want.
  Workaround: None.
• During farm creation, sometimes the server VMs are stuck at the customization step.
  Sometimes during the sysprep process on the farm's server VMs, a Windows service named "tiledatamodelsvc" prevents sysprep from accessing Windows files that it needs to complete the sysprep customization process. As a result, the farm's server VMs do not move past the customization step. The sysprep error log contains the line "Error SYSPRP setupdigetclassdevs failed with error 0".
  Workaround: If you encounter this issue and see that error message in the sysprep error log file, try disabling the "tiledatamodelsvc" service in the image and then creating the farm.
• 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.
• Agent status might display as 'undefined' on the Imported VMs page after duplicating an image or manually creating an image in Microsoft Azure. 
  When you use the Duplicate button on the Images page to clone a published image or when you manually create a master image in Microsoft Azure, the resulting VM is listed on the Imported VMs page. Due to this issue, even when the VM is fully powered-on, the agent status might be displayed as 'undefined'. However, when you select the VM and choose Convert to Image to publish it, the user interface reports the agent in 'Active' state.
  Workaround: None. If the New Image or Convert to Image workflows report the agent as 'Active', you can ignore the 'undefined' status on the Imported VMs page.
• 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.
• When a farm in one node has the same name as a farm in another node, and those nodes are associated with the same subscription, the farm server VMs lose their domain credentials.
  In a multi-node environment, the Administration Console does not prevent you from creating a farm in one node with the same name as a farm in another node from the same Microsoft Azure subscription. Due to this know issue, if both nodes are under the same subscription and you give a farm in each node the same name, this issue occurs.
  Workaround: To avoid this situation, either do not reuse farm names between nodes or, if you need to reuse farm names between nodes for business purposes, use different subscriptions for those nodes.

Reports Related Known Issues

• In the User Activity report, the displayed weekly average (hrs) is not intuitive 
  Due to this issue, the weekly statistics fluctuate along the time because the calculation logic is dividing the current week's duration by seven (7) and not rounding up to a whole week. For example, when you select the last 30 days, the data for completed weeks is unchanged but the data for the current week is divided by seven (7). The current logic is weekly average (hrs) = daily average (hrs) * 7 days, resulting in the last 30 days weekly average = (total duration / 30 days) * 7 days.
  Workaround: None.
• The Desktop Health report does not reflect a newly updated farm name until an hour after the name change.
  If you change a farm's name, 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.
• The formatting in some of the CSV files that you can export from the Reports user-interface screens do not match the on-screen tables.
  Some of the Reports page's subscreens provide an export feature to export the displayed data in CSV format. Due to this issue, the formatting in the CSV files exported from the Desktop Health, Concurrency, and Session History reports do not precisely match the ones you see displayed on the screen. For example, the column headings might be different and the CSV files might have more columns of data than in the on-screen tables.
  Workaround: None.

Identity Management, True SSO Related Known Issues

• After you upgrade your VMware Identity Manager Connector from version 2017.8.1.0 to version 2017.12.1.0, the sync operation might fail. 
  Due to a known issue in VMware Identity Manager Connector version 2017.12.1.0, after the connector restart when upgrading the connector, the sync operation in the VMware Identity Manager administration console might fail.
  Workaround: Save the virtual app collection again by re-entering the administrator password for the tenant and then sync.
• While a node deployment is in progress, the Administration Console's Active Directory page does not display the True SSO Configuration section 
  During the time a node is being deployed, the True SSO Configuration section is not visible on the Active Directory page. Due to this issue, if a node deployment is not yet completed, the Active Directory page does not display the True SSO Configuration section.
  Workaround: Check the state of your nodes on the Capacity page. If one or more nodes have yet to finish onboarding into the system, wait until its progress is completed before attempting to perform True SSO configuration.

User Interface Related Known Issues

• When using the Administration Console, you might see placeholders instead of the actual text strings or you click a button on a page and nothing happens.
  VMware periodically updates the in-cloud management environment that hosts the Administration Console. This issue can occur when static content has been cached in the browser prior to the latest in-cloud update. It is a temporary issue that will clear when the browser cache is cleared.
  Workaround: Try logging out of the Administration Console, clearing the browser cache, restarting the browser, and then logging back into the Administration Console.
• After being logged in to the Administration Console for an hour or more, as you perform some tasks, error messages might be displayed that do not reflect the current state of the system.
  Your authenticated (logged in) session into the Administration Console will time out after 60 minutes. In most cases, when the 60 minutes is up, the system will automatically explicitly log you out and present a message that you must log back in. Due to this issue, sometimes the system ends your authenticated session but does not explicitly log you out. When that happens, when performing certain tasks in the Administration Console, error messages might be displayed which do not accurately reflect the current state, such as the Farms page reports no node is available in which to create a farm and error messages stating "No service_sessions of type identity_node were provided".
  Workaround: If you start to see such behavior and you have been using the Administration Console for an hour or more, manually log out and then log back in.
• Application names are displayed in lowercase characters when end users access them using Workspace ONE
  When your Horizon Cloud environment is integrated with VMware Identity Manager, your end users access their assigned desktops and applications using Workspace ONE. Due to this know issue, the users see the application names displayed with lowercase characters, regardless of the actual case used in the application names. This limitation is due to the way VMware Identity Manager creates launch IDs from Horizon Cloud by using older Horizon Cloud REST APIs.
  Workaround: None.
• 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 desktop 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.
• If a desktop VM's CPU usage is at or close to 100%, the desktop alert is not triggered. 
  If an application or something in the desktop VM causes the VM's CPU usage to reach 100%, the desktop agent fails to send as many data samples as it usually sends to Horizon Cloud because the CPU is very busy. As a result of the low sample count returned, the calculation the system uses to trigger the desktop alert is affected.
  Workaround: None.

Node Updates Related Known Issues

• While a node is undergoing an update, active end user sessions to that node are disconnected.
  During the ten-minute process of updating a node from an earlier software level to the latest one, end users who have connected sessions to the updating node will see those active sessions disconnected. However, no data loss will occur — except for the case where the RDSH farm serving the sessions has the Logoff Disconnected Sessions set to Immediately. For such farms, the disconnected sessions are also logged off immediately and in-progress user work is lost in those conditions.
  Workaround: None. After the update process is complete, those users can reconnect. To prevent data loss for end users, before running the update, make sure the settings in the node's farms do not have Logoff Disconnected Sessions set to Immediately.

Localization Related Known Issues

• Message about node availability is not localized.
  You will see the message "None of your nodes are online or available." in English.
  Workaround: None.
• When non-ASCII or high-ASCII characters are used in the True SSO template name, retrieving the template fails.
  Due to this known issue, if your True SSO template name contains non-ASCII or high-ASCII characters, you cannot successfully configure True SSO with your Horizon Cloud environment.
  Workaround: To avoid this issue, use only ASCII characters in the names of your True SSO templates.
• Some of the strings in the Desktop Health page's desktop health alerts are not localized.
  Workaround: None.

Previous Issues Resolved in this Release

Resolved Active Directory Related Issues

• After your first node is in Ready state on the Getting Started page, if you wait 30 minutes or longer to perform the Register Active Directory Domain task and do not explicitly log off before starting to register the domain, an error appears.
  Fixed in this release: During the node onboarding process, progress is displayed on the Getting Started page. If 30 minutes or more has passed between the time the page shows the node is ready and you begin to register the domain, an error might appear that states 'No service_session of type "identity_node" were provided.'
• In the Register Active Directory window, if the specified domain is unreachable or the specified credentials are incorrect, after you try twice to submit the information, the system logs you off, displays the Horizon Cloud Administration Console's login screen and you have to log in again.
  Fixed in this release: When using the Active Directory page to register an additional Active Directory domain, after the first time you click Domain Bind in the Register Active Directory window, if Horizon Cloud cannot reach the specified domain or if the specified domain-bind account credentials are incorrect, an error message displays and you can return to the Register Active Directory window and try again. If the same thing happens a second time, instead of returning to the Register Active Directory window, the system logs you off.
• Editing the default value in the domain join's Default OU field in the Active Directory page does not persist in the system.
  Fixed in this release: Even though you can edit the domain join's default OU value on the Administration Console's Active Directory page, the change does not persist in the system. The default OU for the AD domain registered with the node continues to be CN=Computers. However, even though the node's default OU is CN=Computers, you can change the default OU for a farm and assignments are created using the farm's OU.
• When you expand the Advanced Properties in the Edit Active Directory window, a copy of the existing auxiliary domain bind account automatically appears in the window, and the only way to remove it is to cancel out of the window.
  Fixed in this release: In the Administration Console, you open the Edit Active Directory window to edit the domain bind information by clicking Settings > Active Directory and clicking Edit next to the Domain Bind section on the page. In that Edit Active Directory window, when you click Advanced Properties, a copy of the existing auxiliary account automatically appears in the window as the next auxiliary account. You must cancel out of the window to remove this automatically added copy.

Resolved Images, Farms, Assignments Related Issues

• In the Import Desktop - Marketplace window, the 3D Support in RDSH option is selected by default, even though it is not supported for use in Windows Server 2016
  This issue is fixed in this release. Previously, when the default 3D Support in RDSH option was installed on a Windows Server 2016 RDS host, the published desktop will launch with a black screen. In this release, the Horizon agent and its options are supported for use in Microsoft Windows Server 2016.
• During a farm's rolling maintenance, reduced availability for end user RDS session desktops and remote applications might occur. 
  Fixed in this release: If there are no end user sessions a farm's servers just before the maintenance window, all servers are shut down at the same time for maintenance. Then, if high demand occurs for user sessions to the RDS desktops and remote applications that are served by that farm right after the maintenance process begins, the farm will not be able to accept even a single user session for a span of three to five minutes.
• While a farm's servers are undergoing power operations, if you click on the Servers tab from the farm's details page, the page might not display any information.
  This issue is fixed in this release.
• For an application that was originally manually added to the inventory, when you subsequently edit the application from the Applications page and change the icon, the previous original icon continues to be displayed to end users and also re-appears in the Horizon Cloud Administration Console's Applications page eventually.
  Fixed in this release: If you edit the application to upload a new icon, you see the new icon on the Applications page. However, the end users assigned to that application continue to see the original icon. Eventually, the original icon reappears in the Administration Console's Applications page also.

Resolved True SSO Related Issues

• When you test the pairing of the Enrollment Server after importing the pairing tokens, the system reports pairing failed even though the pairing is fine.
  Fixed in this release: Due to some temporarily cached information, when you are configuring True SSO in the Administration Console and you click Test Pairing, sometimes the system reports failure even though the pairing is fine. The cached information is updated every minute, so if you wait a minute and re-try, the system reports the actual successful pairing.
• When non-ASCII or high-ASCII characters are used in the True SSO template name, retrieving the template fails.
  Fixed in this release: If your True SSO template name contains non-ASCII or high-ASCII characters, you cannot successfully configure True SSO with your Horizon Cloud environment.

Resolved User Interface Related Issues

• Even after the Getting Started wizard's tasks are completed and you see the completion bar at 100%, when you log out and then log in again to the Administration Console, you see the wizard's progress bar displaying 33% completion.
  Fixed in this release: When you have the setting to show the Getting Started wizard at startup, the system displays the wizard as the first screen every time you log in. Due to this issue, as long as that setting is on, the progress bar displays at 33% completion each subsequent time you log in.
• When the end user clicks the Reset menu action on their browser-based RDS desktop session, the Logoff action is temporarily disabled for up to 5 minutes.
  Fixed in this release: When an end user uses a browser to access an RDS desktop session, the action menu on the desktop includes a Reset choice. To reset a desktop means to reboot the desktop's underlying VM. For RDS desktops where there are multiple users with sessions using the same server, the system appropriately prevents a single user from performing the reset action. However, due to a known issue, when the end user clicks the Logoff action after clicking Reset, a message says the desktop cannot be logged off.
• When using the Administration Console in Microsoft Internet Explorer 11, you might see placeholders instead of the actual text strings.
  Fixed in this release: This issue is due to static content being cached in the browser. It is a temporary issue that will clear when the browser cache is cleared.

Resolved Localization Related Issues

• When using the localized product version, some messages might display the English text.
  This issue is fixed in this release.