Gimpy,

You can try the pre-made login script from my site. Put the kixtart.kix, login.ini, and kix32.exe in your netlogon share (after customizing the INI file, of course) and you're done.

I recently inherited an environment with 329 .KIX files, 14 .REG files, and 12 .VBS scripts that comprised the "login script" and now have one script & one config file to handle all the logic. Talk about scary!

Using this script/config file, you can pretty much reduce your login script configuration to:
Code:
[PROGSHARE]
CLASS=DISK
TARGET=P:
PATH=\\FS001\programs
GROUPS=
OUS=
# repeat this for each mapping, defining groups and/or OUs
# to control who gets the mapping

# This resource record reports the mapping, but actually doesn't map 
# anything, since this happens automatically in AD domains
[HOMESHARE]
CLASS=DISK
TARGET=H:
PATH=HOME


# display a disclaimer, Message Of The Day, or some important notice
# (up to 10 allowed)
# domain admins don't get this message :)
[DISCLAIM]
CLASS=MESSAGE
PATH=disclaim.txt
GROUPS=!Domain Admins

# Call a script to display the disclaimer AND ask for acknowlegement
# Only domain admins - discourages logging in with that much power ;)
[ADMIN_DISCLAIM]
CLASS=SCRIPT
PATH=disclaim.kix
METHOD=call
GROUPS=Domain Admins

Just shows an example of how to think of your login needs as a collection of resources instead of lots of IF statements and hard-coded logic. The configuration is fully documented in the ZIP package.

Short of enhancements due to NT4 => W2K => W2K3 and the growth of kixtart's capabilities, the core logic in this login script has changed very little from when I first wrote it in 1996. (yeah, that's 11 years ago!)

Glenn
_________________________
Actually I am a Rocket Scientist! \:D