Home / server / Questions / 782458
Accepted
Omnomnomnom
Asked: 2016-06-08 04:17:59 +0800 CST

Scheduled task runs with exit code 0, but powershell script is not always executed

  • 772

The situation

In our organisation I made a GPO that creates a scheduled task. This task triggers at logon of two user accounts.

It executes a powershell script that changes the DNS servers for the network connection. (To block some websites for these users, using dnsmasq. I know this is not a bulletproof solution, but its good enough.)

The action for the scheduled task is this command:

C:\Windows\System32\WindowsPowerShell\v1.0\Powershell.exe

And these are the parameters:

-ExecutionPolicy Bypass –NoProfile –Command "& {C:\ProgramData\ORGNAME\scripts\SetDNS.ps1}" > C:\ProgramData\ORGNAME\scripts\SetDNS.log

As you can see, the output gets sent to a log file.

This is the content of the script:

$wmi = get-wmiobject Win32_NetworkAdapterConfiguration -filter "ipenabled = 'true'"
foreach($adapter in $wmi)
{
    if($adapter.description -NotLike "*VMware*")
    {
        $adapter.SetDNSServerSearchOrder("XXX.XXX.XXX.XXX")
    }
}

invoke-expression -command "c:\windows\system32\ipconfig /flushdns"

The problem

The problem is that this works fine, approximately 9 out of 10 times. When it doesn't work, the task scheduler still reports exit code 0, but it seems the script does not even begin to execute because, nothing happens and the log file is not created.

Some extra info

  • The task runs under the SYSTEM account
  • It runs with highest privilleges
  • When the task is ran on demand it works fine
  • All computers run Windows 7 enterprise (x64)

Some things i've tried

  • I thought maybe the task scheduler was triggering the script too fast and some things might not yet have initialized so i tried setting a 30s delay.

  • Re-running the task every 5 minutes for 15 minutes.

  • Restarting the task when it fails, this obviously doesn't work, since powershell.exe seems to return error code 0.

scheduled-task powershell

2 Answers

  1. Best Answer

    I think the exit code task scheduler is reporting is for running powershell.exe not your script.

    Try changing it to this:

    -ExecutionPolicy Bypass –NoProfile –Command "& {C:\ProgramData\ORGNAME\scripts\SetDNS.ps1; exit $LastExitCode}" > C:\ProgramData\ORGNAME\scripts\SetDNS.log

    $LastExitCode has the exit code of the your script, you have to bubble it up one level to the task scheduler.

    It would also be a good idea to add some error handling to your script and use Exit statements to set the actual exit codes.

    • 8

  2. Remove the -Command from your script parameters and instead use -File . Command is meant to be used when you are entering powershell commands but you have a script file instead.

    Details here

    • 1