E
EJsquared
I have set up a scheduled task on Windows Server 2012 R2 Standard, and it's failing ONLY when I set the trigger to repeat or stop task. It doesn't matter if it is a one time, daily, weekly, or monthly trigger. It can be multiple triggers or a single trigger. It will fail when run on schedule or on demand with a specified file not found 0x80070002 error. And the event log entry is kind enough to not tell me which specified file it is unable to find.
The task runs fine under my own domain account with local administrative rights. And without either of these settings configured, the task will run fine under the managed service account credentials - on schedule or on demand, with a single trigger or multiple triggers.
The task runs a powershell script, using a single action which includes the full path to powershell.exe, the arguments include the full path to the script file, and all paths inside the script are fulling qualified.
It is currently set to run using a group managed service account (gMSA). The account has local administrative privileges, has rights to log on as a batch job, has full rights to all file locations, and without the repeat or stop task settings configured, runs successfully.
I have tried creating the task manually in the GUI, creating it through the schtasks command-line utility, and the scheduled tasks powershell cmdlets. All exhibit the same behavior.
Continue reading...
The task runs fine under my own domain account with local administrative rights. And without either of these settings configured, the task will run fine under the managed service account credentials - on schedule or on demand, with a single trigger or multiple triggers.
The task runs a powershell script, using a single action which includes the full path to powershell.exe, the arguments include the full path to the script file, and all paths inside the script are fulling qualified.
It is currently set to run using a group managed service account (gMSA). The account has local administrative privileges, has rights to log on as a batch job, has full rights to all file locations, and without the repeat or stop task settings configured, runs successfully.
I have tried creating the task manually in the GUI, creating it through the schtasks command-line utility, and the scheduled tasks powershell cmdlets. All exhibit the same behavior.
Continue reading...