Is there a way to know the source and legitimacy of the tasks in the task scheduler in windows server 2008 and 2003? Can I check if the task was added by Microsoft (ie: from sccm) or by a 3rd party application?
For each task in the task scheduler, I want to verify that the task has not been created by a third party application.
Task 1: Stick The Landing
Task 2: Chop Stack
Task 3: The Nutstacker
Task 4: Johnny Applestack
Task 5: Back Flip
Task 6: Cantagious
Task 7: Stack Attack
Task 8: Face The Cookie
Task 9: A Bit Dicey
Task 10: Double Trouble <-- You all love it
Total time: 235 seconds
youtube link:
http://youtu.be/At26nbMJk2s
Thanks for watching!
Task 1: Stick The Landing
Task 2: Chop Stack
Task 3: The Nutstacker
Task 4: Johnny Applestack
Task 5: Back Flip
Task 6: Cantagious
Task 7: Stack Attack
Task 8: Face The Cookie
Task 9: A Bit Dicey
Task 10: Double Trouble <-- You all love it
Total time: 235 seconds
youtube link:
http://youtu.be/At26nbMJk2s
Thanks for watching!
Can someone give me a use case for setting up a Windows Server 2008 Task Scheduler task (we'll call this "test") that completes (action completed is task=201) with an error (result code=2)?
I am looking at consolidating all of our scheduled tasks that run on various servers (Win 2008 R2) within our domain on to one "Task Scheduling Server". I am a developer so I'm not even sure if this is a good idea or just a maintenance headache. One of our Network guys copied some of the tasks I monitor over to the new server and asked me to test them.
I get the following error in the Scheduled Task history when I try to run a task:
Task Scheduler successfully completed task "\Restart Tomcat" ,
instance "{264b4620-5f3b-6c5f-a6cb-1625a7fa57de}" ,
action "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.EXE"
with return code 1.
The scheduled task is configured as follows:
Name: Restart Tomcat
User: DOMAIN\tomcat.restarter
Triggers: Daily
System is Windows 2008 R2
I have a task scheduler task with a trigger to run at system startup, and have set the Delay to 20 minutes, however the task runs immediatley on system startup and ignores the 20 minute delay.
There are other triggers, but it is the boot trigger which is at fault by ignoring the delay.
Triggers section of the exported task follows.
<Triggers>
<CalendarTrigge
I have a shell script called run.sh. In it, I may call other shell scripts like:
./run_1.sh
./run_2.sh
.........
If I call the script by ./run.sh, I have found actually it will invoke different tasks inside the script sequentially with different PIDs(i.e., run_1.sh will be a task and run_2.sh will be another task).
Task Management Applications or TODO Apps helps a lot in organizing all the key activities or task in an easy and efficient way.