VMware Horizon Air Hybrid-Mode 1.0 Release Notes

VMware Horizon Air Hybrid-Mode | 12 MAY 2016

Updated on: 12 MAY 2016

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

About VMware Horizon Air Hybrid-Mode

This section contains information about VMware Horizon Air Hybrid-Mode.

For more information, see VMware Horizon Air Hybrid-Mode Documentation.

VMware Horizon Air Hybrid-Mode is a hybrid cloud software service hosted by VMware that enables organizations to deliver virtual desktops and applications from on-premises infrastructure, while centrally managing it all from the cloud. Horizon Air Hybrid-Mode allows you to leverage the best of both worlds: the economics and the simplicity of the cloud with the security and performance of on-premises infrastructure. Horizon Air Hybrid-Mode consists of a cloud service, Horizon Cloud Services, which pairs with an on-premises component, Horizon Air Node.

Horizon Cloud Services – A control plane hosted in the cloud by VMware for central orchestration and management of virtual desktops, applications, and user profiles on on-premises infrastructure.
Horizon Air Node – Optimized hardware including Virtual SAN Ready Nodes and supported hyper-converged infrastructure that run on the organization’s premises, connected to the cloud control plane by way of integrated Horizon Air Hybrid-Mode software.

Before You Begin

Take the following actions before you install, configure, and use this version of Horizon Air Hybrid-Mode.

Best Practices

Knowledge of the following facts is useful before using Horizon Air Hybrid-Mode.

  • Tips for User & Application Management – See the Tips for User & Application Management document.
  • Customizations – The Administration Console enables administrators to customize the user environment. For example, assigning a printer based on contextual conditions. This beta feature is available for customers to evaluate and provide feedback. For production use cases, customers should use the Windows based User Environment Manager administration console.
  • Browser Experience – If you experience issues with the Safari or Edge browser, use another browser, such as Firefox, Chrome, or Internet Explorer and confirm if the issue persists.
  • Knowledge Base Articles – The following VMware Knowledge Base articles apply to this version of Horizon Air Hybrid-Mode.
    • Deleting or updating an assignment might disable writable disks. See KB 2144688.
    • The text in the Administration Console appears blurry when accessed from Windows. See KB 2145320.
  • ASCII Characters – Require the use of ASCII characters in path names, user names, and OVA file names. Avoiding the use of non-ASCII characters in these cases prevents undesirable behavior.

Known Issues

The Known Issues are grouped as follows:

Set Up and Configuration

  • Radius Authentication fails when Access Point does not resolve the host name within the appliance
    In the following cases, the Access Point console shows new-hostname instead of localhost or the previously configured custom-hostname.
    • During an Access Point deployment, the appliance might reconfigure and replace its default host name, localhost, with a custom host name, according to the definition in the DNS server records.
    • You can install Access Point manually by configuring a custom host name to comply with other network configurations and best practices.
    • You can reconfigure the existing default or custom Access Point host name to a new host name after deployment.
    In these situations, new-hostname will not resolve its loopback IP address (127.0.0.1) by default, which leads the Radius authentication adapter to fail to resolve the loopback IP address using the new host name.
    Workaround: Add the Access Point host name next to the localhost entry in the /etc/hosts file. For example, 127.0.0.1 localhost new-hostname.
  • Desktop remote access using the Blast protocol fails while connecting through an Access Point appliance configured with Certificate Authority (CA) signed SSL certificates
    When you configure an Access Point certificate, the Privacy Enhanced Mail (PEM) file might contain additional text outside of the certificate text, such as a Bag Attributes section. The presence of such text causes the Blast Secure gateway to fail, effectively preventing remote desktop access using the blast protocol.
    Workaround
    : While configuring an Access Point 2.5 or 2.6 SSL certificate, manually edit the certificate files in PEM format, removing all the text before -----BEGIN CERTIFICATE----- and all the text after -----END CERTIFICATE-----.
  • After you create an image, install agents, and restart the virtual machine, a harmless error message appears
    As an administrator, after you install the App Volumes Unified Installer and restart the virtual machine as prompted, logging back in causes a connection error message to appear. The error message appears because the App Volumes Unified Installer cannot connect to the App Volumes Manager with which it is configured. The connection issue is caused by an access restriction of the local administrator user because the local administrator user is not joined to the domain and, therefore, not entitled to access the App Volumes Manager.
    Workaround: Ignore the error message. This issue does not block any functionality.
  • The Active Directory screen displays the primary and secondary DNS server IP addresses in an uncertain order
    The Primary DNS Server IP label always lists the IP address that is the smallest number, regardless of if the number is for the primary DNS server or for the secondary DNS server. The Secondary DNS server IP label always lists the remaining IP address. Therefore, the IP address information might be incorrect.
    Workaround: Do not rely on the Active Directory screen for accurate IP address information.
  • Desktop connectivity issues might occur when you deploy Access Point on the same network (VLAN) as the clients and desktops
    If you connect to a desktop through Access Point using the Blast protocol, you might encounter desktop connectivity issues. To access the desktop, you might need to connect again using the Horizon Client.
    Workaround: Since this issue only occurs when Access Point is deployed on the same VLAN on which the client machines and desktops are deployed, prevent the issue by deploying Access Point on a different VLAN.

