Auto Log off

[bloomlight]

We have Win 2003 server as doamin controller system. We alao have a number of computers configured as shared computer(multiple users using the same computer). Users suppose to log off the computer when they done before they leave. Sometimes they fogot to do that. It causes the problem for next user. On the screen, it would say something like this: The computer is locked by user (user name). Only user (user name) or domain administrator can unlock this computer.

I am wondering if there is a way that server can automatically log off the user after certain time. Let's say after 30 minutes of inactive, server can kick off that user and give a nomal logon screen for next user. Thanks

 

[nevets2001uk]

There is a tool called winexit.scr that might work for you. It should allow you to specify a period of inactivity before triggering a log off of the current user. It can be forced but will loose any unsaved work.

This could be applied via a group policy to the computers you wish to enforce this on.

http://www.computerperformance.co.uk/ScriptsGuy/WinExit.zip

Steve G (MCSE / MCSA:Messaging)

 

[bloomlight]

Thanks. I have downloaded this program already.

How to put this program to Group Policy? I am not familiar with that area and would appreciated very much if you can help.

 

[nevets2001uk]

Hopefully you have a top level OU under which all the users you want to apply this to exist.

Open the Group Policy Management Console GPMC (assuming you have it installed). Locate the OU containing the users and create and link a new policy.

The settings you will need can be found under User Configuration > Control Panel > Display. The descriptions should help you work out which is which and you can always get more help my googling them. You will need to change the Screen Saver Executable Name and Screen Saver Policies I believe. We don't do this here so I can't be precise but I'm sure it should get you started.

Once the GPO is applied all users in the OU should get the winexit screensaver and be logged off automatically as per it's settings. I'm not sure how you specify the timeout though.

As a best practice, try this with a test client in a seperate OU first as it's best not to make GPO changes on the live OU's without testing them. If you are happy it works and doesn't brake anything than you can link it to the main OU.

Steve G (MCSE / MCSA:Messaging)