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. 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. 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 VMware Horizon You can connect to your desktop and applications by using the VMware Horizon Client or through the browser. 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”.
0 kommentar(er)
