locked
Disconnected terminal services sessions RRS feed

  • Question

  • hi all, is there a way to disconnect user sessions that have been idle for a long period of time, say longer then 5 hours?  there are often a dozen or so on our server and they eat up valuable resources.  im assuming that theres a group policy setting somewhere that specifies this?

    Thanks,

    Rhys.
    Tuesday, February 23, 2010 4:10 PM

Answers

  • Hi Rhys,

    There are several different ways of doing this.

    The most common is through the Group Policy. In the group policy linked to your Terminal Servers you have to find this setting:

    Computer Configuration > Policies > Windows Components > Terminal Server > Session Time Limits > Set Time limit for disconnected sessions (once you have done this do not forget to rum gpupdate /force)

    One more way is to set the limits in the: Terminal Services Configuration > double click RDP-Tcp > Sessions tab

    Another way is to set the limits in the Properties of particular User's account in ADUC.


    сила в справедливости
    • Marked as answer by RhysDavies Tuesday, February 23, 2010 4:30 PM
    Tuesday, February 23, 2010 4:22 PM
  • Sure are. You can do this in tow places: Group POlicy or TS/ RD Configuration tool:

    Here are the policies:

    Two places (either user or computer config):

         Computer Configuration| Admin Templates | Windows Components | Remote Desktop Services | Remote Desktop Session Host | Session Time Limits

         User Configuration | Admin Templates | Windows Components | Remote Desktop Services | Remote Desktop Session Host | Session Time Limits

    You can also acomplish this on a per server basis in TS Config (RDS Config), double click RDP-Tcp, navigate to the Sessions tab.

    And of course, in R2 this can also be done programatically via Powershell.


    Hope this helps,

    Kristin L. Griffin

    Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) 

    I finally started my blog: blog.kristinlgriffin.com
    Tuesday, February 23, 2010 4:25 PM

All replies

  • Hi Rhys,

    There are several different ways of doing this.

    The most common is through the Group Policy. In the group policy linked to your Terminal Servers you have to find this setting:

    Computer Configuration > Policies > Windows Components > Terminal Server > Session Time Limits > Set Time limit for disconnected sessions (once you have done this do not forget to rum gpupdate /force)

    One more way is to set the limits in the: Terminal Services Configuration > double click RDP-Tcp > Sessions tab

    Another way is to set the limits in the Properties of particular User's account in ADUC.


    сила в справедливости
    • Marked as answer by RhysDavies Tuesday, February 23, 2010 4:30 PM
    Tuesday, February 23, 2010 4:22 PM
  • Sure are. You can do this in tow places: Group POlicy or TS/ RD Configuration tool:

    Here are the policies:

    Two places (either user or computer config):

         Computer Configuration| Admin Templates | Windows Components | Remote Desktop Services | Remote Desktop Session Host | Session Time Limits

         User Configuration | Admin Templates | Windows Components | Remote Desktop Services | Remote Desktop Session Host | Session Time Limits

    You can also acomplish this on a per server basis in TS Config (RDS Config), double click RDP-Tcp, navigate to the Sessions tab.

    And of course, in R2 this can also be done programatically via Powershell.


    Hope this helps,

    Kristin L. Griffin

    Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) 

    I finally started my blog: blog.kristinlgriffin.com
    Tuesday, February 23, 2010 4:25 PM