command linewindowswindows task scheduler
Is it possible to make a new job in the Windows Task Scheduler using the Command Prompt when a normal user is logged in and they don't have administrator privileges?
Is there a reliable way for all users to make a simple job in the scheduler using the Windows Command Prompt?
The simplest solution would be to configure said scheduled task to run under an Administrator account. You do not need to use the same account as the usually-logged-on user – simply provide different credentials when creating the task.
If you do not want "Administrator" to have a password, you could just create a dedicated account just for the scheduled task. (A limited User account will work as well, if you apply the fix below.)
The shutdown.exe program needs SeRemoteShutdownPrivilege to run, instead of the usual SeShutdownPrivilege – my guess is that it uses the same RPC for shutting down both local and remote machines. (This would explain the need for a password, too – by default, only console logins are exempt, which obviously does not include RPC.)
You can grant SeRemoteShutdownPrivilege through secpol.msc → Local Policies → User Rights Assignment, by editing the "Force shutdown from remote system" entry.
INTERACTIVE.BATCH.shutdown.exe does not allow the /t parameter to be used along with either /l (log off) or /h (hibernate) for some reason.
You can make the task execute shutdown /h (i.e. without /t) to hibernate. If you want a window wherein you can cancel the scheduled hibernation (using Ctrl+C), make the task execute cmd.exe instead with the following arguments:
/c "timeout /t 120 /nobreak && shutdown /h"
Remember to use && and not &, or else the second command (shutdown /h in this case) will run irrespective of whether the first one (timeout /t 120 /nobreak) was cancelled or not.
Best Answer
Yes, non-admin user accounts can create scheduled tasks, however they will be limited to running under the user’s credentials (i.e., no admin privileges). If you want to create a task that requires admin privileges with a non-admin account, then an admin-account holder must either enter their credentials at the command-line when creating the task or else at the credentials dialog that pops up when the task is executed: