startup script problem

  • Thread starter Thread starter Paolo Francese
  • Start date Start date
P

Paolo Francese

Guest
I have set a startup script using group policy, the script install the
antivirus from a share.
On a portable PC with windows XP all works fine when the network cable is
plugged, but when I boot it with the network cable unplugged it's stuck for
90 seconds saying "Running startup script...".
The others PCs in the domain do not have this problem.

I've tried to debug the problem enabling the "Run startup scripts visible"
policy.
When the network cable is plugged the script window appers.
When the network cable is unplugged the script window does not appear.

Anyone have any idea?

Thanks in advance.
 
Re: startup script problem


"Paolo Francese" <francese at polito dot it> wrote in message
news:30F0619F-DE6A-4014-8D2B-D6110D6903B9@microsoft.com...
>I have set a startup script using group policy, the script install the
> antivirus from a share.
> On a portable PC with windows XP all works fine when the network cable is
> plugged, but when I boot it with the network cable unplugged it's stuck
> for
> 90 seconds saying "Running startup script...".
> The others PCs in the domain do not have this problem.
>
> I've tried to debug the problem enabling the "Run startup scripts visible"
> policy.
> When the network cable is plugged the script window appers.
> When the network cable is unplugged the script window does not appear.
>
> Anyone have any idea?
>
> Thanks in advance.

Add a few statements of the following form to your script so that you can
track its execution after the event.
@echo off
echo %date% %time% Label1 >> c:\test.log
{Your first script line goes here}
echo %date% %time% Label2 >> c:\test.log
{More of your script lines}
echo %date% %time% Label3 >> c:\test.log
{More of your script lines}
echo %date% %time% Label4 >> c:\test.log
{More of your script lines}
echo %date% %time% Label5 >> c:\test.log
{More of your script lines}
echo %date% %time% Label6 >> c:\test.log
{More of your script lines}

When you examine c:\test.log then you can see immedately where your script
gets stuck.
 
Back
Top