![]() ![]() User Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits. ![]() Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits. ![]() This setting is located in Group Policy under both Computer Configuration and User Configuration: #MOCHA RDP LITE HOST HAS CLOSED THE SESSION WINDOWS#This behavior can be modified by a new Group Policy setting introduced in Windows Server 2008, Set time limit for logoff of RemoteApp sessions. When a new RemoteApp is launched the session is reconnected instead of incurring the overhead of starting a new one.īy default disconnected RemoteApp sessions will remain in a disconnected state indefinitely. Leaving the session in a disconnected state allows subsequent RemoteApps to launch much more quickly. If another application or system tray icon isn't launched within that time, the RDP session is disconnected. This allows time for the user to launch another application, and for applications to display final messages or perform other closing tasks. When all active application windows and all user-launched notification area icons are closed, the session remains active for 20 more seconds. Additionally, any notification area (system tray) icons that are launched by the user will also run in the same session. Any subsequent RemoteApps that are launched from the same client before the session is logged off will run in the same session. When a user launches a Remote Desktop Services or Terminal Services RemoteApp, a Remote Desktop session is created in which the application runs. This article provides help to solve an issue where RemoteApp sessions are disconnected when all RemoteApp windows and user-launched notification area icons are closed.Īpplies to: Windows Server 2012 R2 Original KB number: 2345390 Summary ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |