Logon Script won't run if network isn't available

My logon script set through GPO will not run if the network connection isn't available on startup.

For example, if the user logs off and logs back on, the script will run.  If the user waits a long time on initial startup before logging in, the script will run   However, if the user quickly logs in on initial startup before the network is available, the script will not run at all.  (the script is a batch file)

I would rather not run scripts synchronously, because that slows things down particularly for laptop users when they are off the network.  Is there a way to force Windows to cache the script locally to start before the network is up?

The server environment is Windows 2008 R2 and the workstations are Windows 7.
nnolte99Asked:
Who is Participating?
 
McKnifeConnect With a Mentor Commented:
There are ways, yes.
We can by a policy require that the network needs to be initialized before logon: http://technet.microsoft.com/en-us/magazine/gg486839.aspx - that is something else to running scripts synchronously.

You could also use a scheduled task instead of the common logon script. Deploy a task that gets triggered at logon of any user. Set a delay of 10/20 seconds inside that task and you are done.
0
 
rl3Commented:
If I'm understanding your post then the logon script is local to the AD server and not the workstation your user(s) would be logging into.  So if the network is not available the script is not accessible, because its on the server not the workstation.
0
 
nnolte99Author Commented:
Yes. That way when I update the script I only have to update the script in one location.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
tmoore1962Commented:
Are the systems connecting wirelessly?  I would set the local policy on the systems to 'wait for network before logging on'  when they are connected to domain the script should then run ok.  GPEDIT.MSC  Computer Config - admin templates - system - logon - always wait for network... to enable.
0
 
nnolte99Author Commented:
The systems are, for the most part, connecting through wire.  

Re your suggestion, what if the user is a laptop user working remotely. Won't that cause the person to hang for a long time.
0
 
tmoore1962Commented:
No it making the computer wait for network connection setting just makes it wait any detected network to get connected and then continue on the logon process as before,
0
 
McKnifeCommented:
What should that mean? Come again, please.
He wrote: "if the user quickly logs in on initial startup before the network is available, the script will not run at all" - that tells me that waiting is exactly what should be done here and the policy waits for the NIC to signalize it's connected.
0
 
nnolte99Author Commented:
Scheduled task assigned through AD is the way to go.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.