Sort of. The program needs Run logon scripts synchronous disabled to be used in a logon script.
Too Rube Goldberg overall for my tastes. Back to the drawing board on web filters. :) From: Carl Houseman [mailto:[email protected]] Sent: Thursday, May 13, 2010 3:49 PM To: NT System Admin Issues Subject: RE: VBS script issue Have the script copy the autheticat.exe to the %temp% area and run it from there instead. If it needs other supporting files in that folder, copy those too. And since it's not supposed to complete, change that True to a False, else the script will stall the user login until it times out. From: Kennedy, Jim [mailto:[email protected]] Sent: Thursday, May 13, 2010 3:40 PM To: NT System Admin Issues Subject: RE: VBS script issue I did. The exe does not complete...it is supposed to keep running in the background until logoff. From: Carl Houseman [mailto:[email protected]] Sent: Thursday, May 13, 2010 3:27 PM To: NT System Admin Issues Subject: RE: VBS script issue Did you keep the 0,True arguments as in my example? You should get the errorlevel return of the .exe if you wait for it complete. From: Kennedy, Jim [mailto:[email protected]] Sent: Thursday, May 13, 2010 3:12 PM To: NT System Admin Issues Subject: RE: VBS script issue Very good idea. Status returns empty, but at least I now know for sure the script is firing. From: Carl Houseman [mailto:[email protected]] Sent: Thursday, May 13, 2010 1:07 PM To: NT System Admin Issues Subject: RE: VBS script issue Write an event with the returned status value of WshShell.Run. This will confirm the script ran and tell you if the process creation was successful. iStatus=WshShell.run(\\netbiosDomainName\netlogon\VBS\m86\authenticat.exe RA[x.x.x.x],0,True) WshShell.LogEvent 4,"authenticat.exe status returned: " & iStatus Carl From: Kennedy, Jim [mailto:[email protected]] Sent: Thursday, May 13, 2010 8:59 AM To: NT System Admin Issues Subject: VBS script issue Simple user script assigned to the user via GPO for logon. Calls a run and runs an exe so they authenticate to our webfilter. Domain Name has been munged. It fails to run when they login but if I just double click it as they are logged in it runs just fine. Gotta be something simple I am missing here. This is on XP SP3 workstations in a native 2008 domain. on error resume next Set WshShell = WScript.CreateObject("WScript.Shell") WshShell.Run "\\netbiosDomainName\netlogon\VBS\m86\authenticat.exe RA[x.x.x.x]" ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
