Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Please reference the Guest Operating System Issues section of the following article for the most up-to-date information on this topic: AGENT_PENDING_EXPIRED - The pending session on machine has expired (90352) When users log in they receive the error: "The view agent reports that this desktop is currently logging off a previous session. Please try again." or "Session closed remotely (session close by login from an alternate session)" The Horizon Administrator console shows that the user is logged in to an existing session.The Horizon Administrator console shows the status of the virtual desktop as "Connected" though the user had already logged off the previous sessionComposer Operations (Refresh, Recompose or Rebalance) fail.Desktops are stuck deleting and the desktop shows a user session logged in.When connecting to the desktop console, you see dialogue boxes or displays logging offTypically resolved with a desktop power down / restart. Disclaimer : Several Microsoft Resources are linked below. VMware is not responsible for the reliability of any data, opinions, advice or statements made on third-party websites
An open application or process prevents the user session from logging off.When Windows logs off, it attempts to close all open user applications. If an application is either hung or presents a dialogue box requesting user input, the default behaviour of Windows is to prompt the user on how to handle the application. This behaviour can cause the user session to hang or prevent the desktop from logging off.
When users log off of their desktop sessions, unsaved data will be lost.
Follow best practices in terms of troubleshooting this machine on the Infrastructure level: Troubleshooting a virtual machine that has stopped responding (1007819) Note: Depending on the type of issue, some details on the cause may be present in the system or application events of the machine in question which might be accessible remotely or after recovery from a hang (o/s restart)If a cause is not evident from an analysis of existing logs, you can configure a dump capture to determine the cause of a future occurrence of a hang and analysis with a 3rd party Tool such as Windbg Debugging Tools for Windows - Windows drivers There are several options available to configure and capture a memory dump Suspending a virtual machine on ESX/ESXi to collect diagnostic information (2005831)Generate a kernel or complete crash dump (MS)Forcing a system crash from the keyboard (MS)
You can implement Registry Keys to hasten logoff such as AutoEndTasks – HungAppTimeout – WaitToKillAppTimeout – WaitToKillServiceTimeout. These can help as a temporary measure whilst the root cause of the behaviour is identified.Please reference OS documentation for your particular release.Ensure an Approriate Registry Backup has been taken Set AutoEndtasks to 1. If the user process does not cleanly shut down, this will tell Windows to close the process rather than prompt the user. Registry Path HKCU\Control Panel\DesktopRegistry NameAutoEndTasksRegistry TypeREG_SZRegistry Value1 Microsoft Reference: AutoEndTask WaitToKillAppTimeout determines how long in miliseconds Windows will wait before prompting the user or closing the process. Changing this value is optional, but should be used to complement AutoEndTask=1. It has a nominal impact as a isolated change.The default value is 20000 (20 seconds). Reduce as appropriate as your situation dictates. The below example shows a value of 2 seconds (2000) Registry Path HKLM\SYSTEM\CurrentControlSet\ControlRegistry NameWaitToKillAppTimeoutRegistry TypeREG_SZRegistry Value2000 Microsoft Reference: WaitToKillAppTimeout
For more information, see: https://technet.microsoft.com/en-us/library/cc978604.aspx https://technet.microsoft.com/en-us/library/cc978624.aspx 中文简体：Horizon View 桌面在注销时挂起，阻止 Composer 操作或用户登录