Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Scheduled Tasks not running - XP Pro

2 views
Skip to first unread message

Bob S

unread,
Jul 8, 2004, 1:33:36 PM7/8/04
to
I have set up 2 Scheduled Tasks in XP Pro which have never run. The reason
given in the scheduler for their not running is:

"The scheduled task did not run because no user password was entered."

Could someone tell me how to tell it not to ask for a user password or tell
me how to enter it in my bat file?

Thank you.


David Candy

unread,
Jul 8, 2004, 1:47:38 PM7/8/04
to
You enter your password and account in the task's properties. If the account doesn't have a password then create an account with one to run tasks. You won't see it run.

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

"Bob S" <drbo...@nospam.com> wrote in message news:%23Tst2GR...@TK2MSFTNGP10.phx.gbl...

Malvern

unread,
Jul 8, 2004, 3:44:31 PM7/8/04
to

"Bob S" <drbo...@nospam.com> wrote in message
news:#Tst2GRZ...@TK2MSFTNGP10.phx.gbl...
This is a reply I saved from almost a year ago. May be info you need.

Malv


From: "Nicholas" <mrxp...@nospamyahoo.com>
Subject: Re: Scheduled Tasks Won't Run W/O Password
Date: Monday, July 28, 2003 1:02 PM

Scheduled Tasks Cannot Run with a Blank Password
http://support.microsoft.com/default.aspx?scid=kb;en-us;310715

Visit http://www.kellys-korner-xp.com/xp_s.htm and scroll down to:

"Scheduled Tasks - Applying/Running tasks without a password"

[Courtesy of Kelly Theriot, MS-MVP]

HOW TO: Troubleshoot Scheduled Tasks in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308558

HOW TO: Schedule Tasks in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308569


--
Nicholas


David Candy

unread,
Jul 8, 2004, 4:05:53 PM7/8/04
to
Don't you think you should mention the implications of this "tweak".

It does far more than just allow tasks to run without a password.

It should not be used.

Accounts: Limit local account use of blank passwords to console logon =
only
Computer Configuration\Windows Settings\Security Settings\Local =
Policies\Security Options

Description
Determines whether remote interactive logons by network services such as =
Terminal Services, Telnet, and FTP are allowed for local accounts that =
have blank passwords. If this setting is enabled, a local account must =
have a nonblank password to be used to perform an interactive logon from =
a remote client.

Default: Enabled

Notes

a.. This setting does not affect interactive logons that are performed =
physically at the console.=20
b.. This setting does not affect logons that use domain accounts.=20
c.. It is possible for applications that use remote interactive logons =
to bypass this setting.=20
For more information, see:

a.. Security Configuration Manager Tools

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

"Malvern" <thisis@fak> wrote in message news:cck86v$p7q$0...@216.39.176.78...

Alex Nichol

unread,
Jul 9, 2004, 12:03:05 PM7/9/04
to
Bob S wrote:

>I have set up 2 Scheduled Tasks in XP Pro which have never run. The reason
>given in the scheduler for their not running is:
>
>"The scheduled task did not run because no user password was entered."

Task scheduler by default needs the user to be logged on with a
password. To remove this requirement:

If it is XP Pro, run Control Panel - Admin Tools - Local Security
Policy. In Local Policies - Security Options d-click in the right pane
on
'Accounts: Limit local account use of blank passwords. . . .' and set to
Disabled.

If it is XP Home, which does not have this tool, see
http://www.kellys-korner-xp.com/xp_tweaks.htm
Line 67, left, 'Run Scheduled tasks without PW - Home'

--
Alex Nichol MS MVP (Windows Technologies)
Bournemouth, U.K. Al...@mvps.D8E8L.org (remove the D8 bit)

Bob S

unread,
Jul 9, 2004, 12:57:34 PM7/9/04
to
David, it appears that you find changing this setting dangerous. Could you
explain the reason a bit more? I did not quite catch it.

"David Candy" <da...@mvps.org> wrote in message
news:erG$9bSZEH...@TK2MSFTNGP09.phx.gbl...

