

To resolve this issue, set the Session Timeout in View Agent Direct-Connection Plug-In (VADC) configuration settings. This is occurring because the system is powered off.Īfter powering on all unmanaged View agents running on physical computers, the issue should be resolved. Desktop Session Timeout is controlled by the registry key and has a default value of 600 minutes (10 hours). When this is enabled, you can add Client Computer Accounts to an AD Group and entitle the published application. For tunnelDestinationUrl, enter the URL used by Horizon clients to establish the Horizon Tunnel session to this Unified Access Gateway appliance, such as 3. Horizon 7.3 adds a checkbox named Client Restrictions. The following settings are used by the Horizon client when the user launches an application or desktop, based on the respective protocol. Horizon 7.5 and newer lets you put the shortcut on the endpoint’s desktop. See Create Shortcuts for a Desktop Pool at VMware Docs. The apparent delay “Authenticating” or “Logging In” is caused by a Wake On LAN packet being sent to an unmanaged physical workstation that has the VMware View Agent installed. This applies to Horizon Client 4.6 and newer. T16:07:34.296-06:00 INFO (1064-17F0) UnManagedMachineInformation Could not wake up PM within timeout The Fix T16:07:34.296-06:00 INFO (1064-17F0) UnManagedMachineInformation wait ended for startup update, returning false

In the VDM debug logs, you may find something similar to below: T16:07:44.971-06:00 INFO (1064-181C) UnManagedMachineInformation Wake-on-LAN packet sent to machine Originally, I thought this issue was related to 2FA and/or RADIUS, however after disabling both, the issue was still present. This occurs both with standard authentication, as well as 2FA/MFA/RADIUS authentication. This will either timeout, or eventually (after numerous minutes) finally load. If using the HTML client, it would get stuck on “Logging in”. I noticed after upgrading to VMware Horizon View 7.8 and VMware Unified Access Gateway 3.5, when attempting to log in to a VMware Horizon View Connection Server via the Horizon Client, I would get stuck on “Authenticating”.
