alvin.huff
2009-09-11, 01:59
Hello,
I am attempting to add a scheduled task for Spybot S&D. I want it to
update and immunize on fridays
scan multiple nights per week (2-4)
So far I can
create the schedule task (vbscript)
view it in the scheduled task window
The task runs and I can see it in the running processes but it does do anything (it executes a batch file that runs spybot S&D with appropriate switches)
My test was to run an update which should run briefly and then stop, but it never stops. It shows a bit of processor use at the start but nothing after a few seconds and it just sits there.
I am using a domain admin user account as the credentials for the task. The computer has the domain admin group added to the local admin group.
I can add a scheduled task with no errors with the script below.
script example:
'##domain admin prev
euser = "domain\user"
epass = "Pa555word"
Set objShell = Wscript.CreateObject("Wscript.Shell")
batch = "\\itfs1\ABOR\Batch_Files\spybot_autoupdate.bat"
schedule = "cmd /c schtasks /create /tn spybot_update /tr " & batch & " /sc once /RU " & euser & " /RP " & epass
return = objShell.run(schedule, 1, true)
I can see the process running under the domain admin account I provided in the script, but it hangs.
The process in general:
1.User logs on/off
2.script checks for proper scheduled tasks
3.if not then it will create them
4.schedule tasks will execute batch files that will call spybot S&D with appropriate switches.
any ideas? The task is created. The batch file is executed. I am thinking there is a resource it needs that it is waiting on.
any help would be greatly appreciated. Thanks.
I am attempting to add a scheduled task for Spybot S&D. I want it to
update and immunize on fridays
scan multiple nights per week (2-4)
So far I can
create the schedule task (vbscript)
view it in the scheduled task window
The task runs and I can see it in the running processes but it does do anything (it executes a batch file that runs spybot S&D with appropriate switches)
My test was to run an update which should run briefly and then stop, but it never stops. It shows a bit of processor use at the start but nothing after a few seconds and it just sits there.
I am using a domain admin user account as the credentials for the task. The computer has the domain admin group added to the local admin group.
I can add a scheduled task with no errors with the script below.
script example:
'##domain admin prev
euser = "domain\user"
epass = "Pa555word"
Set objShell = Wscript.CreateObject("Wscript.Shell")
batch = "\\itfs1\ABOR\Batch_Files\spybot_autoupdate.bat"
schedule = "cmd /c schtasks /create /tn spybot_update /tr " & batch & " /sc once /RU " & euser & " /RP " & epass
return = objShell.run(schedule, 1, true)
I can see the process running under the domain admin account I provided in the script, but it hangs.
The process in general:
1.User logs on/off
2.script checks for proper scheduled tasks
3.if not then it will create them
4.schedule tasks will execute batch files that will call spybot S&D with appropriate switches.
any ideas? The task is created. The batch file is executed. I am thinking there is a resource it needs that it is waiting on.
any help would be greatly appreciated. Thanks.