How do i enable wmi

At this point go back and see if this fixes the problem. It might take a couple of minutes for the reports to re-generate. For reading WMI data on a remote server, a connection needs to be made from your management computer where our monitoring software is installed to the server that you're monitoring the target server. This can only be done at the command prompt. Run the following on the target computer if it is running a Windows firewall:.

If the account you are using to monitor the target server is NOT an administrator on the target server, you need to enable the non-administrator to interact with DCOM by following the simple steps listed here. Once the WMI browser can access a remote machine, our products should be able to as well. With UAC running, an administrator account actually has two security tokens, a normal user token, and an administrator token which is only activated when you pass the UAC prompt. It turns out that enabling WMI logging is easy to do once you know where to look, so in this blog post I will show you the steps.

Warning: It goes without saying that this is NOT something that you should enable and then leave enabled! It consumes a fair amount of CPU and diskspace, so I recommend that you only enable it while troubleshooting.

First, open Event Viewer. I know this sounds counter-intuitive, but who said everything must be logical? By the way, there are two different WMI logging options.

The first one is on Event Viewer and the second one is a more traditional log file. When you are not connecting to the built-in Administrator account, UAC affects connections to a remote computer differently depending on whether the two computers are in a domain or a workgroup. However, UAC affects connections for nondomain user accounts. If you connect to a remote computer using a nondomain user account included in the local Administrators group of the remote computer, then you must explicitly grant remote DCOM access, activation, and launch rights to the account.

The CIMOM settings need to be updated if the remote connection is between computers that do not have a trust relationship; otherwise, an asynchronous connection will fail.

This setting should not be modified for computers in the same domain or in trusted domains. If the value is set to 1, the WMI service allows anonymous callbacks to the client. This setting is usually all that needs to be changed to get WMI working Steps 2 and 3 are typically not needed, but they might be in some circumstances. At this point go back and see if this fixes the problem. It might take a couple of minutes for the reports to re-generate. For reading WMI data on a remote server, a connection needs to be made from your management computer where our monitoring software is installed to the server that you're monitoring the target server.

This can only be done at the command prompt.