How can I extend automatic log out times for Terminal Services in Windows Server 2008?
Hi,
I am running a SBS server 2008 and a Windows Server Standard 2008. The SBS server 2008 is the Domain Controller and the Server Standard is the Terminal Server. I am running a mixture of desktop computers and Thin client machines to log into the Terminal Server using terminal services. I am trying to find a way to extend the Auto logging out of the machines so that the Staff does not have to keep logging in every half hour or so. Most staff have their own desks so there is not different users on the machines, just one user per machine. How can I extend the logout times to say about an hour or two??
Thanks
Paul
I am running a SBS server 2008 and a Windows Server Standard 2008. The SBS server 2008 is the Domain Controller and the Server Standard is the Terminal Server. I am running a mixture of desktop computers and Thin client machines to log into the Terminal Server using terminal services. I am trying to find a way to extend the Auto logging out of the machines so that the Staff does not have to keep logging in every half hour or so. Most staff have their own desks so there is not different users on the machines, just one user per machine. How can I extend the logout times to say about an hour or two??
Thanks
Paul
ASKER
Are they on the Terminal Server? Is that stuff under Administrative Tools?
Thanks
Thanks
on the terminal server itself - you can run gpedit.msc
from the domain controller, its under admin tools - group policy management,
from the domain controller, its under admin tools - group policy management,
ASKER
I have checked under User properties and from there gone to the tab Sessions and it has session limits there but they are listed as Never to time out. Is there anywhere else that this is controlled by?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry forgot to mention, once you have enabled the policy please make sure to RESTART your Terminal Server, as since you would be moving the machine in different OU, computers don't generally give desired result unless you reboot them.
Don't rely on gpupdate /force, just give it a Reboot to be sure.
A
Don't rely on gpupdate /force, just give it a Reboot to be sure.
A
ASKER
How do you create OU?? I take that to mean Organisational Unit??
Thanks
Thanks
Right Click in Active Directory > New > Organisational > Unit
Look through computer configuration - admin templates - windows components - remote desktop services - remote desktop session host. I believe you'l;l find the settings you need there.
Specifically the active session idle timeout setting.