schtasks - access is denied

Question

_{Monday, February 13, 2012 3:12 PM | 1 vote}

I'm starting to pull my hair out over the use of schtasks, I haven't had such trouble with something so simple in ages.

I'm trying to create a scheduled task on a 2008 machine via either command line or a remote job dropped by Altiris.

Every single time I use schtasks I get an access is denied error.

To make this clear: I am not using UAC, the command prompt appears prefixed as "administrator", the user is an administrator on the machine in question checked via a GPResult.

If I load the task scheduler GUI and import an XML file to create a scheduled task it works perfectly, under the SAME user context. If I then try to run schtasks in a command line on the same server, using the same XML file it fails with access is denied. This is literally incredible.

Can someone give me a succint, to the point answer about why this utterly awful application can't do what it's supposed to do even with Domain Admin rights and what I can do to make this work? If my tone in this message implies I'm annoyed, it's because I am and I make no apologies what so ever.

Logically this makes no sense to me at all, that I can do something via the GUI and then not via the command line under the same context.

Thanks in advance.

Paul

All replies (1)

_{Tuesday, February 14, 2012 9:57 AM}

Hi,

Please try to provide Everyone group Full permission on the "C:\windows\Tasks" folder.

Whether you are using some parameters in your command or not? Please double check the following article.
How to use Schtasks.exe to Schedule Tasks in Windows Server
http://support.microsoft.com/kb/814596

Runs this command with the permissions of the specified user account. The default is the permissions of the current user of the local computer. The /u and /p parameters are valid only for scheduling a task on a remote computer (/s). The permissions of the specified account are used to schedule the task and to run the task. To run the task with the permissions of a different user, use the /ru parameter. The user account must be a member of the Administrators group on the remote computer. Also, the local computer must be in the same domain as the remote computer, or must be in a domain that is trusted by the remote computer domain.

More information:
http://technet.microsoft.com/en-us/library/cc772785(WS.10).aspx

Regards,
Dollar Wang
Forum Support
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send
your feedback here

Technology changes life……