Tag Info

New answers tagged


When you created the task what did you set under 'Security options'? If the user account is not to be logged in all the time then set this to 'Run whether user is logged on or not' and ticket the 'Run with highest privileges'. Ensure the user account users for this task has the same permissions as your testing account and check the'Run with highest ...


I would not recommend using the 1 minute resolution classes like Min01 unless you are running the agent on a 1 minute interval. That class will only be defined during that one minute. By default the agent runs every 5 minutes, and even with large policy sets a complete policy run usually completes within a minute. You might want to take a look at the ...


Yeah, totally, in that scheduled tasks run an an anonymous user unless you specifically tell it to run under a user account that has privileges to access the network. Usually you'll create a service-specific user account (sometimes just a generic EXAMPLE\ScheduledTasks account), set the scheduled task to run as that user, and give that user access to the ...


Stop Task Scheduler service (to prevent new tasks from starting). Wait for existing tasks to finish. Reboot. Profit ???


incrond (inotify cron daemon) behaves like cron but uses inotify as the triggering mechanism. This guide has some pretty comprehensive examples. An example incron entry for the case you described might be: /path/to/file IN_CLOSE_WRITE /path/to/your_script


If you are running Linux, as I assume you are, then you can rely on Linux inotify mechanism that notifies user-space processes when files change. LSyncd is one program built around that feature, which you can configure to execute arbitrary commands when files change.


This is perfect! It works better than Get-ScheduledTask since I am in a 2008/2012 mixed environment. I added a few lines to query AD and invoke this command against a group of computers. My goal was to disable the task of "Server Manager" opening every time a user logs in. Presto! all gone! $C=Get-ADComputer -SearchBase 'OU=Computers,dc=domain,dc=com' ...


Try add to the end of your script [taskkill /f /im "powershell.exe"] this will kill all "powershell.exe" processes. I don't know how to kill the current power-shell process (equivalent to [cmd.exe /c]). But it will do the trick.


Troubleshoot your task by running as the same user that your task is set up for. For instance, if you're logged in as JoeUser, but your task is running as local administrator, you would need to runas /user:administrator cmd and run your batch from there. There may be some difference in the path, environment variables or permissions which are causing ...

Top 50 recent answers are included