S
SilverFactor
Guest
Please file a bug with the product team. Here are the steps to reproduce the problem:
To prove that "Do not store password" causes the problem, do the following:
This seems like a bug in Windows. Please file a bug on the product team.
Thanks.
More...
- Run the Task Scheduler.
- Click "Task Scheduler Library" on the left panel to show the top-level task list.
- Click "Create Task..." on the Actions panel.
- Enter Name: test
- Select "Run whether user is logged on or not".
- Check "Do not store password. The task will only have access to local computer resources.". This is critical, this seems to cause the problem.
- Switch to the "Actions" tab.
- Click "New..."
- Enter Program/script: %windir%\system32\cmd.exe
- Enter Add arguments (optional): /c exit
- Click OK.
- Click OK.
- Click the newly created "test" task.
- Click "Run" on the Actions panel.
- Click "Refresh" on the Actions panel. Note that the task did not actually run, evidenced by the "Last Run Time" field not updating (it probably says 11/30/1999 12:00:00 AM) and the "Last Run Result" still says "The task has not yet run. (0x41303)". This proves that this is a bug.
To prove that "Do not store password" causes the problem, do the following:
- Double-click the "test" task in the Task Scheduler to edit it.
- Uncheck "Do not store password"
- Click OK.
- When prompted, enter the Windows account password and click OK.
- Click "Run" on the Actions panel.
- Click "Refresh" on the Actions panel. Note that the task did run, evidenced by the "Last Run Time" field updating and the "Last Run Result" field says "The operation completed successfully. (0x0)".
- Again, double-click the "test" task in the Task Scheduler to edit it.
- Check "Do not store password"
- Click OK.
- Click "Run" on the Actions panel.
- Click "Refresh" on the Actions panel. Note that the task did not run, evidenced by the "Last Run Time" field not changing.
This seems like a bug in Windows. Please file a bug on the product team.
Thanks.
More...