WMI Permission denied

[dwos]

I have been searching high-and-low on the Microsoft site for a solution to
why I can't remotely run WMI code for 2 of our computers in our domain. All
other computers respond appropriately and are all built the same.

I run the following script via an Access database in code and for all but 2
PC's I get the correct response. For 2 of the PC's I get the response back
of "PERMISSON DENIED". I am the domain admin and logged in as such, so I
think that can rule out authentication problems. We're not using any GPO's
either.

Both PC's are WinXP Pro, one has SP2 the other has SP1a. The one with SP2
never correctly repsonded before updating to SP2 so have been able to rule
that possibility out.

'=========CODE SNIPPET==================
strComputer="JoeSmith"
Set objWMIService = GetObject("winmgmts:" &
"{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")

Set colComputer = objWMIService.ExecQuery("Select * from
Win32_ComputerSystem")

For Each objComputer In colComputer
Debug.Print "Logged-on user: " & objComputer.UserName
Next

Regards,

Robert C

 

[Peter Falz]

Hi dwos,

I run the following script via an Access database in code and for all but 2
PC's I get the correct response. For 2 of the PC's I get the response back
of "PERMISSON DENIED". I am the domain admin and logged in as such, so I
think that can rule out authentication problems. We're not using any GPO's
either.

is it possible, that these both PCs are not assigned to your domain?
is it possible, that the rights for the domainadmin, are not the same
as at the other PC's?

I think, it is possible, you've a problem with the adminrights.

Cioa
Peter

 

[dwos]

Just checked the permissions on both PC's and they appear to have the same
permissions as all the other PC's. Even checked the permissions in the WMI
snap-in.

Heck, I can do just about everything remotely to them except WMI. I can
open just about any MMC snap-in on either PC. Can't run RSOP snap-in or make
the WMI snap-in work remotely. Just about ready to just rebuild them and
see what happens. Heck I've probably spent more time trying to get it to
work that it would have take to rebuild it.

Cheers,

Robert C

 

[bogdanMo [MSFT]]

Try to logon locally on those machines and use wbemtest.exe/your script to
connect locally. If it doesn't work, try to bring up the WMI mmc snapin and
see the security settings. It's hard to analyze what's happening with those
computers without having any info about them (wrong security settings on
those namespaces, corrupted repository, etc.)