HTML Access Release Notes

|

HTML Access 4.0 | 22 March 2016

Last Updated: 22 March 2016

These release notes cover the following topics:

Key Features

HTML Access makes it easy to access your Horizon virtual desktops (Windows and Linux) and applications from an HTML5-based browser. No need to install any software.

  • Work the way you want to - Access View desktops and applications 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 7 for simple setup and connectivity. Open a browser, enter a server URL, and log in to see a list of available View desktops and applications.
  • 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

New Features in Horizon Client 4.0

  • Support for the latest browsers
  • Support for mobile devices
    Safari on iOS 8 and iOS 9 is supported.
  • Improved security for Chrome and Safari
    For improved security, on Chrome and Safari, HTML Access does not allow the use of an IP address to connect to the View Connection Server. You must use a fully qualified domain name.

New Features in Horizon Client 3.5

  • Support for the latest browsers
  • Windows 10 remote desktop support
    You can use HTML Access to connect to Windows 10 remote desktops.
  • 4K display support
    You can use a single 4K display when accessing a remote desktop or application. Consult the GPU vendor's web site or the View Installation guide for support in vDGA and vGPU modes.
  • Access Point integration
    HTML Access can use the new Access Point appliance instead of a security server to connect to a View Connection Server instance. You can set up either Access Point or Security Server or both in the same environment.
  • Support for keyboard-only access
    You can interact with the HTML Access client (but not the side bar) using only the keyboard.

Top of Page

Internationalization

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

  • For a list of the supported browsers, supported client operating systems, HTML Access system requirements, and installation instructions, see Using HTML Access.
  • HTML Access 4.0 supports View Agent 7.0 and later.
  • With HTML Access 4.0 and Horizon 7.0, if you connect to Connection Server through a load balancer or a gateway such as F5 or Access Point, you must first configure a security setting in View. See the section "Origin Checking" in the see View Security document.

Top of Page

Resolved Issues

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.

Top of Page

Known Issues

  • On iOS Safari, if you connect to a remote desktop and play audio or video on the desktop, and switch to playing audio or video with a native application without disconnecting from Connection Server, and switch back to the remote desktop on Safari, audio will no longer work.
    Workaround: Disconnect or logoff from Connection Server and connect to the desktop again.
  • HTML Access is supported on iOS devices but not on Android and other mobile devices for this release.
  • When you use any version of HTML Access with Firefox 40, 41, or 42, audio does not work. Note that these versions of Firefox are not supported by any version of HTML Access.
    Workaround: Use a supported version of Firefox.
  • 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 another license.
    Workaround: Use RDS Per User CALs for HTML Access.
  • 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.
  • Connecting to a desktop or application fails if Blast Secure Gateway (BSG) is enabled on both the Access Point server and the View Connection Server.
    Workaround: Disable BSG on the View Connection Server.
  • In Access Point, if you set the View Edge Setting "blastEnabled" to False, you will not be able to access remote desktops and applications through HTML Access. Generally, because Access Point is deployed in a DMZ, the "blastEnabled" option is set to True, and this issue does not occur.
    Workaround: In Access Point, if you set "blastEnabled" to False and also use HTML Access, you must also set the "proxyPattern" option to "/|/portal(.*)".
  • If you try to connect to a VADC (View Agent Direct Connection) desktop or application using Internet Explorer, Safari, or Firefox, and you click Cancel on the login page, the login button will be disabled, although you can still enter a user name and password. If you click Cancel again, the login button will be enabled, but logging in with a valid user name and password will fail and you will be presented with the login page again.
  • When you connect to a Linux desktop with the Japanese keyboard, the keyboard mapping might be incorrect. For example, the key positions \| and \_ will be incorrect.
    Workaround: Keep the client input language as Japanese and switch the desktop input language to English for the two key positions \| and \_ only. Keep the desktop input language as Japanese and switch the client input language to English for all other key positions.
  • When connecting to a Linux desktop, some keyboard input does not work. For example, (1) with English keyboard, the * key on the numeric keypad is display as 8, (2) with English keyboard, the + key on the numeric keypad is displayed as =, and (3) with non-English IME on both client and desktop, some non-English keys are not displayed correctly.
    Workaround: For issues #1 and #2, use the typewriter keys * and + in the main keyboard area instead of the numeric keypad. For issue #3, set English IME on the HTML Access client and non-English IME on the desktop.

Top of Page