Changing Windows password wil stop scheduler to run.

[Guest]

In our organisation we like our users to change their password on a reular
basis. Those user running scheduled tasks like backupjobs will find their
tasks will not run. The status of the tasks shows "The scheduled task did not
run because an incorrect username or password was entered."

How can this be prevented?

 

[Pegasus \(MVP\)]

In our organisation we like our users to change their password on a reular
basis. Those user running scheduled tasks like backupjobs will find their
tasks will not run. The status of the tasks shows "The scheduled task did not
run because an incorrect username or password was entered."

How can this be prevented?

This is preventd by adopting stand server administrator
techniques: To run all scheduled jobs under dedicated
accounts whose passwords are very strong and do not
expire.

 

[Guest]

This is NOT an option, company rules...

This is preventd by adopting stand server administrator
techniques: To run all scheduled jobs under dedicated
accounts whose passwords are very strong and do not
expire.

 

[Yves Leclerc]

As most System Administrators, you need to have some special user account
that will not have a password expirations and will not allow the uses the
"login" with those accounts. This is part of the Group Policy system.

 

[-rwxrw-r--]

This is NOT an option, company rules...

Sorry, but you got it all wrong. Bill Gate$ rules and your company better
comply or else!

 

[Bob I]

Then the option you've left yourself with is, to tell your users they
need to update the password in the tasks if they expect them to run.

 

[Guest]

The following one-time setup will eliminate the need to manually reset the
password for each of your scheduled tasks each time you change your account
password.

1. Run Regedit and drill down to the subkey listed below. Then change the
registry entry as indicated.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\
limitblankpassworduse
itemtype = "REG_DWORD"
n = 0
2. Select "Properties" for each scheduled task.
3. Check the "Run only if logged on" box.
Each scheduled task modified as indicated in step #3 will now continue to
run when you change your account password without ever having to make a
change to the scheduled task again. You do not have to reset the scheduled
task password.

This process has two requirements:
1. The user must be logged in with the account specified in the scheduled
task's "Run as:" box.
2. The "Security" tab must be present in the scheduled task.

 

[Guest]

One more thing... Because the user must remain logged in for the scheduled
task to run, workstations in a corporate environment should be locked
(Windows + L) when unattended to prevent unauthorized access.

 

[Guest]

Thanks Curt,

This is what I am going to try. I hope it is the solution for the problem.

 

[Guest]

One more thing... Because the user must remain logged in for the scheduled
task to run, workstations in a corporate environment should be locked
(Windows + L) when unattended to prevent unauthorized access.

That is what we trie to teach users to be aware of ;-)

 

[Julian]

We always run our jobs as the SYSTEM user, no password but you can't log on
as the SYSTEM user so it's secure!