Terminal Services Group Policies for disconnect

Discussion in 'Windows Small Business Server' started by GR Demi, Jun 20, 2005.

  1. GR Demi

    GR Demi Guest

    We are using a group policy to define a'Time limit for active but idle
    sesion' and "Sets a time limit for active Terminal Services sessions' yet
    we never disconnect or terminate a session when the limits are reached.

    We are using a company specific GPO that is linked to the local domain in
    the same manner as all the SBS GPO's. From gpresult and GPO modeling, the
    desired settings should be made. Other policies defined in this GPO are
    working.

    What are we missing?, Where are these changes actually made?this is the
    template we are modifying:

    a.. policy_name Policy
    a.. Computer Configuration (or User Configuration)
    a.. Administrative Templates
    a.. Windows Components
    a.. Terminal Services
     
    GR Demi, Jun 20, 2005
    #1

    1. Advertisements

  2. GR Demi

    GR Demi Guest

    I forget to mention we are only using remote desktop connection for
    administrative functions right now.
     
    GR Demi, Jun 20, 2005
    #2

    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. Win Upd local computer policies vs. AD policies

  2. Group Policies or Local policies

  3. Terminal Services Policies

  4. terminal Services Policies not working

  5. Logoff / Disconnect difference in Terminal Services Manager

  6. user policies not applying, system policies are

  7. Local group policies vs. domain group policies

Loading...