Exceptionally slow Startup and Shutdown scripts

[Trapper]

Hello All,

When applying startup and shutdown scripts via group policy the machines just sit there on "Running Startup Scripts" for what can only be described as an epoch.

They rarely seem to do anything at the end, but for example the following script, which removes a single profile, took half an hour at shutdown!

@echo off


title Remove InstallXP Profile

echo.
echo.
cls
echo.
echo.
echo Deleting InstallXP profile
echo This is an automated maintainence protocol enacted by IT Support
echo.
echo Please wait...
echo.
rmdir /q /s "C:\Documents and settings\InstallXP"
echo.
echo Operation complete.
exit

I've also set a startup script to install an MSI, as the AD way of deploying rarely seems to work for me:

@echo off

title Installing Driving Software Theory 2010 for Room 43

echo Installing your Driving Software Theory 2010 software
echo Please allow this product to install
echo This should take no longer than 5 minutes
echo If you have any problems please contact IT Support
echo.
echo Many Thanks!
echo.
echo Please wait...
msiexec /i "\\hsapps\Software\RemoteDeploy\DTS Driving Client 2010\DTS Driving Client 2010.msi" /passive
echo Installation Complete! Please look for this program on your start menu under "Work Related Learning"
pause
exit

Is there anything obvious that I've done wrong on these scripts?!!

Any ideas on why it's so slow?

Cheers,

[ZeroHour]

Well your startup script tells it to repair/reinstall on every boot.
I really would try and get GP deployment working if I was you as its really a much better option in. What kind of issues were you having?

[browolf]

if you packet sniff the traffic from the pc using a laptop connected to a hub connected to the pc. When the pc is misbehaving, sometimes there's clues as to what the problem might be. like the pc is looking for something on the network and can't find it.

if would help to check the presence of the driving theory software before running the installer. ie no need to run it if its already there and batch is quicker.

if not exist "c:\program files\driving\etc.exe" do run msi