End User Issues

  • The Disconnect and Log Off option might fail to log off the desktop session
    If a session is established to a desktop or clone a significant period of time after the creation of the clone, selecting the Disconnect and Log Off option in the Horizon Client might fail to log off the desktop session. In such a case, the session goes into a disconnected state.
    Workaround: Perform one of the following procedures to log out of the desktop session.
    • Log off or sign out of the session by logging off of the Windows guest operating system.
    • In the Administration Console, select the disconnected clone or session and log out. This operation kills the session and the clone is resynchronized.
    • As a user, log in to the disconnected session using the Horizon client. Then select the Disconnect and Log Off option.
  • When you capture Microsoft Office suites in separate bundles and assign two or more together, a dialog box appears the first time users launch applications from the bundles
    Deploying multiple Microsoft Office bundles concurrently, initiates a permanent behavior where a harmless reconfiguration dialog box appears and soon disappears during the initial launch of an application from the bundles. After the dialog box disappears, users can access and use the application.
    Workaround: To prevent the dialog box from appearing, enable one bundle containing Microsoft Office applications at a time or in a bundle include all of the Microsoft Office suites.
  • Updating the computer-name prefix of an existing application assignment might change the writable volumes associated with the assignment
    Writable volumes are shared across application assignments based on matching operating system and computer-name prefixes. Therefore, updating the prefix might result in the system presenting a different writable volume, which would not contain any of the data saved to the previous writable volume.
    Workaround: Do not create or update application assignments with longer (more specific) computer-name prefixes than the computer name prefixes used for existing application assignments.
  • When you attempt the initial log off of a dedicated desktop assignment from the Horizon Client menu, the logoff fails
    The first time you log on to a dedicated desktop assignment, attempts to log off of the desktop from the Horizon Client fail.
    Workaround: To work around the issue, for the initial log on, use the Windows Menu item to log off, not the log-off buttons in the Horizon Client. After implementing the workaround, future log-off attempts succeed, regardless of if you use the Horizon Client or the Windows log-off button.
  • After logging into a desktop using the Horizon Client, locking the desktop does not disable single sign-on
    The following functionality exists in Horizon 7, but not in Horizon Air Hybrid-Mode. When a you lock a remote Windows desktop session, the Horizon Client does not allow you to reconnect to that desktop, or any other desktop to which you are entitled, unless you reauthenticate. Therefore, implement the workaround that follows to ensure that single sign-on is disabled in Horizon Air Hybrid-Mode.
    Workaround: Inform users of the following best practice. Close the Horizon Client or disconnect from Horizon Air Hybrid-Mode when you leave the client desktop or mobile device unlocked.

Administration Issues

  • A "Device or resource busy" message appears when you attempt to remove a file share
    This issue can occur when you attempt to remove a file share soon after adding it because the file share import operation that was initiated when you added the file share has not finished.
    Workaround: If this issue occurs, attempt to remove the file share again after the file share import completes.
  • You cannot delete applications from the inventory
    To work with application assignments, you must import an AppStack from a file share. Afterward, applications in the AppStack appear on the Inventory page at Application > Inventory. You cannot delete these applications from the inventory page.
    Workaround: Contact VMware support to clear such applications from the inventory page.
  • When you publish an image, clones do not reflect the selected time zone
    Setting the time zone as you publish an image has no effect. The time zone of the client is configured in the clone and might not match the time zone selected when you publish the image.
    Workaround: Change the master time zone to the desired setting.
  • When you filter desktops for a specific operation, a message appears implying that the operation will be performed on non-selected desktops as well
    A misleading message appears after you perform the following steps.
    1. Create an assignment.
    2. Launch multiple desktops.
    3. Use filters to filter out specific connected desktops.
    4. Select an operation, such as the log-off operation, to be performed on the filtered desktops.
    The message indicates that the selected operation will be performed on the complete list of desktops in the assignment, instead of only on the desktops you specified.
    Workaround
    : Ignore the list and proceed with the operation, which will be performed only on the desktops you specified.
  • Attempts to create an assignment using special characters for the computer OU name might fail
    While creating an assignment, if you enter special characters in the Computer OU field and click Next, an error message appears with the following text. Unable to create assignment. The Computer OU entered in the Definition tab is invalid. Please enter a valid Computer OU and try again.
    Workaround: Do not use an OU name that contains special characters, such as #, %, &, !, @, (, and *. Instead, either choose a different OU name or rename the OU to remove special characters.
  • Using duplicate AppStack names can cause unpredictable behavior
    Creating two AppStacks with the same name might delay the availability of corresponding applications or cause  the applications to become  inaccessible.
    Workaround: Do not assign the same name to two or more AppStacks.
  • When you rename an image, an error message appears
    When you select Inventory > Images, rename an image, and click Save, the following error message appears.
    Unable to update name due to internal server error. Please try again.
    Regardless of the error message, the operation might succeed. In such a case, the image is renamed. If the operation fails, the image is not renamed.
    Workaround: Manually inspect the image to determine if it is renamed. If the renaming operation fails, most likely the name is already in use. Therefore, verify that you have a unique name for the image and attempt to rename the image again. For your information, the renaming operation completes in a few seconds.