----------Need setup a bunch of pc's to Auto Log Off

[thatsright]

We have 12 NT 4.0 Workstation PC's here at my job. What I'd like to do is set each one of them to automatically log off after an hour of inactivity.

Is there anyway I can set this up to happen automatically, regardless of who uses the machine? I tried WinExit from the NT 4 Resource Kit, but it only works per user, and as soon as someone else logs into the PC, it disappears.

Thanks

 

[bustacaptx]

http://archives.neohapsis.com/archives/sf/ms/2001-q1/0168.html

If I recall correctly, in the resource kit, there is a screensaver that logs out the user when it starts (works for NT 4.0 WS and Windows 9x, most likely Win2K). I would look into combining that with a policy that prevents users from changing the screensaver and you achieve your goal.

---end quote---

Google is your homeboy.

 

[thatsright]

Originally posted by: bustacaptx
http://archives.neohapsis.com/archives/sf/ms/2001-q1/0168.html

If I recall correctly, in the resource kit, there is a screensaver that logs out the user when it starts (works for NT 4.0 WS and Windows 9x, most likely Win2K). I would look into combining that with a policy that prevents users from changing the screensaver and you achieve your goal.

---end quote---

Google is your homeboy.

But, what you don't understand is that this tool only works PER USER, So if there are 22 people who might use the PC, I have to install/setup the program 22 times.

 

[bustacaptx]

That's what I get for not reading the entire post.

I've not used NT 4 in a my excellent compatriot's age, but can't you install WinExit as an admin to be available for all users?

If not, create a simple reghack to check for installed WinExit on login and, if not installed, install it for the current user. Should be relatively easy.

If that doesn't work ... well, just leather up and install it manually for all the users. Can't take more than an hour tops, right?

 

[thatsright]

Originally posted by: bustacaptx
That's what I get for not reading the entire post.

I've not used NT 4 in a my excellent compatriot's age, but can't you install WinExit as an admin to be available for all users?

If not, create a simple reghack to check for installed WinExit on login and, if not installed, install it for the current user. Should be relatively easy.

If that doesn't work ... well, just leather up and install it manually for all the users. Can't take more than an hour tops, right?

40 or so users, times 12 NT workstations pcs....Ohhh thats only 480 Installs on WinExit!!!!:thumbsup:

I tried installing WinExit as the Machine Admin, and then as the Domain administrator, but the same problem in that it disappears when I log on as someone else.

 

[bustacaptx]

This may be what you're looking for ... Group Admin Policies

http://www.microsoft.com/technet/prodte...technologies/management/gp/admtgp.mspx

Introduction
Administrators can use Group Policy to deliver and apply one or more desired configurations or policy settings to a set of targeted users and computers within an Active Directory® directory service environment. The majority of available policy settings are provided through Administrative Template files (.adm files) and are designed to modify specific keys in the registry. This is known as registry-based policy. For many applications, the use of registry-based policy delivered by .adm files is the simplest and best way to support centralized management of policy settings.

Intended for IT administrators and developers, this document describes how to implement registry-based Group Policy by using .adm files.

For detailed instructions about enabling applications for Group Policy, see ?Group Policy? in the Microsoft Platform Software Development Kit at http://go.microsoft.com/fwlink/?LinkId=26258.

Overview of Registry-Based Policy and Administrative Template Files
By using registry-based policy, operating system components and applications can respond to registry key settings that administrators can manage centrally with Group Policy. These policy settings determine the behavior of the application for targeted computers or users. As long as a component or application has been policy-enabled (that is, its behavior changes based on registry values indicated in the .adm file), you can manage its features and settings through registry-based policy.

.Adm files are UNICODE text files that Group Policy uses to describe where registry-based policy settings are stored in the registry. All registry-based policy settings appear and are configured in the Group Policy Object Editor under the Administrative Templates node. .Adm files do not apply policy settings; they simply enable administrators to view the policy settings in the Group Policy Object Editor. Administrators can then create Group Policy objects (GPOs) containing the policy settings that they want to use. For example, you might have one GPO that contains various policy settings for managing the Active Desktop feature.

[snip]

 

[bustacaptx]

Also:

http://blog.case.edu/djc6/

Automatically log off users
One of the concerns I had with Active Directory in the Nord Computer Lab was that users would forget to log off their account. Previously, the computers automatically logged on as a generic user, so people had a habit of not logging off. One way to remedy this situation is the WINEXIT.SCR screensaver which is part of the Windows Server 2003 Resource Kit Tools

Copy the file to C:\WINDOWS\SYSTEM32 on each computer, and use the group policy management console to set this as the default screensaver and set the timeout period. You MUST also change the permission on a registry key for the screensaver to work for all users of the machine. See KB156677: Logoff Screen Saver Does Not Function in Windows NT

By default, WINEXIT.SCR presents the user with a dialog box 30 seconds before they are to be logged off, which is determined by when you've set the 'screensaver' to kick on. I wanted the dialog box to come on a lot earlier, say 5 minutes before hand to give the user time to react. You can also set WINEXIT.SCR to Force application termination, and insert a custom message. The following ADM file I wrote can be used with the group policy management console to configure these settings. Installing this will put a group of settings entitled "Winexit.scr Policy settings" under "User Configuration->Administrative Templates" in the GPMC.

;; Remember in GPMC to go View->Filtering
;; and uncheck "Only show policy settings that can be fully managed"
;;
;; David Carlin (djc6@case.edu) 2/25/2005
;;
;; WINEXIT.SCR is located in the Windows Server 2003 Resource Kit

CLASS USER

CATEGORY !!Screen_Saver_Policy

POLICY !!TERMINATE_APPS
KEYNAME "Control Panel\Screen Saver.Logoff"
VALUENAME ForceLogoff
VALUEON "1" VALUEOFF "0"
END POLICY

POLICY !!COUNTDOWN_TIMEOUT
KEYNAME "Control Panel\Screen Saver.Logoff"
VALUENAME CountDownTimer
VALUEON "300"
END POLICY

POLICY !!ENTER_DIALOG_MESSAGE
KEYNAME "Control Panel\Screen Saver.Logoff"
PART !!ENTER_DIALOG_MESSAGE
EDITTEXT
DEFAULT !!DEFAULT_MESSAGE
VALUENAME DialogMessage
END PART
END POLICY

END CATEGORY

[strings]
Screen_Saver_Policy="Winexit.scr Policy settings"
TERMINATE_APPS="Terminate running applications"
COUNTDOWN_TIMEOUT="Enable 5 minute warning logoff notice"
ENTER_DIALOG_MESSAGE="Warning message about being logged off"
DEFAULT_MESSAGE="You are about to be logged out. Press the cancel button to stop this