here's the catch 22 though, The published app is an accounting app, if they minimize it then the session becomes idle, if i log off the windows session with the condition of idle time, then the user session remains open/locked in the app and the only way to release the user session is by going into the admin module.
Jean-Paul Natola From: [email protected] To: [email protected] Subject: RE: [NTSysADM] Kill RDPINIT, published app Date: Mon, 7 Jul 2014 15:19:25 +0000 Group policy allows for direct control of RDP sessions. You can determine how long before idle sessions are disconnected, and if/when disconnected sessions are logged off. -- There are 10 kinds of people in the world... those who understand binary and those who don't. From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Monday, July 07, 2014 11:11 AM To: [email protected] Subject: RE: [NTSysADM] Kill RDPINIT, published app I don't think that would fly, considering Citrix isnt installed :) Jean-Paul Natola Date: Mon, 7 Jul 2014 15:57:21 +0100 Subject: Re: [NTSysADM] Kill RDPINIT, published app From: [email protected] To: [email protected] Dunno about the RDWeb end, but a logoff script to terminate it after a wait period might do what you need. Combine this with a tsdiscon command and you may make it slick. Sounds like a job for Citrix's LogoffCheckSysModules :-) On 7 July 2014 15:54, J- P <[email protected]> wrote: Hi all, I'm having issues where RDPINIT stays open after users logoff from published apps,thus leaving the session in a disconnected state. Is there something i can configure on the RDWeb server to address this? 2008r2 Thanks -- James Rankin --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
