I'm trying to set up scheduled tasks that run every hour, regardless of who is logged into the computer. I also want to create some other scheduled tasks that start off disabled. Essentially, Task A will disable itself and trigger Task B at the next startup once certain criteria are met. Then, when Task B runs, it will disable itself to enable Task C for every user login. I've managed to get it working partially through Intune, but the issue arises when different users log in; for example, if Bob installs the tasks and logs out, Sarah won't see them in her task scheduler. I'm open to any suggestions or alternative methods to accomplish this. Thanks!
5 Answers
It sounds like your scheduled task isn't being created under the SYSTEM context, which is why it's not available for all users. You'll want to ensure that the tasks are set to run under that account so they work regardless of who's logged in.
Make sure to create the scheduled tasks to run under the /SYSTEM account. Just a heads-up, it may have some limitations when it comes to accessing parts of the Windows user interface.
Have you thought about using a computer group policy task instead? That's a more traditional method, and it might solve your issues since I haven't used Intune much myself.
I tackled something similar using NSSM to create a service that runs a PowerShell script. Lock down the script folder so users can't mess with it, and run it as a service account. My main service checks for new scripts regularly and manages them automatically, which could be a way to simplify your deployments.
If you install the tasks as SYSTEM and set the running account to BUILTINUsers, that should help you get around the visibility issue for different users.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures