Click Start, Run and type regedit.exe
Navigate to the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE
Backup the branch by exporting it to a REG file.
In the right-pane, delete the following values (if found):
"EnableRemoteConnect"="Y"
"LegacyAuthenticationLevel"
"LegacyImpersonationLevel"
Close Registry Editor and restart Windows.
--
Regards,
Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting
http://www.winhelponline.com
Well, as much as I wanted that to work the last time I tried it, it did not.
Here is what appears after clicking connect when the namepsace "root\cimv2"
is entered:
Error
Number: 0x80070005
Facility: Win32
Description: Access is Denied
--
Horsepower
:
See this note from Jiachuan Wang [MSFT]:
<quote>
I'm trying to see whether it's a WMI control issue or WMI service issue:
If the following works, it means the WMI service works properly. (Otherwise WMI repository could be corrupted)
1) wbemtest.exe
2) Click "Connect..." and type "root\cimv2" for namespace, and
click "Connect" to connect to that namespace
3) Click "Enum classes..." and then "Recursive" radio button (don't need to type a superclass), and then click "OK"
4) you shlud see a list of classes
If the above succeeds, that means a WMI control issue. Usually Administrator will have access to it even you deny it. there could be some reasons like promotion to domain controller or group policy causing problem.
</quote>
Source:
http://groups.google.com/group/microsoft.public.windowsxp.wmi/msg/cc23ed5975d86724
--
Regards,
Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting
http://www.winhelponline.com
I have an issue with more than one client's PCs. Windows Installer fails to
run properly, and after much reading and digging I've come across this one.
WMI Control in computer management will not work. I get the following after
selecting properties:
Failed to Connect to <local computer>
because "Win32: Access is Denied"
What in the world can I do? I have run WMIDiag from MS and it gives me
errors too from the same area. Are my DCOM security modification all out of
whack?
Thanks in advance for the help.