Unless you have Win-9x systems, there's no need for a batch file. I'm not sure what forum you were reading, but that's not advice I'd give, and I have worked on some global enterprise environments. GPO logon script for computer and admin tasks and login script via profile for user/environment setup. This way, everything runs in the appropriate context.
I generally install our login script into the netlogon folder, customize the login.ini, and define one user to have "kix32.exe kixtart.kix" in the login script field of their profile. If that works as defined, I'll select groups of user with similar configurations in ADUC, edit the properties and change the login script setting for all of them. Our login script works on all platforms, from W2k to 2K8 and W7. In small environments (under 20 resource mappings and no lookups), it runs in sub-second times. We've actually had to allow admins to specify a "minimum display time" so the screen is visible for at least 5-6 seconds. In a large environment - 50+ resoureces and multiple 500-item lookup tables, it still runs in under 10 seconds. By eliminating custom coding (the login script is tokenized and the same script used at every client) and using a config file, I can usually have a login script installed and configured at a new client in a few minutes. At one client, I replaced 435 individual script files with a single script and config file in just a few days of review of existing scripts and change-control meetings.
Glenn
_________________________
Actually I
am a Rocket Scientist!
