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.
--
Sharon F
MS-MVP ~ Windows XP Shell/User
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!
http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org
"mctiger" <wmck...@yahoo.com> wrote in message
news:ek9ab0t97khplpffp...@4ax.com...
> 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
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
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"Sharon F" <sharo...@ETEmvps.org> wrote in message news:%23ikb2g7...@tk2msftngp13.phx.gbl...
> 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.
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"Sharon F" <sharo...@ETEmvps.org> wrote in message news:%23$YMGYBRE...@TK2MSFTNGP10.phx.gbl...
On Wed, 26 May 2004 21:32:12 -0400, "Rick \"Nutcase\" Rogers"
<ri...@mvps.org> wrote:
>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.
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!
http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org
"mctiger" <wmck...@yahoo.com> wrote in message
news:j0ffb0t1mqbikjq1s...@4ax.com...
while online.
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"mctiger" <wmck...@yahoo.com> wrote in message news:j0ffb0t1mqbikjq1s...@4ax.com...
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
>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.
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!
http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org
"mctiger" <wmck...@yahoo.com> wrote in message
news:92vgb0146mb0uq95h...@4ax.com...
On Sat, 29 May 2004 08:43:31 -0400, "Rick \"Nutcase\" Rogers"
<ri...@mvps.org> wrote:
>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.
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!
http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org
"mctiger" <wmck...@yahoo.com> wrote in message
news:nrahb0pdbqldoku8n...@4ax.com...
On Sat, 29 May 2004 16:56:32 -0400, "Rick \"Nutcase\" Rogers"
<ri...@mvps.org> wrote:
>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.
Under resolution--The third step-under System Variables-double-click
the PATH environment variable.
under System Variables--Does it read environment variable or should it
read environment variables? Or should it read Path environment
variables?
Which way should it read?
Thanks.
It's
%SystemRoot%\system32;%SystemRoot%;%systemRoot%\system32\WBEM
Rick told you this before.
It stops being read at the first error.
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"mctiger" <wmck...@yahoo.com> wrote in message news:digjb01e627cnffl3...@4ax.com...
On Sun, 30 May 2004 21:29:24 +1000, "David Candy" <da...@mvps.org>
wrote:
>It's NOT %System Root%system root;%System Root%;%systemRoot%\system32\WBE
>
>It's
>
>%SystemRoot%\system32;%SystemRoot%;%systemRoot%\system32\WBEM
>
>Rick told you this before.
>
>It stops being read at the first error.
Have sence,patience,and self-restrain,and no mischief will come.
--
Best of Luck,
Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!
http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org
"mctiger" <wmck...@yahoo.com> wrote in message
news:bvijb0pnk8j65uvml...@4ax.com...
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"mctiger" <wmck...@yahoo.com> wrote in message news:3ohjb0hsijmfg8e13...@4ax.com...
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
and yet you post back with similar errors.
Type
cmd /c echo %path% > "%userprofile%\desktop\path.txt
and ATTACH the file that appear on your desktop.
"mctiger" <wmck...@yahoo.com> wrote in message news:bvijb0pnk8j65uvml...@4ax.com...
On Sun, 30 May 2004 09:14:04 -0400, "Rick \"Nutcase\" Rogers"
<ri...@mvps.org> wrote:
>Go back and check that there aren't multiple instances in the PATH statement
>now. If your earlier error-laden version is still in there, the whole thing
>will be buggered up.
Have sence,patience,and self-restrain,and no mischief will come.
cmd /c echo %path% > "%userprofile%\desktop\path.txt"
also type
cmd /c set >> "%userprofile%\desktop\path.txt"
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"mctiger" <wmck...@yahoo.com> wrote in message news:a40kb09g4i3ft0chv...@4ax.com...
On Mon, 31 May 2004 02:05:04 +1000, "David Candy" <da...@mvps.org>
wrote:
>Type it in Start - Run
>
>cmd /c echo %path% > "%userprofile%\desktop\path.txt"
>
>also type
>
>cmd /c set >> "%userprofile%\desktop\path.txt"
Have sence,patience,and self-restrain,and no mischief will come.
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"mctiger" <wmck...@yahoo.com> wrote in message news:ci3kb09f9uv0k1ul1...@4ax.com...
I hope this helps you help me!
Thanks again..
On Mon, 31 May 2004 02:46:10 +1000, "David Candy" <da...@mvps.org>
wrote:
>I'm sorry you are far too stupid. Either read what is written or f*ck off.
Have sence,patience,and self-restrain,and no mischief will come.
It should be
%USERPROFILE%\Local Settings\Temp
Which will display the same as tmp
C:\DOCUME~1\wmckeeby\LOCALS~1\Temp
You've put the path in there.
Security Policy requires access to the folder.
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"mctiger" <wmck...@yahoo.com> wrote in message news:505kb0pmltcttgghu...@4ax.com...
On Mon, 31 May 2004 03:32:26 +1000, "David Candy" <da...@mvps.org>
wrote:
>Your temp line is wrong.
>
>It should be
>
>%USERPROFILE%\Local Settings\Temp
>
>Which will display the same as tmp
>C:\DOCUME~1\wmckeeby\LOCALS~1\Temp
>
>You've put the path in there.
>
>Security Policy requires access to the folder.
Have sence,patience,and self-restrain,and no mischief will come.
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"mctiger" <wmck...@yahoo.com> wrote in message news:gp7kb091k7dv75cqo...@4ax.com...
Hope this helps.But still get the same error message .
Thanks for your help.
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"mctiger" <wmck...@yahoo.com> wrote in message news:br8kb05f6envf9935...@4ax.com...
Yes, I'm talking about the whole PATH line in the environmental variables.
Go in there, and carefully use the arrow keys to check the entire length of
it.
--
Best of Luck,
Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!
http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org
"mctiger" <wmck...@yahoo.com> wrote in message
news:atvjb0hcfvqn9l4v0...@4ax.com...
On Sun, 30 May 2004 17:30:43 -0400, "Rick \"Nutcase\" Rogers"
<ri...@mvps.org> wrote:
>Hi,
>
>Yes, I'm talking about the whole PATH line in the environmental variables.
>Go in there, and carefully use the arrow keys to check the entire length of
>it.
Have sence,patience,and self-restrain,and no mischief will come.
MMC can be executed with command line parameters, such as a console
file name. Additionally, the following command line switches are
recognized by MMC64.
/32
/64
If both of the preceding switches are specified on the command line,
then the far right switch is in effect.
Start-up considerations if /32 or /64 is in effect.
If MMC64 is started with no command line parameters, or if MMC64 is
started with the /64 command-line option, it executes as the MMC64
application. If MMC64 is started with the /32 command-line option,
MMC32 is launched, using the same parameters initially passed to MMC64
(except the /32 command-line option), and MMC64 will terminate.
Start-up considerations if a console file is specified.
If the MMC64 command line does not contain a /32 or /64 command-line
option, but the command line does contain a console file name, then
MMC64 examines the console file before determining which version of
MMC remains in execution. MMC64 uses the following algorithm.
If all snap-ins referenced by the console file are available in 64-bit
form, then MMC64 will remain as the executing version (the remaining
algorithm steps are not executed). A snap-in is considered available
in 64-bit form if it exists as an HKEY_CLASSES_ROOT\CLSID\snap-in
clsid\InprocServer32 key in the registry, where snap-in clsid is the
registered CLSID for the snap-in.
If not all snap-ins referenced by the console file are available in
64-bit form but all of them are available in 32-bit form, then MMC64
starts MMC32. MMC32 executes using the console file as specified on
the command line, and MMC64 terminates (the remaining algorithm steps
are not executed). A snap-in is considered available in 32-bit form if
it exists as a HKEY_CLASSES_ROOT\Wow6432Node\CLSID\snap-in
clsid\InprocServer32 key in the registry, where snap-in clsid is the
registered CLSID for the snap-in.
If the number of unavailable 64-bit snap-ins is a subset of the
unavailable 32-bit snap-ins, then MMC64 remains as the executing
version (the remaining algorithm steps are not executed).
If the number of unavailable 32-bit snap-ins is a subset of the
unavailable 64-bit snap-ins, then MMC64 starts MMC32 and MMC64 closes
(the remaining algorithm step is not executed).
If none of the previous steps yields a conclusion, then a user
interface is presented to the user, prompting the user to specify
which version of MMC to run (an option to cancel is also presented to
the user).
In any event where MMC64 fails to successfully start MMC32, MMC64
continues to run. After MMC32 has been successfully started by MMC64,
then MMC64 closes. If an error occurs after MMC32 has successfully
started, MMC64 is not notified, as it will have already been closed.
I really do not understand any of this.Can you help with this?
Which advice from this should I follow?
I updated to sevice pack 2=Bata version.I uninstalled the Bata.
Maybe that mixed things up???
Thanks again.
On Sat, 29 May 2004 10:48:56 +1000, "David Candy" <da...@mvps.org>
wrote:
>Snap-in failed to initialize
--
----------------------------------------------------------
http://home.comcast.net/~wizardofwhimsy/index.html
"mctiger" <wmck...@yahoo.com> wrote in message news:fnokb0tl9tn1a7g8i...@4ax.com...
On Mon, 31 May 2004 09:03:32 +1000, "David Candy" <da...@mvps.org>
wrote:
>This is what I get.
> 1.. Windows XP Support Center
> 2.. "Snap-in Failed to Initialize" Error Message When You Open Microsoft Management Console
> 3.. Viewing Saved FRS, DNS and Directory Service Event Logs and Events on Windows XP Non-Domain Domain Controllers
> 4.. Detailed Usage of the Event Viewer /AUXSOURCE Switch Option
Have sence,patience,and self-restrain,and no mischief will come.