No, it works fine when I run the scripts manually. The first script calls the second script, and the second script runs in a loop. The problem only occurs when running the scripts as part of the logon process.
Dumb question, but how do I launch the first script with Cscript? From: Christopher Bodnar [mailto:christopher_bod...@glic.com] Sent: Monday, June 07, 2010 4:48 PM To: NT System Admin Issues Subject: Re: Nested VBS in logon scripts Try launching the first script with Cscript instead of Wscript. Also, what happens if you launch the first script manually, instead of part of the logon process? Do you still experience the same issues? You want to see if it's the logon process that is causing the issue, or if it's really the scripts. Chris Bodnar, MCSE Systems Engineer Distributed Systems Service Delivery - Intel Services Guardian Life Insurance Company of America Email: christopher_bod...@glic.com<mailto:christopher_bod...@glic.com> Phone: 610-807-6459 Fax: 610-807-6003 From: John Hornbuckle <john.hornbuc...@taylor.k12.fl.us<mailto:john.hornbuc...@taylor.k12.fl.us>> To: "NT System Admin Issues" <ntsysadmin@lyris.sunbelt-software.com<mailto:ntsysadmin@lyris.sunbelt-software.com>> Date: 06/07/2010 04:06 PM Subject: Nested VBS in logon scripts ________________________________ I’m not a logon script or WScript expert—hopefully some of you are. A vendor has provided us with a VBS script that runs during logon. Its purpose is to call a second VBS script, with the goal being that the second script will continue running in the background after the user has logged in (it’s a loop that periodically sends a bit of data somewhere). So in the first script is a line that says: objShell.Run "\\server\path\SecondScript.vbs<file:///\\server\path\SecondScript.vbs>", 0, False Unfortunately, the second script—the one that’s supposed to run perpetually in a loop—dies while running. After extensive testing, it appears that the second script is dying when the first script’s WScript.exe instance wraps up; it’s not spawning its own separate instance of WScript. We know this because if we add “WScript.Sleep(10000)” to the end of the first script, the second script will continue to run for 10 seconds. But during those 10 seconds, the user logon process just sits there. So, is there a trick to this? A way to have the first script that runs during logon call a second script that will continue to run in a loop after logon is complete? The vendor says we’re the only installation they’ve seen this issue in. Could there be some group policy we have in place that would cause the behavior we’re seeing? John Hornbuckle MIS Department Taylor County School District www.taylor.k12.fl.us NOTICE: Florida has a broad public records law. Most written communications to or from this entity are public records that will be disclosed to the public and the media upon request. E-mail communications may be subject to public disclosure. ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you. NOTICE: Florida has a broad public records law. Most written communications to or from this entity are public records that will be disclosed to the public and the media upon request. E-mail communications may be subject to public disclosure. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
