The Terminal Services Team has posted another great article detailing more features of Microsoft Windows Server 208 Terminal Services. This time the article is about RemoteApp (seamless applications) session termination. The procedure for when to end a RemoteApp session involves two stages. In the first stage, heuristics are applied to determine whether the session needs to be disconnected. If the session needs to be disconnected, stage two is triggered. In stage two, Group Policy settings are used to decide if and when to log off the disconnected RemoteApp session. One thing to note here is that by default, RemoteApp sessions will remain in a disconnected state indefinitely. This where a new Group Policy setting comes in to play (the RemoteApp session logoff delay). This setting “…allows for the administrator to set the time delay for the logoff from a disconnected RemoteApp session. As it is much faster to connect to a disconnected session as opposed to starting a new session, you can use this policy setting to provide a faster startup times when a user launches a new RemoteApp on the same server. Based on server performance, an administrator must determine a time limit that provides the best user experience, while not overwhelming server resources by permitting these “no remote program running” RemoteApp sessions to remain in a disconnected state.

Continue at source…

Technorati : Longhorn, RemoteApp, Seamless, Session, Terminal Services, Windows Server 2008
Del.icio.us : Longhorn, RemoteApp, Seamless, Session, Terminal Services, Windows Server 2008
Ice Rocket : Longhorn, RemoteApp, Seamless, Session, Terminal Services, Windows Server 2008