--LastExec
What parameters should be used there after -LE?

just want to know if the task is enabled or disabled yet, if it gets disabled i want to recieve a critical.

any ideas?

Hi how can I can get the name of the ok Tasks like the $RunningTask.Name.
Thanks

We have configured the script 'check_ms_win_tasks' to monitor tasks scheduled in the Task Scheduler of our Server. The output of the Script is as expected. It shows Total tasks, OK tasks, Failed tasks, Running tasks correctly. But it is not giving 'Critical Alerts' for the tasks which are running for long time or that are running indefinitely. We want to know how to set 'Critical Alerts' for tasks that are running for long time (more than 5 mins).

Thanks you very much for this, it’s really usefull for me and it’s helping me a lot.

In the other hand, I have a question, I’m having some false positives in tasks that never has started, showing that info, for example:

” {Taskname: “Copia Abril” (Author: DOMAIN\USER)(Exitcode: 1)(Last runtime: 12/30/1899 00:00:00)} {Taskname: “Copia Agost 17″ (Author: DOMAIN\USER)(Exitcode: 1)(Last runtime: 12/30/1899 00:00:00)}” ”

There are some option for ignore scheduled tasks that has never started? there are some tasks, that are started and ended correctly but it returns "Exitcode: 1", so, Nagios show me a fail:

"1 / 2 tasks failed! {Taskname: "Copia Biostar" (Author: DOMAIN\USER)(Exitcode: 1)(Last runtime: 10/13/2016 07:00:00)}"

so, it's possible to admit the exit code: 1 in ok tasks?

In https://outsideit.net/monitoring-windows-scheduled-tasks/, section "How to monitor your scheduled tasks?":

• Link "define the script like this" to https://docs.nsclient.org/tutorial/#external-scripts
• For item 2, add the INI section [/settings/external scripts/scripts] on top to guide the reader to the correct section
• Consider defining a wrapped script, see https://docs.nsclient.org/howto/external_scripts/#wrapped-scripts

As request by JDC, add an option to display the full task paths in the output.

Hi,

Thanks for your script! I'm using it to monitor 2 machines and the script works great. However I would like to monitor a third machine - but only the tasks in a special folder (right below the \ root). However it seems that -IF works as a wildcard and I cant get it to JUST report the specific folder. Stepts to reproduce (on Server 2016, I think other OS should have the same default foders under the Microsoft tree):

• Create a folder named App right below the root
• Place just 1 Task there and run it one time
• us -IF "APP"

I get 10 Tasks geported - because there are 9 Tasks under Microsoft\Windows\AppID and other folders that match App. Trying with \APP and so on didn't get the 1 task to display. Maybe I don't see the right way to do this?

Sometimes this plugin goes to critical state because the exit code of the task is -2147020576. I think this happens when the task is running as it last only a few minutes.

This is the output:

1 / 1 tasks failed! {Taskname: "TASK" (Author: DOMAIN\User)(Exitcode: -2147020576)(Last runtime: 2/12/2018 10:05:01 PM)}

The error: 0x8004131F is alerting all the time however it means that: "Launch request ignored, instance already running", the script entry below will fix this for that specific result:

<                 If ( $ObjTask.LastTaskResult -eq '0'-or $ObjTask.LastTaskResult -eq '0x00041325' -and $ObjTask.Enabled ) {

>                 If ( $ObjTask.LastTaskResult -eq '0x8004131F'-or $ObjTask.LastTaskResult -eq '0'-or $ObjTask.LastTaskResult -eq '0x00041325' -and $ObjTask.Enabled ) {

When a task was just created and was still never run, its 'LastRunTime' is set to a date far away in 1989 which means "never". Such task should be assumed "OK" ; its 'LastTaskResult' remains undefined I think.
Line 447, I would add :
-or $ObjTask.LastRunTime -lt (get-date 2000-01-01)
NB: I have not found any "clean" way to get the value of this '1989' date, so I use 2000 which seems reasonable but somewhat 'dirty'.
Thanks for your script
Nicolas

There is an issue with the script.
Tasks that run under another user are not included in the checking process, they simply are invisible to the script.

how can one fix this?

Hello,

When I try to execute this command
check_nrpe -H 192.168.0.30 -p 5666 -c check_ms_win_tasks -a '-H 127.0.0.1 -ET Microsoft'

I get : Failed to execute check_ms_win_tasks: 87: Incorrect Parameter

If I add -n:
check_nrpe -H 192.168.0.30 -n -p 5666 -c check_ms_win_tasks -a '-H 127.0.0.1 -ET Microsoft'

I get:
CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected).

What I've done:

Add into NSClient.ini:

[/settings/external scripts/scripts]
check_ms_win_tasks=cmd /c echo scripts/powershell/check_ms_win_tasks.ps1 $ARG1$; exit $LastExitCode | powershell.exe /noprofile -command -

Created a new command in the CCM named "check_ms_win_tasks" with this command "$USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -t 60 -c check_ms_win_tasks $ARG1$"

Disable UAC and DEP on the Windows Server, allow execution of script with: set-executionpolicy remotesigned.
When I execute the script in local, it works.

Can you help me ?

Thank you !