Thoughts from the EPS Windows Server Performance Team
Useful Microsoft Blogs
Hello AskPerf! This is going to be a quick blog post to alert you to some of the changes in Windows 8 and Server 2012 as it relates to Task Scheduler. Most of these changes are a welcome addition like using PowerShell to manage Task Scheduler. There were however, some features removed that could affect you in your environment. Those include the following:
For the “Send an e-mail” action, you can use the PowerShell “Send-MailMessage” cmdlet in its place.
For the “Display a message” action, you can use the built-in msg.exe command line tool. Help file output below:
Since the “AT” command has been deprecated, you can use schtasks.exe instead. If you need a command prompt launched as the Local System account, you can use “PSEXEC.EXE -s“. Psexec.exe is part of the PsTools, and can be downloaded here.
For more information on what else has been changed since Windows Vista, check out the following MSDN article:
What’s New in Task Scheduler
For more information on the schtasks.exe command, check out the following AskPerf Blog:
Two Minute Drill: The Schtasks command
-AskPerf Blog team
So, has the "at" command been deprecated or removed? I see it tells you to use schtasks instead, but if it's merely deprecated, it should surely still function if you give it a full and valid command to run?
It actually appears that "at.exe" was deprecated in Server 2003:
technet.microsoft.com/.../cc725744%28v=ws.10%29.aspx - it just didn't give any warnings in the output back then.
I do see lot of 2012 server getting restarted if the task failed with event 104 ,is it due to setting done or when any task fails it is restarting...!
@Adam: It has been removed. If you try and schedule a task using AT, it will return "The request is not supported."
@Privin.P: I'm not aware of any failed task restarting a Server. More information is needed.
I've seen two posts on StackOverflow indicating that Task Scheduler on Win 2012 does not accurately report Return Codes from executable actions in the TaskScheduler EventID 201 events. The Return Code is still propogated to Task Last Run Result although
has '0x8007' prefix. Anyone else noticed this?
Return code of scheduled task prefixed with 0x8007000 in list view, registered as 0 in the event log. I have the same issue with windows 8 pro x64...