mm said:
How to use Scheduler Advance Options if you have no windows password?
Leave the AT service (the 'at' command) configured with its default of
using the System account. You cannot log into the System account and
why no login credentials are required to use it OTHER than you must be
an admin-level user at the time you define the 'at' task.
I have windox XP Home SP3 and expect to soon have XP Pro
I've never bothered with using a Home edition of any version of Windows.
It may have restrictions that do not apply in the uncrippled versions of
Windows.
If the Advanced -> AT Service Account menu lets you choose the account
under which commands issued using the 'at' command then leave it at the
default of using the System account. If you pick a different account,
you will need to provide the login credentials to that other account to
prove you have permission to use that other account. Even if you pick
your own account, remember that tasks can run WITHOUT you being logged
in so they still have to know that they have permission by the account
owner to run under that account. A blank password means you can never
verify that the person defining the scheduled task has permission to use
that account.
It seems in order to used the advanced features of the Scheduler, I
have to enter my login password. I tried to just create a new
password where it says Set Password on the Task tab of the scheduled
item screen, but it ignored that.
All tasks defined using the GUI for Task Scheduler require an account
with its login credentials. Tasks defined therein cannot be defined or
executed without the proper login credentials.
If you want to run a scheduled task where you don't need to supply login
credentials then use the 'at' command in a command shell. You must be
logged under an admin-level account to schedule tasks using the 'at'
command. It has far less features than tasks defined using the GUI for
Task Scheduler.
For help, run in a command shell:
at /?
I don't want to have to enter a password to get into Windows, and I
don't see what that has to do with the scheduler anyhow.
Then you cannot schedule tasks under that account. The scheduled task
runs under the privileges of the account you defined for it to execute
under. To verify you have permission to use that account requires you
provide the valid login credentials for it. Just because you are the
only user of that instance of Windows doesn't obviate that Windows was
designed to be a multi-account OS.
Since you choose to let anyone log into your host that has access to it
(physically at the computer or remotely), you can still define a
non-blank password for your account but not bother with the login screen
at all. Define a non-blank password for your account. Then configure
Windows to automatically login using that account with the pre-supplied
login credentials. Then when you power up your computer, Windows will
load and automatically log into your account. Anyone walking up to your
computer can do the same just like they did when you had a blank
password just by hitting the Enter key.
It's your choice if you want to toss the security included in NT-based
versions of Windows but don't expect Microsoft to do the same. If you
want to run scheduled tasks then you need non-blank login credentials
for the accounts under which they execute - unless you choose to login
under an admin-level account and use the 'at' command to define
scheduled events (and only if under the System account since specifying
any other account will require non-blank login credentials).
