So have VBS script 1 call a batch file, and have the batch file call VBS script 
2?

As for the vendor... It's iBoss, a content filtering company. And we're 
definitely not the first in Florida to use them.  :-)





-----Original Message-----
From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: Monday, June 07, 2010 4:45 PM
To: NT System Admin Issues
Subject: RE: Nested VBS in logon scripts

Well, you are probably going to have to wrap the second script in another bat 
file and use "start".

If they say that no one else is experiencing this, then they probably haven't 
sold their solution elsewhere. :-)

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com


-----Original Message-----
From: John Hornbuckle [mailto:john.hornbuc...@taylor.k12.fl.us]
Sent: Monday, June 07, 2010 4:36 PM
To: NT System Admin Issues
Subject: RE: Nested VBS in logon scripts

No dice, I'm afraid.

The first suggestion hangs the login completely. Which makes sense, because the 
first script is waiting for the second script to finish, but the second script 
will never finish; its whole purpose is to run perpetually as long as the user 
is logged in.

The second suggestion calls the second script, but same problem as before--it 
only runs for a moment before quitting. The WScript.exe process doesn't 
continue to run in the background after the user is logged in.






John





-----Original Message-----
From: Ben Scott [mailto:mailvor...@gmail.com]
Sent: Monday, June 07, 2010 4:21 PM
To: NT System Admin Issues
Subject: Re: Nested VBS in logon scripts

On Mon, Jun 7, 2010 at 4:05 PM, John Hornbuckle 
<john.hornbuc...@taylor.k12.fl.us> wrote:
> objShell.Run "\\server\path\SecondScript.vbs", 0, False

  First, try:

        objShell.Run "\\server\path\SecondScript.vbs", 0, True

  The "True" tells the script host to wait for the run command to finish before 
continuing.

  If that doesn't work, try:

        objShell.Run "wscript  \\server\path\SecondScript.vbs", 0, True

  That should work for sure, as it explicitly starts a new script host.  You 
may need the full path to WSCRIPT.EXE; I'm not sure if .Run honors PATH or not.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~


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/>  ~


~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~



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/>  ~

Reply via email to