<div>
There is an &quot;admin template&quot; called MMCSnapins.admx that as a &quot;WMI Control&quot; option that turns off the ability to bring up the WMI control. &nbsp; I haven't tried it, but it appears to be similar to what you're describing.<br />
<br />
Check this registry location to see if it's turned on for you:<br />
<br />
HKCU\Software\Policies\Mic<wbr />rosoft\MMC<wbr />\{5C659257<wbr />-E236-11D2<wbr />-8899-0010<wbr />4B2AFB46}!<wbr />Restrict_R<wbr />un<br />
<br />
<br />

</div>


<div>
graye - that would make sense - however on any PC i checked both in the domain and out of the domain and my servers - i cant get that registry key. It stops at Microsoft - i do not have any keys for MMC. 
</div>


<div>
Well, the lack of that registry key just means you don't have that policy enabled (which is a good thing)<br />
<br />
Are you in the local adminstrators group on the PCs where that WMI configuration doesn't work?<br />
<br />
Have you tried launching the WMI &quot;snap in&quot; by hand (by starting with just a blank MMC, and then adding the WMI snap in)
</div>


<div>
graye, <br />
<br />
Couple more clues:<br />
<br />
1.) I am part of the local admins - as well as even logging in as local administrator to the pc does not work.<br />
2.) I am on my XP machine that is off the domain and i am also missing that registry key you mentioned however my WMI works just fine.<br />
3.) I tried a blank MMC then addedd WMI snap in and i still can not connect to WMI because access is denied even logged in as computer administrator.
</div>


<div>
That's good information.... somebody/something has probably messed with your DCOM security settings<br />
<br />
<a href="http://msdn.microsoft.com/en-us/library/aa910247.aspx" rel="ugc">http://msdn.microsoft.com/en-us/library/aa910247.aspx</a>
</div>


<div>
I tried this on my win2k3 sp2 host without success.<br />
I am now rejoining the domain to see if that helps propegate the local security policy (didnt appear to get updated.).<br />
<br />
I did notice you appear to have added and &quot;i&quot; to your second string &quot;wmi iD:(A;&quot;. I removed the &quot;i&quot; before the D, the descriptor command executed successfully..<br />
<br />
I still encountered the same failures in my WMIDiag log. :-(<br />
<br />
What I did identify was related to the local security policies. Someone had modified several policies and not included the SYSTEM account where it was allowed by default.<br />
<br />
I updated the Domain Controller local policies and performed a GPUpdate /Force /Sync. <br />
<br />
This did not work either... I finally ended up taking the host out of the domain modifying the security policies on the local host. Then adding back into the domain.<br />
<br />
I am no longer getting the authentication errors from the WMIDIAG tool.<br />
I am getting some performance errors that I think are related to my rebuild of the WMI;<br />
54 errors all relating to the ROOT/SUBSCRIPTION space.
</div>


<div>
This solved the problem I was having re-installing my iSCSI initiator. However, need to chase down logical disk manager access rights :(
</div>


<div>
<div class="content wysiwyg-content">
Hello, I will be thrilled if some one can help me - I have a windows environment - 7 windows 2003 servers and approx 200+ XP Sp2 workstations. I am installing a new software requiring WMI - WMI is working on all our servers both locally and remotely however the workstations does not allow WMI locally or remotely. When I check the secutiy tab on WMI - it will not let me click it - better yet it will not let me click any tabs on the WMI properties. Is there some where in my GPO or domain settings that will prevent me from changing the WMI settings? Any help is much appreciated.
</div>
</div>


Hello, I will be thrilled if some one can help me - I have a windows environment - 7 windows 2003 servers and approx 200+ XP Sp2 workstations. I am installing a new software requiring WMI - WMI is working on all our servers both locally and remotely however the workstations does not allow WMI locally or remotely. When I check the secutiy tab on WMI - it will not let me click it - better yet it will not let me click any tabs on the WMI properties. Is there some where in my GPO or domain settings that will prevent me from changing the WMI settings? Any help is much appreciated.

WMI Security Issues

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.