Scheduled Tasks

[mctiger]

Hi,
If you want to use this,Why do you need a password for it to work?
If left blank,the task may not start it states.
I am the administrator if that helps.
thanks in advance.
Have sence,patience,and self-restrain,and no mischief will come.

 

[Sharon F]

Hi,
If you want to use this,Why do you need a password for it to work?
If left blank,the task may not start it states.
I am the administrator if that helps.
thanks in advance.
Have sence,patience,and self-restrain,and no mischief will come.

I think the user name/password requirement is to block unauthorized
accounts from scheduling a task that could effect the system on a global
basis. XP comes from the NT branch of the Windows family. Security is
emphasized more and this is one example of that.

MVP Kelly Theriot has a workaround on her site for the password
requirement. I've never tried it but it may do what you want. Scroll down
to "Scheduled Tasks" on this page to read about the required changes to
accomplish this.

 

[mctiger]

Hi,
Can you please post MVP Kelly's Theriot web site?
This way I can check out the information that you provided.
Thanks again.

I think the user name/password requirement is to block unauthorized
accounts from scheduling a task that could effect the system on a global
basis. XP comes from the NT branch of the Windows family. Security is
emphasized more and this is one example of that.

MVP Kelly Theriot has a workaround on her site for the password
requirement. I've never tried it but it may do what you want. Scroll down
to "Scheduled Tasks" on this page to read about the required changes to
accomplish this.

Have sence,patience,and self-restrain,and no mischief will come.

 

[Rick \Nutcase\ Rogers]

Hi,

From MVP Kelly (a workaround):

For Pro: Start/Control Panel/Administrative Tools/Local Security
Policy/Local Policies/Security options.
In the right hand pane (third down). Accounts: Limit local account use of
blank passwords to console logon only. This is enabled by default, disable
it.

For Home: Backup your registry before modifying. Start/ru nregedit, locate
the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Value name: limitblankpassworduse
Type: REG_DWORD
Data: 0 (disabled) 1 (enabled)

It is enabled by default. Disable it (set the value to 0) and scheduled
tasks should run.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[Sharon F]

Can you please post MVP Kelly's Theriot web site?
This way I can check out the information that you provided.
Thanks again.

Sorry! I pulled up the page and looked it up before giving the reference.
Then forgot to paste the link. Anyhow, main page:
http://www.kellys-korner-xp.com/xp_abc.htm

Schedules Tasks is on the "S" page:
http://www.kellys-korner-xp.com/xp_s.htm

 

[David Candy]

But 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.
b.. This setting does not affect logons that use domain accounts.
c.. It is possible for applications that use remote interactive logons to bypass this setting.
For more information, see:

a.. Security Configuration Manager Tools

 

[Sharon F]

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

It should not be used.

Some questions are a tough call in these groups. A question is asked and
there is a way to accomplish what is desired. Do you hold back the info or
not? Is the change worth it in the long run? The individual user needs to
make that decision.

Thanks for pointing out some important details regarding this particular
area and change method. Anything that alters the security layers should be
looked at very closely before implementing.

 

[David Candy]

It should be given with a reading of the riot act. Remote desktop is one vector. Consider how many computers have the admin account called Administrator without a password.

 

[mctiger]

Hi,
I tried what you said. I received a box instead.
Snap-in failed to initialize
Name:Group Policy
CLSID( 8Fc0B734-A0E1-11D1-A7D3-000F87571E3)
What does this mean????
How can I fix this also?
Thanks in advance.
Thanks for all the responses also.

Hi,

From MVP Kelly (a workaround):

For Pro: Start/Control Panel/Administrative Tools/Local Security
Policy/Local Policies/Security options.
In the right hand pane (third down). Accounts: Limit local account use of
blank passwords to console logon only. This is enabled by default, disable
it.

For Home: Backup your registry before modifying. Start/ru nregedit, locate
the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Value name: limitblankpassworduse
Type: REG_DWORD
Data: 0 (disabled) 1 (enabled)

It is enabled by default. Disable it (set the value to 0) and scheduled
tasks should run.

Have sence,patience,and self-restrain,and no mischief will come.

 

[Rick \Nutcase\ Rogers]

Hi,

Which step did you try?

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[David Candy]

Type in Help
Snap-in failed to initialize

while online.

 

[Carrie Garth]

| | Hi, I tried what you said. I received a box instead.
| Snap-in failed to initialize
| Name:Group Policy
| CLSID( 8Fc0B734-A0E1-11D1-A7D3-000F87571E3) <SNIP>

See the following Microsoft Knowledge Base article:

