Log in or Sign up. You are viewing our forum as a guest. For full access please Register. I think it's pathetic that you can't use Task Scheduler without having to log on with a password. Anyone figured a work around for this? AceH ,. Log in or Sign up to hide this advert. This command is shipped in Windows for backward compatibility for NT 4. Its defaults are to schedule jobs to run as the Task Scheduler service account System by default. To access this tool, open a Command Prompt cmd.
This is done for security reasons and therefore, we strongly recommend you do not use a blank password if you want to run scheduled tasks. Having said that, it is possible to configure the operating system to allow executing tasks with a blank password. The following steps demonstrate how to modify this setting.
Once this option is disabled, Windows operating system will allow running a scheduled task without a password. Disadvantages of Disabling Password Passwords make your environment secure.
Configuring your computer to run scheduled tasks without passwords could potentially create security risks. Therefore, avoid disabling passwords on machines that are typically accessed by many users. Quick Links. Tutorial Videos. Industry Solutions.
If your task fails to run manually, the errors in the log file are the clues to what to do next. Always try to go back to your simple Command Prompt task that you created before to make sure the ST mechanism works properly - you know for sure that one works. Then apply your knowledge to get your new task working. You can change the task Properties to use your login account and password since you know it works properly on the Command Prompt task.
If you change your new task and choose to run it and are logged in with the same account, you should see your task run. When you are satisfied it is working properly, you probably don't want to have it interrupt you while you are logged in, so change the Properties back to use some other user account login that has a password that you created just to run your scheduled tasks.
This account has no password and is usually used for system oriented tasks but you will only be able to see it running when using Task Manager. If you try to manually run a ST like this, you will not see it open any window to run but you will see it running in Task Manager and in the log file.
If you think you want to see it actually run, change the Properties to use your account and password, troubleshoot the task, then change the Properties back and test it again. These kinds of tasks may run just fine, but you will only be able to tell by the log file, looking in Task Manager or the status columns in the tasks folder. If you temporarily change the task to use the same account and password you use to login, you will be able to watch it run.
Once you understand how to get a simple task like Command Prompt working and you know where the log file is and how to change the task Proprieties, you can work on your new or afflicted task and get it working. There are ways to work around some of the restrictions and requirements, but it is best to just use what you have and use it properly. A common problem with Scheduled Tasks is that there is no password on the account used to create the task or folks expect to "see" the task running when it is not assigned to their login and when theydon't see anything and think the task is not running.
That is not the way it works. The log file and Task Manager will tell you what is really going on. If you are used to not having a password on your account because you don't like to enter one when you login or you are the only user on your system, and decide to start using some STs, it is sometimes easiest to just assign a password to your account or just create a new XP user account with a password and use it for the STs.
You can assign a password to your account and still have your system set up to never prompt you for a password when you login but you should remember your password - or set up a new account just for your scheduled tasks.
0コメント