Startup script

[briannbecky]

I recently setup a startup script for all computers on the network
through group policy. The script is just a very simple VBScript that
adds our IT department group into the administrators group of each
computer, it's only 4 lines long and is 1KB in size. For some reason,
the XP computers run this script in a couple seconds, while 2K
computers hang for about 10 minutes. Anyone seen this before? Like I
said, it's small and only takes a second or two when running it
manually. Also, many people with 2K machines have called complaining
how slow it is starting up, so I removed the group policy. Now, even
though I removed it, it still hangs on running startup scripts. Why
would it do this if there is no longer anything to run? Any help you
guys can provide would be greatly appreciated!

Thanks,
Brian

 

[lforbes]

I recently setup a startup script for all computers on the
network
through group policy. The script is just a very simple
VBScript that
adds our IT department group into the administrators group of
each
computer, it's only 4 lines long and is 1KB in size. For some
reason,
the XP computers run this script in a couple seconds, while 2K
computers hang for about 10 minutes. Anyone seen this before?
Like I
said, it's small and only takes a second or two when running
it
manually. Also, many people with 2K machines have called
complaining
how slow it is starting up, so I removed the group policy.
Now, even
though I removed it, it still hangs on running startup
scripts. Why
would it do this if there is no longer anything to run? Any
help you
guys can provide would be greatly appreciated!

Thanks,
Brian

Hi,

Windows XP has a feature that actually loads the desktop etc while the
scripts and the services are still starting running. Therefore the
script is more than likely hanging on the XP machines as well but it
just keeps going. Windows 2000 doesn’t have this feature.

I have never had any luck getting VBScripts to run well on startup. I
can get them to run on logon but it seems that the VBScript engine
doesn’t often start before the "startup scripts" runs. I have tried
it on everything from printers to creating directories etc.

There is an option to "run scripts visable" in Group Policy. I find
this works really well for troubleshooting. It will tell you what
scripts are hanging and the errors.

This script may be a problem IF the IT are Already a member of the
administrators group. Therefore it may be generating an error. You can
add the line "on error resume next" into your VBScript. This will make
it continue on error.

It may be not that script that is hanging or the script may be
elsewhere. A good idea is to install the Group Policy Management
console as it shows you on a glance what startup scripts are active.

Cheers,

Lara

 

[briannbecky]

Lara,

Thanks alot for the info! I discovered in group policy, that you need
to enable the option to run the scripts asynchronously. It flies
through it now with hardly any delay!

Brian