TrentGreenawalt
Technical User
Hi, I have one terminal server with roughly 30 users on it at the same time and since my ERP solution doesn't have a timeout setting for users within the actual program I am forced to do this with AD, terminal server Local policy, or Group policy.
So my question is this:
What is the best way to do this, and what settings actually superceed the others. My biggest problem is that nothing that I have tried to "set" actually does anything.
Here is some pertinent info to help with your response:
1) I have different groups of users with different timeout settings: salesreps 15 min, cust service 30 min, and two "machines" that run scheduled tasks that can't have a timeout.
2) I have tried the individual settings in each of the users AD accounts Sessions tabs, but they don't work. I have setup a GP to lock down the terminal server in it's own OU and that still doesn't even work for "everyone" (Note: this isn't a desired solution anyways due to the users that need no timeout period.
3) I have a feeling the Local machine policy is messing everything up, but from what I have read the GP should superceed the local policy.
So if anyone has any insight into this I would greatly appreciate it. Idealy, I would like to lock the machine down from GP and then control the timeout via AD. My next "troubleshooting step" is to remove all policies on it and start from the top down meaning AD sessions, get that to work and then pass down the rest of the lock down steps via GP.
Thanks in advance for your help!
Trent Greenawalt
Anderson Pump & Process
Brookfield, WI
So my question is this:
What is the best way to do this, and what settings actually superceed the others. My biggest problem is that nothing that I have tried to "set" actually does anything.
Here is some pertinent info to help with your response:
1) I have different groups of users with different timeout settings: salesreps 15 min, cust service 30 min, and two "machines" that run scheduled tasks that can't have a timeout.
2) I have tried the individual settings in each of the users AD accounts Sessions tabs, but they don't work. I have setup a GP to lock down the terminal server in it's own OU and that still doesn't even work for "everyone" (Note: this isn't a desired solution anyways due to the users that need no timeout period.
3) I have a feeling the Local machine policy is messing everything up, but from what I have read the GP should superceed the local policy.
So if anyone has any insight into this I would greatly appreciate it. Idealy, I would like to lock the machine down from GP and then control the timeout via AD. My next "troubleshooting step" is to remove all policies on it and start from the top down meaning AD sessions, get that to work and then pass down the rest of the lock down steps via GP.
Thanks in advance for your help!
Trent Greenawalt
Anderson Pump & Process
Brookfield, WI