KB826282 - "Snap-in Failed to Initialize" Error Message When You
Open Microsoft Management Console
http://support.microsoft.com/default.aspx?Product=winxp&scid=kb;en-us;826282

 

[mctiger]

Hi,

Which step did you try?

Hi,
I followed the xp pro directions.
Then went to
KB826282 - "Snap-in Failed to Initialize" Error Message When You
Open Microsoft Management Console
http://support.microsoft.com/default.aspx?Product=winxp&scid=kb;en-us;826282

This was no line for environment variable. So I added it in with the
path %System Root%system root;%System Root%;%system Root%\system32\WBE

After that I ok both boxes and exited.
Then went to Local Policies/security again,But still get the same
message.Snap-in failed to initialize.
What else can I do???
I typed in the help box=snap-in failed to initialize.
It showed options but no fixes.

Have sence,patience,and self-restrain,and no mischief will come.

 

[mctiger]

Hi again,
Is there a way to reinstall this program? If so how?
Under help about console= Microsoft Management Console 2.0 Version
5.1(Built2600.xpsp2.030422-1633:Service Pack1 Physical memory
available to windows: 259,636 KB.
I am trying to give the most info. to help me with this problem.
I hope this helps.
Thanks again.

Hi,
I followed the xp pro directions.
Then went to
KB826282 - "Snap-in Failed to Initialize" Error Message When You
Open Microsoft Management Console
http://support.microsoft.com/default.aspx?Product=winxp&scid=kb;en-us;826282

This was no line for environment variable. So I added it in with the
path %System Root%system root;%System Root%;%system Root%\system32\WBE

After that I ok both boxes and exited.
Then went to Local Policies/security again,But still get the same
message.Snap-in failed to initialize.
What else can I do???
I typed in the help box=snap-in failed to initialize.
It showed options but no fixes.

Have sence,patience,and self-restrain,and no mischief will come.

Have sence,patience,and self-restrain,and no mischief will come.

 

[mctiger]

Hi,
I also seen 2 variables listed under the first box.
Under user variables for (my name) listed.
TEMP
TMP
Should there only be one listed?
They both have the same path.
C:\Documents and settings\my name\Local Settings\TEMP

Have sence,patience,and self-restrain,and no mischief will come.

 

[Rick \Nutcase\ Rogers]

Looks like you misspelled and made several errors in it:

Yours:

%System Root%system root;%System Root%;%system Root%\system32\WBE

Should be (from the article):

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM

Copy/paste from here to avoid errors. Make sure you do not remove any
existing PATH statements. There should be no space between "system" and
"root" - there are in the one you posted.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[mctiger]

Hi,
I copy\pasted the line to it.
It still gives me the same error message.
Can I re-install this program?
And if so--How would I go about it.
Thanks again for your help.

Looks like you misspelled and made several errors in it:

Yours:

%System Root%system root;%System Root%;%system Root%\system32\WBE

Should be (from the article):

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM

Copy/paste from here to avoid errors. Make sure you do not remove any
existing PATH statements. There should be no space between "system" and
"root" - there are in the one you posted.

Have sence,patience,and self-restrain,and no mischief will come.

 

[Rick \Nutcase\ Rogers]

Hi,

You wouldn't reinstall a snap-in. Are you sure you copied it to the PATH
statement under SYSTEM variables? And have you rebooted since doing this?

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[mctiger]

Hi,
I followed your advice to the T.
Start-Control Panel-Administrative Tools-Local Security Policy-Local
Policies-Security Options.
Copied & pasted your last post under System Variables double clicked
the path Environment Variable.
Pasted %System Root%system root;%System Root%;%system
Root%\system32\WBE- clicked OK-then OK again-then exited by OK.
Re-booted the computer.
Still the same....
I appreciate all the help that you are giving me.

Hi,

You wouldn't reinstall a snap-in. Are you sure you copied it to the PATH
statement under SYSTEM variables? And have you rebooted since doing this?

Have sence,patience,and self-restrain,and no mischief will come.

 

[mctiger]

Hi,
By the way after the steps of OK- the apply button is grayed out.
The only option is clicking the OK button.
I hope this helps you.
Thanks again.

Hi,
I followed your advice to the T.
Start-Control Panel-Administrative Tools-Local Security Policy-Local
Policies-Security Options.
Copied & pasted your last post under System Variables double clicked
the path Environment Variable.
Pasted %System Root%system root;%System Root%;%system
Root%\system32\WBE- clicked OK-then OK again-then exited by OK.
Re-booted the computer.
Still the same....
I appreciate all the help that you are giving me.



Have sence,patience,and self-restrain,and no mischief will come.

Have sence,patience,and self-restrain,and no mischief will come.