Windows 10 task scheduler changes domain users to local ones

[Guest Torben Schiffke]

Hello everyone,

 

I'm having a strange problem with the Windows 10 task scheduler. Following setup:

 

- Windows 10 pro workstation (fully updated) in a Windows 2012 domain environment

- domain administrator is logged in 24/7

 

If I first create a task which should run interactively under the domain administrators account everything is fine. As soon as I change eg. the trigger of the task, the task won't run the next time it should. I only get a 332 event from the task scheduler which states the task could not be executed because the user [LocalPcName]/Administrator was not logged in. While this is technically correct (I'm logged in as [Domain]/Administrator) the task should not be executed under the local administrators account in the first place.

 

If I edit the task and explicitly set the account to [Domain]/Administrator and then save everything is OK again.

 

So: Whenever I save a scheduled task (after the initial creation) without explicitly stating [Domain]/Administrator as the user account, the user account gets changed to the local administrator. I also see this, when I export the tasks before and after saving a trigger change: The User-IDs in the XML-file are different and they match the local and domain administrators respectively.

 

I already saw this question (Task Scheduler - Domain User Changes to Local User When Editing) and I am pretty sure the suggested workaround would work, but for me there is no way to rename the administrator accounts.

 

So: Am I doing something wrong or is this really a bug in the task scheduler UI?

 

Thanks in advance!

 

More...