5.0.1 Release Notes

The following enhancements are incorporated into this release.

Mobile Client Enhancements

FH Web 5.0.1 iOS and Android clients include the following enhancements:

• New user interface
• Improved application usability
• Task management

The FH Web 5.0.1 mobile clients include the following gesture changes:

• Dragging a single finger produces a left button drag in the remote application
• Dragging three fingers pans the client’s view

Automatic Host Update

Administrators can configure FH Web hosts to automatically download and install FH Web updates. Administrators can control the types of updates that are automatically installed. FH Web supports Mandatory, Recommended, and Optional host updates.

Improved Windows Compatibility

FH Web 5.0.1 contains a number of improvements that reduce the risk of incompatibilities with Windows Updates.

The following issues were successfully resolved this release.

• Printing fails, or the default printer cannot be found, when Symantec Endpoint Protection is installed on the host.
• Client files are not removed on uninstall if client was upgraded from version 4.8.2.
• Intermittently, processes running within a session on a version 5.0.1 host cannot be terminated.
• When the Program Window is resized so its height is small, and is then minimized, it fails to restore when it is activated from the task bar.
• Cursor intermittently disappears in the Mac Client when the host version is 5.0.1.
• Dllhost.exe processes remain running on the host.
• Minimize, Maximize, and Close buttons are very small when DPI scaling is disabled.
• The cursor changes to the arrow cursor when characters are typed in Notepad.
• Applications fail to activate when they are selected on the Mac client’s Applications menu.
• A specific application’s dialog box is not visible in version 5.0.1.
• When DPI scaling is active in a session running on a Windows Server 2012 R2 host, the text in the logon dialog and the program window is not scaled correctly.
• The host runs out of memory intermittently due to a session starting with a large, invalid display size.
• The client fails to update its display after a new folder is created in a file dialog.
• Client USB drives are not accessible.

The following known issues will be resolved in a future release.

• The first time a user connects to a host, the text of menu items may not display on a secondary monitor when the secondary monitor is to the left of the primary monitor.
• On Windows 8.1 and Windows Server 2012 R2, the desktop is painted black if the client does not support 32-bit color.
• Artifacts from an application’s title bar may appear in the lower-left corner of the client’s desktop when an application is minimized and restored.
• An SSL security warning dialog may be displayed when users connect from a Mac to a host that is configured to use SSL.
• When the FH Web host is Windows 8.1 or Windows Server 2012 R2 and is run on VMWare, the mouse does not work in the console session while the Windows desktop is running in a FH Web session.
• The FH Web installer intermittently hangs on Windows 8 and Windows Server 2012 because of an issue with the Microsoft tiworker.exe process. To work around this issue, end the tiworker.exe process and restart the FH Web installer.
• The FH Web Client cannot be run in Apple Safari on Windows.
• Encrypted PDF documents cannot be printed with the Universal Printer Driver.
• Windows Server 2012 Essentials is not supported. Sessions will not start on this operating system.
• Avast Free Home Antivirus is not supported on 64-bit hosts.
• Bitdefender Antivirus is not supported on 32-bit hosts.
• Radmin is not supported.
• On Mac OS X 10.8 Mountain Lion, users need to disable Gatekeeper to install the native Mac OS X client.
• The automatic client update feature is not supported if the client modifies the client installer to install the client in a location other than the default location. To work around this issue, install the client in the default client location.
• When Integrated Windows Authentication is enabled, client printers may be listed twice in Notepad and WordPad.
• Users must disable the firewall from Total Defense Anti-Virus before a client is able to connect to a FH Web host.
• Users must add the FH Web Application Publishing service (aps.exe) to the exclusion list for Vipre Antivirus before a client is able to connect to a FH Web host.
• When using multiple monitors and connecting to hosts running Windows 8, 8.1, or Windows Server 2012 or 2012 R2, display issues might occur when moving windows across the monitors and off-screen.
• The client is unable to connect to a FH Web host running Windows 8 on port 491 when McAfee Anti-Virus is installed. To resolve this, open a FH Web port in the McAfee Firewall. For more information, see http://service.mcafee.com/FAQDocument.aspx?id=TS100887.
• Help files may fail to open when Integrated Windows Authentication is used without server-side password caching.
• Object Linking and Embedding (OLE) operations may fail when Integrated Windows Authentication is used without server-side password caching.

• Cannot add printers in the Printers applet when the Universal Printer Driver option is not enabled and there is no printer driver installed on the host that has the exact same name as the client printer driver. To work around this issue, do one of the following.

  • Add an entry to the MappedPrinterDrivers.xml file that maps the name of the driver on the client to the name of a driver on the server.
  • Enable the Universal Printer Driver option in the Cluster Manager.
• Type 4 printer drivers are not supported, and the Add option in the Printers applet will fail when a Type 4 printer driver is specified. To work around this issue, specify a compatible Type 3 printer driver.

• When the web server on the host is IIS, and IIS is configured to only serve documents with file extensions that are registered MIME types, files with the following extensions may not download: .deb, .crx, .dmg, .xpi.

  Example: Firefox may display the following error message when a user attempts to install the plug-in: Not a valid install package.

  To resolve this issue, define a MIME type for the needed extensions, as described in Microsoft Knowledge Base article 326965 (http://support.microsoft.com/kb/326965). For the Chrome Extension, specify the MIME type as application/gg-chrome.