Discussion Locked

Automated log out for NT 4.0

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
How can I set users to automatically log off after a set period of inactivity?

10 replies

by vshipp

Unfortunately, with the exception of RAS or dial up networking, this functionality is not available in NT4 (or 2000 for that fact)
there are ways to manually end a session from server manager etc. but nothing that I have seen to automate this.

If you are attempting to get all connections cleared in the evening for backup purposes, you could run a batch job prior to beginning the backup.

First get a list of all machines in the domain.

Netdom /noverbose member >> machines.lst

Will give you a list of domain machines.
Be sure to remove any Servers or machines that you do not want involved.

Next, with the machines.llst file in the root of your current directory, type:

for /f %a in (machines.lst) do shutdown %a /R T:10 /Y

This will reboot each machine thus ending the session.
Ugly, YES but effective. The users will lose any open files, but so would an unattended logoff.
The use of this should be limited to absolute necessity situations like that last full backup on new years eve 1999 et

by mrshawng

The Windows NT 4.0 Resource Kit contains a screensaver called "WinExit" when correctly installed and configured, it will log off any users after a predetermined amount of time. It is in effect a screensaver that logs you off instead of displaying a screen image.

CYA

by paul_beauvais

There is a screen saver in the resource kit that will do this. The problem with that is that it works to well during peak work hours and if a user needs to use the screens aver duing the day they are logged off. This creats alot af extra network traffic and haedachs for users.

An alternate solution may be to write a VB or C++ app that checks the system time and then accesses the user32 api to close all open programs and log any user off. This can be even more effective becouse in the code you can exclude groups of users (such as the Administrators group).

Further you could easily register this as a service to stop users for using the task manager to stop the proccess.

If you have any questions feel free to email me directly.
Paul

This discussion is closed to new replies.