How can I limit the number of active local sessions

[vv211]

I wasn't really sure which forum to post this under, but my concern is based on the limited resources available to PCs so I put it here; anyway ....

I'm interning/working at a college, and right now we're talking about the issue of students walking away from the PCs without logging off. While everyone is in agreement that a lockout policy of, say, 30 minutes can mitigate the risks associated with this behaviour, I'm concerned with the PCs slowing down with too many of these locked sessions.

Our PCs are configured to reboot once every week, so if two students walk away from the PC each day without logging off (which I think is a conservative estimate), leaving all their programs open, there could be 10+ active, but disconnected, sessions end of day friday, slowing the PC down for any students who have a night class and logon to that PC.

So is there a way we can put a limit on how many active, local sessions there can be a computer? I'm hoping for something that goes along the lines of

IF new user logging on AND current active sessions >= 3
   force logoff oldest session
ELSE
   continue as normal

Any existing programs/built-in windows tools or help with making a script for this would be cool

Edit: I should mention we don't want to logoff idle users since some classes are 3+ hours, and if a student stops working for a bit during a lecture we wouldn't want to close their work on them and have them lose everything

 

[torchwood]

Hi Samuri,
have a look at this, (note Home premium does not have group policy)
https://www.google.co.uk/url?sa=t&r...).aspx&usg=AFQjCNESZomCZ27yA5usZ-GsyAe9_qpVxg
Roy

 

[vv211]

Thanks for the suggestion, but unless I'm misunderstanding what Terminal Services is, it's similar to Remote Desktop. These are all students who login locally on the PC's, and then will walk away from them when they're finished; nothing is being done remotely.

All PCs have Windows 7 Enterprise installed

 

[Ztruker]

This is old (2005) but I wonder if it still applies?

How can I limit the number of allowed concurrent sessions per user in an Active Directory (AD) domain?

 

[LMiller7]

This is old (2005) but I wonder if it still applies?

How can I limit the number of allowed concurrent sessions per user in an Active Directory (AD) domain?

This requires an Active Directory domain which must be hosted on a server OS. Not relevant to the current situation.

 

[vv211]

This is old (2005) but I wonder if it still applies?

How can I limit the number of allowed concurrent sessions per user in an Active Directory (AD) domain?

This requires an Active Directory domain which must be hosted on a server OS. Not relevant to the current situation.

We are using and AD domain. But there's also no guarantee that students will be logging in again at any other point during the week to kill their previous sessions.
I'm looking at more of a worst case scenario, which in all fairness hasn't happened yet to my knowledge.