How to set Remote desktop session host to close an application gracefully on disconnected session

Toutes les réponses

• lundi 7 mai 2012 09:45

  Modérateur

   

   
  

  0

  Hi,

  You can configure RDS to terminate sessions by seession time limit options thru GPO.
  Terminal Services RemoteApp™ Session Termination Logic:http://blogs.msdn.com/b/rds/archive/2007/09/28/terminal-services-remoteapp-session-termination-logic.aspx

  Regards,
  Clarence
  Forum Support
  Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contacttnmff@microsoft.com.

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  
  

  • Modifié Clarence ZhangModerator lundi 7 mai 2012 09:45
  •  
  • Réponse
  • Citation

   
• lundi 7 mai 2012 14:36

   

   
  

  0

  Hi Clarence

  I am forcefully disconnecting IDLE users and the problem is windows 2008 is not ending the application properly it seems to kill the app. While in 2003 in the same scenario it closes down and exits the application.

  cheers

  Neil

  • Réponse
  • Citation

   
• mardi 8 mai 2012 07:55

  Modérateur

   

   
  

  0

  Hi,

  Did you make the application available to clients thru RemoteAPP or Remote desktop?Did you set the new policy—Set time limit for logoff of RemoteApp sessions?
  If normal, the application process will be ended when the user session has been logged off.
  
  Regards,

  Clarence

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Marqué comme réponse Clarence ZhangModerator mercredi 16 mai 2012 08:23
  • Non marqué comme réponse Neil Maxwell jeudi 17 mai 2012 20:10
  •  
  • Réponse
  • Citation

   
• mardi 8 mai 2012 19:51

   

   
  

  0
  I had a similar problem with a desktop application that I was running as a remote web application.  What I found was that I needed to configure the sessions so that they ended after disconnection.  Specifically, in Server Manager, in the Remote Desktop Services role, in the RD Session Host Configuration feature, I right clicked on the Connection in the Connections pane and selected Properties.  Once the properties dialog comes up, click on the Sessions tab and review the settings there.  I set an Active Session Limit of 12 hours, an Idle session limit of 6 hours and checked the Override user settings check box and then specified to end a disconnected session after 1 minute.  The application I was working with is written using VBA in Access and the effect of these settings were to remove all msaccess.exe instances from the process list for that logged on user 1 minute after a user disconnected from the remote web application.  The access .ldb file got cleaned up properly to reflect that that user was no longer using a concurrent license seat in our software.  This worked for me but your mileage may vary depending on the licensing structures and the particularities of the program you are using.  I did also write a .NET desktop app that I could run to determine which users were logged into the app and then end their specific process.  That also resolved the locked license issue but wound up being unnecessary to deploy because the measures I outlined first worked perfectly for my specific situation.  I'm just mentioning the .net desktop app in case you need to pursue that option for some reason.

  ---

  What monstrosities would walk the earth were men's faces as unfinished as their minds. Victor Hugo

  • Réponse
  • Citation

   
• mardi 15 mai 2012 06:54

  Modérateur

   

   
  

  0
  Hi,
  
  I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help.
  
  Regards,
  Clarence
  Forum Support
  Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contacttnmff@microsoft.com.

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Réponse
  • Citation

   
• jeudi 17 mai 2012 20:18

   

   
  

  0

  Sorry, been focused on sorting out Printing issues on our remote desktop servers, now that that is all sorted I can focus on this one.

  Clarence: I am not using remote app at this stage, however I would like to go that route. I haven't set the policy that you mention as I am not using remote app. In the mean time I have taken off all the time limits and noticed that some users seem to not exit the app, but just click on start and log off and this should close the app correctly but it doesn't.

  I cant help but think that there is a group policy or registry setting that says something like wait for application to exit before logging off, it may not be related to remote desktop services, like if you try and shutdown a windows 7 machine and it tries to wait for the programs to close, I need to try and set server 2008r2 to do exactly that.

  Thanks for the input so far.

  • Réponse
  • Citation