Windows 2008 scheduled tasks run as administrator

Windows server task scheduler does not run. Asked 10 years, 10 months ago. Active 9 years, 4 months ago. Viewed 98k times. Improve this question. Under what user the bat file is set to run? It may not have the required permission. It wont show any errors but will not run. Add a comment. Active Oldest Votes. Improve this answer. Kevin Stewart Kevin Stewart 3 3 silver badges 3 3 bronze badges.

This guy should get a medal!!! Thanks to this answer I could make everything work. A simple workaround I found is this: you create another batch file which you should name something like "DummyCaller. However, if you call it this way, it works perfectly. Maybe someone could shed some light on that? Thanks so much! I have been up and down all the permission settings for my. Server Fault is a question and answer site for system and network administrators.

It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search.

I have a scheduled task that is running as USER. I have checked the box "Run with highest privileges" in the scheduled task properties. The task is a powershell script that, among other things, reboots the system. The script executes and runs normally, but as a scheduled task, it fails to reboot the system. Here is the kicker: When I manually run the script as USER using the exact same command line as what's in the scheduled task, the script still runs but this time it actually reboots the system.

The local Admins group has the right to shut down the system. Nothing in the event logs offers any clues. Why would the same script running under the same credentials work interactively but not as a scheduled task? Verify any commands which reference path are absolute, IE. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? This task did nothing except fire up cmd. Once this task had been created, I then logged in as an administrator and modified the task to fully do what I wanted. Including the option run as another user which you cannot set using the low end user. So in essence once the initial task is setup by the user it appears that you can use an admin account to change the options that cannot be changed with the low level user.

In addition it must be noted that any higher level user administrator can see and run all scheduled tasks including the low level user generated tasks.

Now if I can just figure out how to assign rights to allow non admin users to manage scheduled tasks, that would be great…. Actually I did the same as you, before reading this your blog post but the result was that the task didn't even run manually from both admin and non admin accounts.