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: 696
  • Last Modified:

logon script

I have a windows XP laptop that is having issues with the logon script.  I have a windows server 2003 DC where the logon scripts reside.  Every other PC runs fine, so far no issues with the logon scripts, besides this one particular one.  
When I run the logon script manually:  start -> run and type the path of my logon script location, and run the script, it works fine, so I'm thinking that it's an issue with timing, the logon script runs before another file needs to run or a service starts up.  

So is there a way to delay the logon script from running, at least by 5 or 10 seconds after the user logs on to windows XP?
0
afacts
Asked:
afacts
  • 2
  • 2
  • 2
2 Solutions
 
4runnerfunCommented:
If there aren't any other problems, then you can delay your script by pinging local host. Ping 15times..

ping 127.0.0.1 -n 15
0
 
afactsNetwork EngineerAuthor Commented:
I'm lost, so do I enter that command somehwere in the script?  
0
 
SommerblinkCommented:
From the 2003 Resource Toolkit, there is an executable called sleep.exe. (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd)

You can pass this an integer and it will pause.

Otherwise, there is a timeout command in Windows Vista/7.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
4runnerfunCommented:
Yes, wherever you want the pause, enter that command.
0
 
SommerblinkCommented:
Afacts: You would enter in the command the line above the command that is failing, if you believe that there is some sort of timeout issue.
0
 
afactsNetwork EngineerAuthor Commented:
Thanks guys for your help, but actually that wasn't the problem.   After I looked at the script, I looked where it was crashing on, and for some reason, it didn't like the network drive mapped letter, so I just changed it from I to Z, and it started working just fine.  Somehow, the system was creating the I drive as a "disconnected network drive", and it was just cuasing problems.

Thanks again for the quick response.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

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