Windows Forum

Ask something
Discussion Locked

Logon Scripts

0 helpful
7 replies

by rsvfw

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Trying to create a logon script for Win2K Pro users, that will modify the registry (i.e. remove any keys that pertain to OS/2 or posix).

7 replies

by maxwell edison

KiXtart is a logon script processor and enhanced batch scripting language for computers running Windows XP, Windows 2000, Windows NT or Windows 9x in a Windows Networking environment.
The latest version (4.00) is of 19 november 2001 and can be downloaded here.

http://www.kixtart.org/downloads.html

The KiXtart free-format scripting language can be used to display information, set environment variables, start programs, connect to network drives, read or edit the registry change the current drive and directory and much more.

See the whole description here:

http://www.kixtart.org/

Another possibility:

How to Add User-specific Registry Values During Logon:

This tip outlines a method for adding user-specific registry values during the logon process. This is necessary when a change to HKEY_CURRENT_USER is desired but mandatory profiles cannot be used. It also remedies the situation where per-user information needs to be added to the registry during logon.

You can call regini.exe from a logon script to add or change user registry values. The syntax of the command is:

regini textfile.key

where textfile.key is a text file (with any extension) containing formatted registry entries, value types and data. For example, the following is a sample key file for HKEY_CURRENT_USER\Environment:

HKEY_CURRENT_USER\Environment
TEMP = REG_EXPAND_SZ %SystemDrive%\TEMP
TMP = REG_EXPAND_SZ %SystemDrive%\TEMP

Key files can be generated using the Windows NT 4.0 Resource Kit utility regdmp.exe and then modified using Notepad. Regini.exe is included with Windows NT 4.0, Terminal Server Edition. The key file is in the same directory as the logon script or referenced explicitly with a full path to its location, such as:

regini M:\WTSRV\system32\myfile.key

The preceding is from:

http://www.dabcc.com/Tips/tips.htm

(REMOVE SPACES from the pasted URLs.)

Maxwell

by maxwell edison

.
.
The following is the rest of the tip that was posted above:

Example: Adding user-specific environment variables during logon

In Windows NT 4.0, user-specific environment variables such as %TEMP% are stored in the HKEY_CURRENT_USER portion of the registry and are therefore difficult to control. Suppose you have an application that requires the %MYPATH% environment variable to exist for each user and the path needs to be C:\Myapp\%username%\settings. Using regini, you can add an environment variable %MYPATH% that points to this custom directory, including the name of the current user.

1. Use regdmp from the Windows NT 4.0 Resource Kit to generate your key file:

regdmp HKEY_CURRENT_USER\Environment > userenv.key

2. Open the userenv.key file and modify it to look like this:

HKEY_CURRENT_USER\Environment
MYPATH = REG_EXPAND_SZ C:\MyApp\%username%\settings

3. Save the userenv.key file to %SystemRoot%\system32\Repl\Import\Scripts directory (alongside your logon script) and add the following line to your logon script:

regini userenv.key

Users will now receive the custom %MYPATH% environment variable upon logon.

CAUTION: Adding user-specific environment variables will override system environment variables, so if you add a custom value for %PATH%, for example, you will nullify the system environment variable stored in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\ key.

NOTE: Regini.exe is capable of adding or changing registry values but not deleting existing values.

For more information about regini and regdmp, see the Windows NT 4.0 Resource Kit document Regini.doc.

Best of luck and have a GREAT 2002!

Maxwell

by joseph moore

Well, if you can set up one Win2KPro machine to the way you want it, you could then export those pieces of the Registry that are how you want them, then place the saved .REG files with the other login scripts. Have the logon scripts CALL the reg file names.
CALL REGEDIT /S regfile1.REG

etc.

This is conditional, of course, that the Registry pieces you could make from this one correct Win2KPro machine do not affect other Registry information.
Registry modification is a tricky business.

by rsvfw

I should have mentioned that the entity I work for runs four different makes and models of computer end items (i.e. HP, Compaq, Gateway and NEC) so this answer will not help in that instance - thank you though

by rsvfw

Neglected to state the following fact in the initial question - This must be done over a LAN or from a network drive, and it must work on different end items (i.e. HP, Compaq, NEC and Gatway machines)

This discussion is closed to new replies.