HTML Access Release Notes
HTML Access 3.4 | 4 June 2015
Last Updated: 4 June 2015
These release notes cover the following topics:
HTML Access makes it easy to access your Windows virtual desktop from an HTML 5-based browser. No need to install any software.
- Work the way you want to - Access View desktops from device platforms where no native client is available, or from any computer on which you do not
want to install software. You can also select HTML Access from a VMware Workspace Catalog.
- Simple connectivity - HTML Access is tightly integrated with VMware Horizon 6 for simple setup and connectivity.
Open a browser, enter a server URL, and log in to see a list of available View desktops.
- Secure from any location - At your desk or away from the office, your data is always secure. Enhanced certificate checking is
performed on the client. HTML Access also supports optional RADIUS and RSA SecurID authentication.
Top of Page
What's New in This Release
This release of HTML Access includes the following new features:
Top of Page
For HTML Access, both the user interface and the documentation are available in English, Japanese, French, German, Simplified Chinese,
Traditional Chinese, and Korean
Top of Page
Before You Begin
- To use HTML Access with Hosted Apps: A separate HTML Access installer (version 3.4) is available on the Horizon 6 version 6.1.1 download page. Download and run this installer after you install
or upgrade the other Horizon 6 components. Once you provide HTML Access version 3.4 to your users, they will not be able to connect to older View Agent desktops (version 6.1 or earlier) from their Web clients.
Take these steps:
- Install or upgrade your View Connection Server instances to version 6.1.1. Note: When you install View Connection Server version 6.1.1 interactively, an older version of HTML Access (version 2.6)
is installed. At this stage, hosted applications are not yet available through HTML Access. Users can continue to use HTML Access version 2.6 to connect to desktops running View Agent version 6.1.
- Install or upgrade View Agent to version 6.1.1 on all RDS hosts and VDI machines. Users of HTML Access version 2.6 can connect to desktops running View Agent version 6.1 or 6.1.1.
- From the Horizon 6 version 6.1.1 download page, download the HTML Access installer version 3.4 onto your View Connection Server instances and run the installer.
- For a list of the supported browsers, supported client operating systems, HTML Access system requirements, and installation instructions, see
Using HTML Access.
- The OpenSSL library is updated to version openssl-1.0.1m.
- Uninstalling View Connection Server does not remove the HTML Access component. HTML Access is a separate component that you must remove separately.
Top of Page
Resolved in HTML Access 3.4
Previously, when using HTML Access to connect to a desktop, some words in the pre-login message were cut off, depending on the size of the browser window. This issue has been resolved.
Resolved in HTML Access 2.5
Previously, sometimes the first time you logged in to a remote desktop and attempted to use the copy/paste feature, the Get Copied Text dialog box was empty. This issue has been resolved.
Top of Page
- HTML Access is not supported on iPads or other mobile devices for this release.
- HTML Access is no longer supported for accessing Windows XP and Windows Vista remote desktops.
The first time the first user attempts to connect to a remote application on an RDS host, the user might get an error message such as, "Unable to set up the application session for the display protocol. Please
contact your system administrator" or "The display protocol for this desktop is currently not available."
Workaround: Wait 15 seconds or longer and connect again. After the first user goes through this process, all users will be able to connect without receiving the error message.
The location-based printing feature does not work if you set your browser to use a proxy or if the client system is in a vLAN that is different from the vLAN in which the View environment is located.
Location-based printing policies that use the Mac Address or client name are not supported.
Sometimes the virtual printing feature and location-based printing feature are not able to display the correct list of printers in the Devices and Printers window of a remote, session-based desktop. This issue
can occur with desktops provided by Windows Server 2012 RDS hosts and Windows Server 2012 R2 RDS hosts. The printers shown within applications are correct, however.
Workaround: Log off the desktop running on the server and reconnect to it.
VMware recommends not using RDS Per Device Client Access Licenses (CALs) for HTML Access. If you do so, the licensing mechanism treats each browser as a device, and if cookies are cleared, the browser will use
Workaround: Use RDS Per User CALs for HTML Access.
If your client system uses a super high resolution monitor (such as 2560 x 1600), HTML Access fails to display the desktop.
Workaround: Lower the resolution on your monitor and connect. The resolution on the client monitor must be less than 2560 x 1600 if the remote desktop resolution is 1920 x 1200.
Sound playback quality is best on browsers that have Web Audio API support. Chrome, Safari, and Firefox 25 and later browsers have Web Audio API support. Browsers that do not have this support include Internet Explorer
(up to and including Internet Explorer 11) and Firefox 24 and earlier.
On Chrome browsers, if audio is playing and you switch to another tab in the browser, audio processing becomes intermittent. After you re-focus on the View desktop tab, audio might be out of sync with video
for a few seconds.
Workaround: Either refresh the page or pull the View desktop's tab out of the browser so that it has its own window.
The Linkclump Google Chrome extension interferes with proper right-click behavior. If you right-click something in the remote desktop, you might see the right click behave like a left-click-and-drag action.
Workaround: Either disable the extension or go into the Google Chrome browser's Linkclump Options page and in the Blacklist section, enter the address of the View Connection Server.
If you are using a Firefox browser and your HTML Access desktop session gets disconnected immediately upon connecting, verify that your Firefox browser proxy settings are configured correctly.
- Do not configure desktops to be suspended after users disconnect. This setting does not work correctly with HTML Access.
Top of Page