Depends on what your scripts are doing.
I had my login script maintain the login configuration in an INI file. The script took nearly 90 seconds to run on a 256K frame-relay link. By caching the file on the local disk, the login script time to run dropped to 12 seconds with a cached file and 16 seconds if the file was missing or outdated.
To cache it locally, I simply A) check for a local copy - download if not present. B) if present, compare the file times and download if the local copy is older. The login script always references the local copy - a HUGE performance gain. 12-16 seconds to map an average of 7 of 20 shared drives, display 2 messages, and run 3 external programs over a 256K link is not bad, considering everything loads from the netlogon share.
The other think I did to improve performance is to determine up front what shares I'd be mapping - load all share parameters into an array, compare security (group and OU membership) and remove those definitions that failed. What I had left, I simply mapped with no further checks.
My script, with documentation and sample config file, is available from my web site if you want to take a look. I've used it at well over 100 client sites without script changes anywhere - all done via the config file.
Glenn
_________________________
Actually I
am a Rocket Scientist!
