Inactivity Settings for User Accounts

  • Thread starter Thread starter Mike Towan
  • Start date Start date
M

Mike Towan

Is there a way through GPO to apply a policy to either a
machine or an OU that will time out an inactive network
session? What I am looking for is something similar to
what you can do with terminal sessions. I have a handful
of users that roam around and leave themselves logged on
to multiple machines at a time, sometimes for days at a
time, and I want to be able to cut that off with GPO.
 
-----Original Message-----
Is there a way through GPO to apply a policy to either a
machine or an OU that will time out an inactive network
session? What I am looking for is something similar to
what you can do with terminal sessions. I have a handful
of users that roam around and leave themselves logged on
to multiple machines at a time, sometimes for days at a
time, and I want to be able to cut that off with GPO.


.
Click to expand...
One thing that you might want to consider would be to
limit these "problem" users to one or two machines. You
can do this in their user profile. The other way would be
to use GPO to restrict the "log on locally" right for EACH
AND EVERY machine. That would probably be a lot of work!

There is also CCONNECT from the Resource Kit. Howerver,
IIRC, that requires that you have a SQL Server.

I know that this limits the number of computer on which
these users can log. It prevents them from logging on to
any other computers. Not exactly what you are asking.

I would have to take a look into this further. Off the
top of my head I can not think of a Policy - or
a "workaround" - that does this.

Cary
 
-----Original Message-----

One thing that you might want to consider would be to
limit these "problem" users to one or two machines. You
can do this in their user profile. The other way would be
to use GPO to restrict the "log on locally" right for EACH
AND EVERY machine. That would probably be a lot of work!

There is also CCONNECT from the Resource Kit. Howerver,
IIRC, that requires that you have a SQL Server.

I know that this limits the number of computer on which
these users can log. It prevents them from logging on to
any other computers. Not exactly what you are asking.

I would have to take a look into this further. Off the
top of my head I can not think of a Policy - or
a "workaround" - that does this.

Cary
.
Click to expand...

Cary,

Thanks for the info! I will look into the CConnect option
and see what it does. Limiting the computers wont work,
because the users are mobile, which is half the problem
now...they can log on to any of about 30 machines on a
regular basis.

Thanks for checking into it!

Mike
 
-----Original Message-----


Cary,

Thanks for the info! I will look into the CConnect option
and see what it does. Limiting the computers wont work,
because the users are mobile, which is half the problem
now...they can log on to any of about 30 machines on a
regular basis.

Thanks for checking into it!

Mike
.
Click to expand...
Mike,

CConnect will allow them to be logged onto one machine at
a time - PERIOD!

So, if "John" logs into machineA at 8:30am on the first
floor in the corner office and then is called into a
meeting with "Sally" and John - at 9:15am in the middle
office - wants to check an e-mail that has some
information regarding their meeting and trys to log onto
machineB John will not be allowed to ( forget about the
fact that he could use OWA internally to check that e-
mail!!! ).

So, this sorta sets the "inactivity" period to 0 seconds!
I guess, if you want to look at it that way.

Cary
 
Back
Top