"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.
--
----------------------------------------------------------
'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...
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
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...
>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)
"David Candy" <da...@mvps.org> wrote in message
news:erG$9bSZEH...@TK2MSFTNGP09.phx.gbl...
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...
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...
"Bob S" <drbo...@nospam.com> wrote in message news:%23Roqfth...@TK2MSFTNGP11.phx.gbl...
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...
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...
>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
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...