David Candy

unread,
Jul 9, 2004, 1:40:23 PM7/9/04
to
Anyone who knows a username can log in without a password remotely. Have you renamed your inbuilt administrator account? Is it password free like most? Can they guess your name?

So if you want the world to be able to login via Remote Desktop, Terminal Services, FTP server, Telnet, or the RUNAS command (treated as remote logon like scheduled tasks) then turn this off.

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

"Bob S" <drbo...@nospam.com> wrote in message news:eg2BZXdZ...@TK2MSFTNGP12.phx.gbl...

Bob S

unread,
Jul 9, 2004, 9:15:17 PM7/9/04
to
David, thanks for your expert advice. I have two questions.

1. Would I be correct in restating what you have said below with the
following? "As long as I do NOT turn this off, even if a person could guess
my new administrator login name, they would NOT be able to login via Remote
Desktop, Terminal Services, FTP server, Telnet, or the RUNAS command.
However, if I turn it off, he could." Right?

2. I set up a new account (as you recommended yesterday) and gave that
account a password. Further I set up my two scheduled tasks on that
account. One of them was to run a few minutes ago, and it did not. The
comment in the status field is "Could not start." Can you help me figure
out why it could not start?

Thank you for all of your help.
Bob

"David Candy" <da...@mvps.org> wrote in message

news:eGLVVvdZ...@TK2MSFTNGP11.phx.gbl...

David Candy

unread,
Jul 9, 2004, 11:38:59 PM7/9/04
to
1. Only if they can guess your password. But if you don't have one they can't logon. Each specific service needs to be allowed as well - telnet is off unless turned on, same for remote desktop.. Not sure if it affects the standard admin ways of getting into another computer as don't have a network to test.
2. Disable TS on advanced menu then view the log file on that same menu.

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

"Bob S" <drbo...@nospam.com> wrote in message news:%23Roqfth...@TK2MSFTNGP11.phx.gbl...

David Candy

unread,
Jul 9, 2004, 11:44:09 PM7/9/04
to
I have no objection to anyone using it. I just think the implications need to be spelt out if advising someone to use it.

Eventually someone will start port scanning looking for services and trying them with admin/nopwd.

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

"Bob S" <drbo...@nospam.com> wrote in message news:%23Roqfth...@TK2MSFTNGP11.phx.gbl...

Bob S

unread,
Jul 10, 2004, 12:32:23 AM7/10/04
to
David, this is what the log said.
"8pm UpdateStephOL & Bkup BobData.job" (8pm UpdateStephOL & Bkup
BobData.bat) 7/9/2004 8:00:00 PM ** ERROR **
The attempt to retrieve account information for the specified task failed;
therefore, the task did not run. Either an error occurred, or no account
information existed for the task.
The specific error is: 0x80070534: No mapping between account names and
security IDs was done.

A bit more data: Before I scheduled the task, I logged off as my normal
name and logged back on in this new account (which has a password). At the
end of scheduling the task, I believe I was asked to enter the password for
the new account twice - which I did. Then I logged back off and back on in
the account I use most of the time.

What do I need to do now? Thanks again.
Bob


"David Candy" <da...@mvps.org> wrote in message

news:OQeR19i...@TK2MSFTNGP10.phx.gbl...

Alex Nichol

unread,
Jul 10, 2004, 1:21:12 PM7/10/04
to
Bob S wrote:

>I have set up 2 Scheduled Tasks in XP Pro which have never run. The reason
>given in the scheduler for their not running is:
>
>"The scheduled task did not run because no user password was entered."

Task scheduler by default needs the user to be logged on with a

David Candy

unread,
Jul 10, 2004, 1:54:44 PM7/10/04
to
http://www.google.com.au/search?q=+site:support.microsoft.com+0x80070534&num=100&hl=en&lr=&ie=UTF-8&safe=off&filter=0

Do these seem similar to your configuration.


--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

"Bob S" <drbo...@nospam.com> wrote in message news:OTzlobjZ...@tk2msftngp13.phx.gbl...

0 new messages