Endpoint Protection

Q: SEP: How do I delay logon script starting until network communicataions is possible?

WindowsXP starts after logon and the logon script, traditional .cmd script, starts before SEP has completed starting and allows network communication.

What is the best way to delay the logon script from running until network communications is possible?

I feel this may be a by-product of the delay introduced as SEP starts.  Using current SEP version.

The PAUSE cmd is not what I'm looking for - because it requires user intervention, press enter, to allow the script to continue.

Hi,

In windows, there is a way to delay the start of a service. Its called "Service Delayed Start".

Please refer to the link below for the same:

http://support.microsoft.com/kb/193888

P.S.: I would not recommend to make this a policy or a companywide enforcement for the same. As you are delaying the start of a security software, that your system vulnerable when it is starting up. And that can be considered as an attack vector.

Aniket

I don't think you read the message I posted.  Perhaps you were trying to respond to some other message from someone else.  I'm not wanting to delay the start of services.  The word 'service' is not even in the message I posted.  Please read the message again.

I'm still looking to start the logon script or hold its' processing until after network access to drive shares on a windows server is availalbe.  Currently the logon script starts and runs before network access is available.  It runs before Symantec Endpoint Protection has completed its' start up process.  Thus, any NET USE drive mappings fail.

Check out this article from Microsoft.................http://support.microsoft.com/kb/305293

There is a group policy that forces computers to wait for network before starting up or logging in.  Make sure to read the article throughly.  To ensure that it applies to you.  Also note that the default is to allow "Fast logon optimization".

I had to use this for my logon script to run and map drives properly.

I am glad to hear that it worked for you!  Would you be so kind as to mark this as the solution to your problem?  Thanks!