Task Scheduler Not Running VBScript Correctly

January 14, 2016 at 14:31:33
Specs: Server 2008, 16g
have a very frustrating issue with Task Scheduler that I’m hoping someone can shed some light on for me. I’ve scheduled a task that runs a VBScript which collects all users who are in the Administrators group from several VM’s. The problem is when I run the task from a Windows Server 2008 R2 64-Bit I only get a partial list of users or none at all. But if I run the same script from a Windows Server 2012, it works fine. The output is just a txt file.
I’ve tried all these settings from another post:
1) Make sure that the task is set to "configure for Windows Vista or Windows 2008" on the first page of the task properties (under the "general" tab) 2) Make sure that the task is set to "start in" the folder that contains the batch file: open the task properties, click on the "actions" tab, click on the action and then the "edit" button at the bottom. In the "Edit Action" Window there is a field for "start in (optional)" that you set to the path to the batch file. 3) Make sure that the task is running as an account that has explicit "Full access" permissions to all these things: The .bat file itself, the folder containing the .bat file, and the target files/folders that are affected by the .bat script. Inherited permissions didn't seem to work for me. 4) Make sure that the account running the task is a member of the local "administrators" group for this machine 5) Make sure that the task is set to "run whether logged on or not" 6) The Task should run successfully with expected output when you right-click on the task and select "run" If it does that then it will run successfully when you are logged off.
Thanks in advance.

See More: Task Scheduler Not Running VBScript Correctly

Report •


#1
January 15, 2016 at 17:22:46
Kinda hard to troubleshoot a script without seeing it first.

How To Ask Questions The Smart Way


Report •

#2
January 19, 2016 at 06:36:32
That's just it, the script works. It has problems on Win2008 srv and if I move it to a 2012 svr, I have no issues. I've read that server 2008 might have issues with vbscript, but haven't found a resolution. Any ideas?

Report •

#3
January 19, 2016 at 09:04:50
How, exactly, is it failing? Are you capturing any error text? If so, what error text are you getting?

How To Ask Questions The Smart Way


Report •

Related Solutions


Ask Question