Article ID: 156677 - Last Review: November 1, 2006 - Revision: 1.2 Logoff Screen Saver Does Not Function in Windows NTThis article was previously published under Q156677 SYMPTOMS
If you are logged on to a server or workstation without administrative
rights, the logoff screen saver included in the Windows NT 3.51 and 4.0
Resource Kits does not function properly.
You will also get the following error messages when attempting to use the utility without administrative rights:
Error encountered while creating registry key. Make sure you have set
values and create subkey permissions.
RESOLUTIONImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows In order for non-administrators to be able to use WINEXIT, you must add Set Value and Create Subkey permissions for the group Everyone on the following registry key:
HKEY_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\IniFileMappings\Control.ini
To do this, use the following steps:NOTE: You must be logged on with administrative rights to make these changes.
MORE INFORMATION
WINEXIT is a screen saver that logs the current user off after the
specified time has elapsed. In other respects, it is similar to other
screen savers and can be configured and tested on the Screen Saver tab of
the Display Properties dialog box in Control Panel.
WINEXIT displays a dialog box in which it displays the countdown timer and a user-defined message. When the countdown timer reaches zero, the log off process is initiated. To install Winexit.scr before configuring:
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 3.51 &
4.0. We are researching this problem and will post new information here in
the Microsoft Knowledge Base as it becomes available.
| Article Translations
|

Back to the top
