WMI Remote Connection

Question

0.00/5 (No votes)

See more:

Hi,

I am a beginner in WMI and I want to use WMI for my project. On the local machine, I have no problem. And I can also use wmic for local.

But in the remote connection, I didn't connect. I get an error like this:

Win32: Access Denied.

Is it a workgroup problem?

After that, I tried everything and opened all access permission about WMI and finally I damaged the WMI :)

Now I am getting an error like this:

0x80040154 (REGDB_E_CLASSNOTREG)

At wmimgmt.msc , i saw an error like WMI not registered and I can't select any tabs. So WMI has downed.

What can I do?

And in the wmic, I get this error for another computer.

wmic code: /node:xxx.xxx.xxx.xxx (this remote machine ip address) CPU GET NAME

Response to this command

xxx.xxx.xxx.xxx - Invalid node

Can any one help me?

Thanks!

Agah Burak DEMİRKAN

Posted 9-Apr-10 4:40am

Agah Burak DEMİRKAN

Updated 9-Apr-10 5:14am

Deeksha Shenoy

v2

Add a Solution

2 solutions

Solution 2

Thanks for reply. I did everything in the links before the message commit for errors and remote connections. But didn't work. And now my wmi is down. I found a diagnosis tool for wmi which name is "WMIDiag". This tool give a lot of tips for errors and warnings.

But my biggest problem is registries. In the all of website i traveled, they are talking about some registries but there aren't those registries in my computer.

Posted 13-Apr-10 22:37pm

Agah Burak DEMİRKAN

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Uros Calakovic · Accepted Answer · 2010-04-10T07:50:00

Solution 1

You can start here[^]. There are also two useful webcasts on TechNet (here[^] and here [^]) regarding troubleshooting WMI using the WMI Diagnosis Utility. Googling troubleshooting WMI[^] also returns useful results.
There is also a MSDN section about connecting to WMI remotely.[^]

Posted 10-Apr-10 7:50am

Uros Calakovic