In earlier windows server versions (prior to 2016) it was possible to grant non-admin users the permission to run a scheduled task by doing following steps:

  1. Scheduled Task: run under system, execute script
  2. Give user read and execute rights on specific task under C:\Windows\System32\Tasks\

Now in server 2016 this doesn't work anymore. Do you know how to do it?

Thank you

related post, which didn't get answered, neither helped: Allow non-admin user to run scheduled task in Windows Server 2016

  • Are you getting an error? – spacenomyous Oct 31 '17 at 9:52
  • no, the task just doesn't show up in the task scheduler – n0rthclub Oct 31 '17 at 10:56
  • I was able to reproduce it. It only works if the assigned user is changed on the task or it is run from an admin CMD prompt. I however can see the task with my non-admin account using schtasks.exe /query. I haven't been able to find anything explicitly stating changes in the account permissions and/or session isolation. – spacenomyous Oct 31 '17 at 15:47
  • What's the end goal of providing access to the scheduled task? Is it to get around UAC and running an application as administrator? – Nixphoe Apr 16 '18 at 14:48
  • The goal is to let less priviledge user run admin tasks. a Task runs a script (from a secure location and signed) which for example changes the primary dns server – n0rthclub Apr 24 '18 at 7:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.