Win10IoT Add-On (VMware Horizon View Client)
VERSION  : 2406
REVISION : A
PASS     : 1

DESCRIPTION :
VMware Horizon Clients allows you to connect to your VMware Horizon virtual desktop from your HP Thin Client giving you secured access to virtualized applications and desktops.

This package installs the VMware Client 2406 on supported thin client models running the 64bit Win10 IoT.

CONTENTS :
  VMwareHorizonClient-2406.exe - Install package that installs VMware Horizon Client.
  VMwareHorizonClient-2406.txt - This file.

https://docs.omnissa.com/bundle/horizon-client-windows-RNV2406/page/HorizonClientWindows-ReleaseNotes.html

ENHANCEMENTS/FIXES: 
- Improved experience with IME usage in RDS applications
- Organize remote applications using folders
- Enhancement to Log In as Current User
- Updated OS support


KNOWN ISSUES:
- Enable Relative Mouse feature does not work on touch-enabled screen
    If you use a touch-enabled screen on your client system to work in a remote desktop, do not use the Enable Relative Mouse feature. This feature provides improved mouse performance for 3D and CAD applications, but for touch-enabled screens and tablets, the mouse coordinates are not translated properly, even in 3D and CAD applications.
    Workaround : None.

- Tax issues for IBM Credit Memos
    N/A

- Remote application launches and displays a black area after legal notice confirmation
    After confirming the legal notice, the remote application launches and displays a black area in the UI.
    Workaround: Disconnect then reconnect the remote application.

- Keylogger blocking does not work in nested sessions
    When users attempt to open a nested session in which both the host and guest desktops have keylogger blocking enabled and all required drivers installed, the connection is denied.
    Workaround: None.

- When a remote desktop is reconnected, Powermic Speechmic does not work with DMO 2022.2
    When a remote desktop is reconnected after being disconnected, Powermic device does not work with dictation on DMO 2022.2. This happens when using a USB split and RTAV solution.
    Workaround: Use Nuance extension to redirect Powermic devices on the remote desktop.

- Horizon Client for Windows quits when launching a remote desktop
    Horizon Client for Windows might quit unexpectedly when launching a remote desktop with multiple monitors at a high resolution.
    Workaround : Check the supported multiple monitor configurations in the documentation to resolve this issue. If you still encounter this issue, consider the following workarounds:
        - Configure your monitor layout so that it’s not very wide or very tall (for example, use a tile/matrix layout instead of using single row/column of monitors).
        - Try not to launch multiple desktops with multiple monitors in one client instance, but start a new client instance to launch another remote desktop.
        - Use the Omnissa Horizon Blast protocol to start the remote desktop.

- Limited context menu with Browser Redirection feature
    With the Browser Redirection feature, the context menu options on right click are limited to open link in new tab, open link in new window, back, and forward.
    Workaround: None.

- Incorrect event log report
    With the clipboard audit feature, the event log reports one byte more than the actual length of the data that was copied from the agent machine to the client machine. For example, if you copy 10 bytes of data from a remote desktop to the client machine, the event log reports “XXX copy 11 bytes CPFORMAT_TEXT data from Horizon Agent to Horizon Client XXX with clipboard.” Also, if “\r\n” is in the copied text, the event log records only the length of “\r.” For example, if you copy the following text, the audit message records the length as 12 bytes:
      aaa
      bbb
      ccc
    Workaround: None.

SPACE REQUIREMENTS :
  This add-on requires uncompressed free space on the flash memory (Drive C:)
  and uncompressed free space in the temporary folder. These space requirements
  must be met in order to successfully deploy this add-on.

  1) Space required on the flash memory for installation    : 60 MB
  2) Space required on the flash memory after installation :  40 MB (with NTFS Compression)
  3) Space required in the temporary folder for installation : 160.00 or better MB

  To ensure that the temporary folder always has the required amount of free space
  for installation, HP recommends that the %TEMP% and %TMP% variables be
  temporarily re-defined to a network share on the deployment server, and that the
  setup program be executed from the deployment server. Otherwise, the add-on may fail
  to deploy correctly.


PREREQUISITES :
For the Windows operating systems that this release of Horizon Client for Windows supports, see the Horizon Client for Windows Guide.

Horizon Client for Windows is supported with the latest maintenance release of the following deployment types:

  Omnissa Horizon 8 version 2006 and later

  Omnissa Horizon Cloud Service - Next-Gen

  Horizon Cloud in Microsoft Azure

To use Horizon Client in FIPS mode, you must use Connection Server version 2309 or later; if using Unified Access Gateway, you must also use Unified Access Gateway 2309 or later. For more information, see Omnissa Knowledge Base (KB) article 95144.

To install Horizon Client for Windows, download the installer from the Horizon Clients download page.

For installation instructions, see the Horizon Client for Windows Guide.

For information about the features that are supported in nested mode, see Omnissa Knowledge Base article 67248, “Horizon Guidelines for Nested Mode.”

Note: Install command for HPDM: "set TEMP=C:\temp & set TMP=C:\temp & VMwareHorizonClient-2406.exe /s"

Copyright (c) 2024 HP Development Company, L.P.