Horizon Cloud with On-Premises Infrastructure 1.2 Release Notes
Horizon Cloud with On-Premises Infrastructure | 8 DEC 2016
Note: As of February 7, 2017, Horizon Cloud with On-Premises Infrastructure is made available as a deployment option with VMware Horizon® Cloud Service™. In the documentation for the 1.2 release, you might see references to older names.
These references will be updated in subsequent releases.
The product documentation that references previously released versions will continue to reflect the names they had
at the times they were released.
Release notes last updated on: 7 FEB 2017
Check for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
About Horizon Cloud with On-Premises Infrastructure
This section contains information about the Horizon Cloud with On-Premises Infrastructure deployment option of VMware Horizon Cloud Service.
For more information, see VMware Horizon Cloud Service Documentation.
Horizon Cloud with On-Premises Infrastructure 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 Cloud with On-Premises Infrastructure 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 Cloud with On-Premises Infrastructure 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 software.
New Horizon Cloud with On-Premises Infrastructure is made available as a deployment option with Horizon Cloud.
The latest release adds the following enhancements:
- Support for HTML Access for desktop
- VMware Identity Manager™ on-premises integration
- Enhanced Log collection for troubleshooting
- Integrated App Volumes management for deletion and management of AppStacks and writable volumes
- Demo mode, a read-only mode for administrators
- New Notifications page
- Windows 10 Anniversary guest operating system support
- Independent assignment for user writable volumes
- Support for application bundles to deliver groups of applications together
- Geographic expansion with new instance in Europe
Before You Begin
Take the following actions before you install or upgrade to this version of Horizon Cloud with On-Premises Infrastructure.
- Set-Up Prerequisites – Review the set-up prerequisites and suggested workflow before getting started with the installation of Horizon Cloud with On-Premises Infrastructure.
See the Customer Checklist PDF file that is available
from the Resources section of the Horizon Cloud with On-Premises Infrastructure Web page.
- Download – Download from My VMware the software necessary to deploy and use the service with your on-premises infrastructure. See the Horizon Cloud with On-Premises Infrastructure download page
- Internet Access – Note that authenticated proxy is not supported on the Horizon Air Link appliance to gain access to Horizon Cloud Services. If you require an authenticated proxy for the Horizon Air Link appliance to reach the Internet, whitelist the Horizon Air Link with the proxy such that it does not require authentication.
Knowledge of the following facts is useful before using Horizon Cloud with On-Premises Infrastructure.
- Browser Experience – If you experience issues with the Safari, Edge, or Internet Explorer 11 browsers, use another browser, such as Firefox or Chrome, or another version of Internet Explorer and confirm if the issue persists.
- Text Input – Follow these guidelines when entering characters.
- Use standard ASCII characters only in path names, OVA file names, and user names and passwords.
- Do not use commas in user passwords.
The resolved issues in this release of Horizon Cloud with On-Premises Infrastructure are as follows:
End User Issues
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.
This issue is resolved.
- When you delete a mapped and dedicated virtual machine, the user loses access to the pool
After you map a user directly to a dedicated virtual machine pool, as opposed to when you map the user indirectly with a group mapping, when the user logs in, the system assigns a specific virtual machine to the respective username. If you later delete the virtual machine, the user can no longer see the pool, despite the fact that the user still has an individual mapping.
This issue is resolved.
- Once the applications in a file share are assigned and launched, you cannot remove the file share
After you assign applications in a file share to users and the users launch their desktops, which include the assigned applications, you cannot remove the file share. Therefore, when you select Settings > Locations > File Share and attempt to remove the file share, the attempt fails. Unassigning the applications does not enable you to remove the file share.
This issue is resolved.
- 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.
This issue is resolved.
The Known Issues for this release of Horizon Cloud with On-Premises Infrastructure are grouped as follows:
Attempting to change the image name while creating an image in the Administration Console fails
In the Horizon Air Hybrid-Mode Administration Console, when you select Inventory > Images and click New to create a new image, edits to the auto-populated Image Name text box do not take effect.
Workaround: If you want to rename an image, after you finish creating the image, select Inventory > Images, select the image, and click Rename. You can then provide a new name for the image.
The scroll feature does not work on the AppStacks screen until you refresh the page
The AppStacks screen, which is accessible by selecting Settings > Storage Management, does not display a vertical scroll bar when you first access the page, preventing you from scrolling. This issue becomes apparent when the number of AppStacks extends beyond the bottom of the page. Using the browser scroll bar does not resolve the issue.
Workaround: Click the refresh icon on the AppStacks page.
Previous Known Issues
This section lists previously reported Horizon Air Hybrid-Mode 1.x known issues that might continue to exist in the product.
Set Up and Configuration
- 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.
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.
- 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
- After you push an image update to a desktop assignment, the assignment might display the wrong image version
Updating an image and pushing the changes to an assignment updates the desktops based on the new image. Users who are logged into desktops at the time are skipped. After those users log out, the image version automatically updates. However, when you check the image version, for example by clicking Assign, clicking the assignment, and clicking Desktops, the image version on the Desktops page continues to display the old image version.
Workaround: Ignore the image version that appears on the Desktops page. The desktop is created from the correct image.
- 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.
- 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.
- 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
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.