WMI Control - Access Denied, could not connect to <local computer>

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

It seem that I played too much with WMI security on one of our server...

So now, what could I do to reset the too restrictive security on Root\CIMV2
using soething else than WMI Control, which could'nt be used anymore???

Thanks.

Claude Lachapelle
Systems Administrator, MCSE
 
Still unresolved...

When I'm trying to change settings of COM Security with the Component
Services (dcomcnfg.exe) console (Computer properties), I'm always getting:

Catalog Error
You do not have permission to perform the requested action. If security is
enabled on the System Application of the target computer make sure you are
included in the appropriate roles.

What they are talking about when saying "on the System Application" ?

Thanks.
 
Using WMIDiag.vbs from Microsoft, I found the problem, it was related to My
Computer, DCOM security which was not allowing remote connection to WMI.

Thanks to WMIDiag.vbs VERY GOOD REPORTING (all results are written into a
txt file).
 
Claude Lachapelle said:
It seem that I played too much with WMI security on one of our server...

So now, what could I do to reset the too restrictive security on Root\CIMV2
using soething else than WMI Control, which could'nt be used anymore???

Thanks.

Claude Lachapelle
Systems Administrator, MCSE
Click to expand...
 
Claude Lachapelle said:
Still unresolved...

When I'm trying to change settings of COM Security with the Component
Services (dcomcnfg.exe) console (Computer properties), I'm always getting:

Catalog Error
You do not have permission to perform the requested action. If security is
enabled on the System Application of the target computer make sure you are
included in the appropriate roles.

What they are talking about when saying "on the System Application" ?

Thanks.
Click to expand...
 
Claude Lachapelle said:
Using WMIDiag.vbs from Microsoft, I found the problem, it was related to My
Computer, DCOM security which was not allowing remote connection to WMI.

Thanks to WMIDiag.vbs VERY GOOD REPORTING (all results are written into a
txt file).
Click to expand...
 
Back
Top