At a command prompt, type gpupdate and press ENTER to force the policy to refresh immediately on the local computer.Īfter the policy setting is enabled, disconnected RemoteApp sessions will be logged off after the configured time delay.In the RemoteApp session logoff delay list, select the desired time for logoff delay, and then click OK.In the right pane of the Local Group Policy Editor, double-click Set time limit for logoff of RemoteApp sessions.Locate the appropriate node under Computer Configuration or User Configuration as shown above. To do this, click Start, click Run, type gpedit.msc, and then click OK. Log on to the terminal server as an administrator.To enable and configure the policy setting: User Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits.Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits.This setting is located in Group Policy under both Computer Configuration and User Configuration: 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. "and Michael Harris on 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 "Based on posts by Alex Angelopoulos on & _ "Written by Rob van der Woude" & vbCrLf & _ " (the local computer)." & vbCrLf & vbCrLf & _ " (without leading backslashes) default is " & _ " is the name of the computer to be logged off" & vbCrLf & _ VbCrLf & vbCrLf & "Usage: CSCRIPT LOGOFF.VBS " & _ "Logoff the current user of any WMI enabled computer on the network." & _ Msg = vbCrLf & "Logoff.vbs, Version 1.00" & vbCrLf & _ Set OpSysSet = GetObject("winmgmts://" & strComputer & "/root/cimv2").ExecQuery("select * from Win32_OperatingSystem where Primary=true") ' 5 works OK in Windows 2000, but may result in power off in XP ' logoff = 0 (no forced close of applications) or 5 (forced) ' Define some constants that can be used in this script ' Default is local computer if none specified ' Adapted from posts by Alex Angelopoulos on ' and Michael Harris on ' Logoff current user on any WMI enabled computer on the network Not particularly elegant (yes, yes, ugly as hell), but good enough for now. I decided to store it as a string inside the tool and make it write it to disk, execute it and delete it. Finally found out this script in this page:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |