Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1454
  • Last Modified:

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.
0
nnolte99
Asked:
nnolte99
  • 3
  • 2
  • 2
  • +1
1 Solution
 
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
 
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
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
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
 
McKnifeCommented:
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
 
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

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now