Download Vdi Horizon Client

0 views

Skip to first unread message

Jeana Rodia

unread,

Aug 3, 2024, 4:25:46 PM8/3/24

to leosluclapent

I am running Big IP version 12.1.0 with APM and Horizon View 7.0.1. Currently attempting setup with the f5.vmware_view.v1.5.1 iapp template. The feature we really want to implement is using smartcard authentication with SAML 2.0 through the horizon client. Both the View server and F5 have been configured according to the companion guide for the iapp. The horizon client will prompt for a pin and then after a second or two display "Authentication Failure." APM logs consistently show the access policy failing at the cert inspection step. No SAML traffic appears to take place.

If I attempt the same exact connection through a regular web browser via HTML 5, I can authenticate to the webtop where the authentication fails to the back end (the documentation says that's what should happen and that manual login has to occur from the webtop). The main thing is the APM log looks great. SAML authentication is seen for the browser connection the cert inspection from the same smartcard passes where it fails on connections from the Horizon client. I could really use some guidance on this.

As the question states I have a rather frustrating issue where my PCoIP zero client will not connect to the assigned virtual machine in the desktop pool in Horizon 7 it attempts to connect and then fails with the following error;

Your last commen helps, if this is a dedicated machine to a single user, can you confirm that no admins are connected to it using RDP, you can see any connections under sessions in horizon view admin page

VMware Horizon Client for Windows makes it easy to access your remote desktops and published applications with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).

2572160: When using Horizon Client with Media Teams Optimization enabled, if the client wakes from hibernation during a Teams call, the Teams call continues, but sometimes self preview video in the remote desktop, and the remote peer's incoming video, freezes.

In an IPv6 environment, if you configure IP address mapping for location-based printing, users might encounter a problem accessing the printer because the client can have multiple IPv6 addresses. Anytime the client connects, it can use any one of the addresses.

Workaround: Use the location-based printing group policy setting IP Range to include the multiple addresses. However, the printing problem might still occur because the client might use a temporary address, which is not in the specified range.

If you have multiple monitors with different screen resolutions and expand Horizon Client to all monitors and then select the Enable Relative Mouse feature, occasionally, the mouse pointer might not be able to move downward beyond a certain position.

When a user connects to a desktop using PCoIP shortly after the desktop is powered on, autofit of the desktop window might not work. This issue happens most often if the desktop or network is under stress shortly after power-on (to start multiple applications or to map network drives, for example).

If you install Horizon Agent and then install Horizon Client on the same Windows machine (a nested mode installation), and you later uninstall Horizon Agent, the client's "log in as current user" function is lost after Horizon Agent is uninstalled. This problem occurs because the wsnotify.dll file is removed after Horizon Agent is uninstalled.

If you connect multiple USB devices to the client system, select Automatically connect at startup in Horizon Client, and then connect, disconnect, and quickly reconnect to a remote desktop, not all of the USB devices are redirected to the remote desktop after you reconnect.

Workaround: Wait for the USB devices to be redirected back to the client machine (for example, wait for the devices to appear in the device manager) and then reconnect to the remote deskop. Alternatively, you can manually redirect any unredirected USB devices to the remote desktop.

After you disconnect and reconnect multiple remote desktops, you see an error message that states that an error occurred when connecting a USB device to your remote desktop. This problem typically occurs when multiple USB devices are connected to the client machine and you select Automatically connect at startup in Horizon Client.

If you use the RDP protocol to connect to a published desktop from a physical machine, and then you try to connect to the same published desktop from a zero client, the RDP session ends on the physical machine and the zero client cannot connect.

Workaround: Relaunch the same desktop pool with RDP from the physical machine, select Options > Disconnect and logoff in the launched RDP session, and then reconnect to the same desktop pool from the zero client.

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"

I see clipboard for copy/pasting from host client machine to VM works but not vice versa. Is there a way to move things such as text or entire files from the VM to the host client? Can a drive from the host client be mounted as an alternative to using the clipboard to move something from the VM to the host?

Connection to remote machine is fine, remote apps open fine, however app menus and right-click context menus open and suddenly disappear. It looks like the menus open fine, but something is stealing the focus. This happens in Chrome, MS Office Apps, the Windows File-Explorer, etc. The only app that does not have this behavior is MS Teams.
This happens only when opening the app using Horizon, if I open them using the browser client, everything is OK.

It looks like the setup of the display at the beginning of the session has trouble setting up. I added the following registry key to the machine / if this is instant clones you will need to add to the golden image and take new snapshot and push to the pool:

Unfortunately, the registry modification does not work for us. We have also only experienced this problem with the Linux Horizon client on Igel OS. We are on the latest versions of the connection servers and clients that are supported according to the documentation.

Which version? Please be more precise. And what issue?
No need to set any registry keys with 16.4. If there are still issues with primary display you should open a support ticket for further investigation as this was fixed in 16.4.

Please check what is serving the primary display. DXDIAG can be used to see what is in use.
Try to uninstall vSGA driver from VMWare to force the NV display as primary.
Anyways, please open a support ticket as this behavior should have been changed/solved with 16.4

Installing Horizon Client From the Command Line at VMware Docs has instructions on how to install the Horizon Client silently. Common methods for installing the client silently include: SCCM and Active Directory Group Policy Computer Startup Script.

VMware Fling View Auto-Connection Utility: The View Auto-Connection Utility allows you to connect the VMware View Client automatically into a View desktop or an application pool when the system starts up.

In the Horizon Client, each desktop/app icon has a star icon you can click, or right-click an icon and Mark as Favorite. Favorites are stored in the LDAP database on the Horizon Connection Server.

When you connect to a Horizon Connection Server, and if the certificate is not trusted or valid, then the user is prompted to accept the certificate. You can disable this prompt for any client machine that can be controlled using group policy.

When you install the Horizon Agent component, be sure to select the scanner redirection feature if you want to use it; it is disabled by default. If you are installing the feature onto a server-based OS (Windows Server 2008 R2 or Windows Server 2012 R2) for either VDI desktops or RDSH desktops or applications, then be sure that the Desktop Experience feature (a Microsoft operating system feature) is installed on the server OS first. (This is a prerequisite for installing scanners in a server-based OS.)

After a user makes a connection from a compatible Windows Horizon Client to the new Horizon Agent, a new tool-tray application icon appears. The user clicks the icon to reveal the compatible image acquisition devices available for scanning.

Scanner Redirection Preferences, available by clicking Preferences from the tool-tray icon, allows further configuration of the scanning process, for example, adjusting the default compression applied to the scanning. This can greatly reduce the bandwidth needed to transmit the image (the compression is applied on the client side before the image is transmitted to the guest), but, of course, the more an image is compressed, the lower the image quality. In addition, in the Scanner Redirection Preferences, options are available to adjust the default image capture device (for example, automatic mode, last-used, or an absolute specified device).

These preferences can also be adjusted by way of Group Policy options in the guest OS. A new GPO file (available in the Horizon with View GPO Bundle) allows this configuration. See Configuring Scanner Redirection in Setting Up Desktop and Application Pools in View for more information

Horizon 7.7 and newer with Horizon Client 4.10 and newer have a new VMware Integrated Printing (aka VMware Advanced Printing) feature that replaces the older ThinPrint technology. ThinPrint is no longer available in Horizon Agent 2006 and newer.