Archived from groups: microsoft.public.windowsxp.customize (
More info?)
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
--
----------------------------------------------------------
http://www.uscricket.com
"Curt B" <CurtB@discussions.microsoft.com> wrote in message news:4D0448AF-D4EA-49D2-A05D-867B7EC27A8D@microsoft.com...
> You're welcome. I'm glad I could help.
>
> "Mark" wrote:
>
>> Thank you very much Curt that worked fine - Just the sort of answer I was
>> looking for
>>
>> "Curt B" wrote:
>>
>> > By default, Windows XP requires a password for a scheduled task. However,
>> > you may disable this with the following registry change:
>> >
>> > HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Lsa
>> >
>> > limitblankpassworduse
>> > Change the value in the Value Data box from 1 to 0
>> >
>> > Then, check the "Run only if logged on" box in the scheduled task.
>> >
>> > The task will now continue to run when the user periodically changes their
>> > domain password without the need to change the scheduled task password.
>> >
>> > Let us know if that gets you what you need.
>> >
>> > "Mark" wrote:
>> >
>> > > Ok heres the scenario. One of my users has a scheduled task that open up
>> > > spreadsheets every morning. This works fine apart from then his domain
>> > > password needs changing (every 30 days). Once he has changed the domain
>> > > password he needs to edit the properties of the scheduled task and change the
>> > > password manually.
>> > >
>> > > I have also re-created this problem on another pc running a different
>> > > scheduled task
>> > >
>> > > Windows XP sp1
>> > > AD Domain (2003)
>> > >
>> > > Any one have any ideas?
>> > >
>> > > Cheers