Your script may not be displaying due to the default GPO settings. By default, the login script runs minimized.

I take the middle ground in login script visibility - I force my login scripts to run visibly, and even force them to remain on the screen for 15 minutes if an error occurs (unless they actually read the message and press a key). If all goes well, the login script flashes and disappears in 3-4 seconds. I color code the resource mappings - green for good and red for fail. A failure causes the script to not close and asks the user to contact the help desk. If a login script runs minimized, errors can occur and the user would never know.

There are two GPO settings - Run Login Scripts Visible (default false) and Run Login Scripts Synchronously (default false). I change both of these - the first to allow the script to run visibly and the other to prevent the desktop from appearing until the login script completes.

If you're not comfortable with setting GPO properties, you can download the pre-built login script from my web site. No need to know scripting (in fact, you can't modify it) - just create a config file to define the resources you want to map. Some advantages:
  • No script knowledge needed
  • The core display is customizable - just create a "LoginDisplay.kix" file with the display info and format you want. This runs after the script initializes but before any resource mapping is performed. This requires a minimal understanding of macros, variables, and "?" to create basic screen output. (avoid use of AT!! It's unnecessary and mostly inappropriate outside of doing plain-text forms input.)
  • Simple configuration of resource records, yet powerful mapping parameters to decide what and how resources are mapped.
  • Path rewriting - change the UNC path based on user, site, subnet, or OU.
  • Support for per-user configuration files - perfect for testing or special user situations.
  • Fully supported - we offer free startup support via email on up through complete site engineering and training for a reasonable fee.

For your simple configuration, the LOGIN.INI file would contain
 Code:
# ForceVisible is a boolean value that forces the login script to run in a maximized window
ForceVisible=y
# Minimum tune to display the login script window (in seconds)
# Insures that the window id displayed for at least "n" seconds in fast environments
MinimumDisplayTime=6

[H_DRIVE]
CLASS=DISK
TARGET=H:
PATH=\\server\share
DESC=Common data share

You'd then create a LoginDisplay.kix script with the following:
 Code:
Color g+/n
Big ; Display in BIG character mode
'ASA' ?
Small     ; rest in normal size text
'whatever else you want to display...' ?

There are dozens of variables available to you from the login script initialization at this point, all documented in the readme. You can use any of them along with macros to display what you want. The resource mappings will automatically display after your initial message, successful maps in green, unsuccessful in red.

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