Shortcut Menu

Skip

Main Navigation

Choose your language

You are here:

ActiveXperts.com > Support > Knowledge base > Network Monitor > Monitoring Windows / WMI

Activexperts Support Pages


Q7250015: I cannot monitor my Windows 2003 SP1 and Windows XP Pro Sp2 machines. I get the following error: "Unable to query the WMI service on computer". What's wrong?

This generally happens on computers with the Windows Firewall enabled which blocks WMI calls to it. By default, Windows 2003 SP1 and Windows XP Professional SP2 have the Firewall module enabled. To have WMI calls allowed on a Windows 2003 Service Pack 1 computer with firewall enabled, the following script has to be run:

  Set objFirewall = CreateObject("HNetCfg.FwMgr")
  Set objPolicy = objFirewall.LocalPolicy.CurrentProfile
  Set objAdminSettings = objPolicy.RemoteAdminSettings
  objAdminSettings.Enabled = TRUE

This script will enable WMI administration.

The problems can also be a security issue, where the ActiveXperts Network Monitor Service Account has no privileges to monitor the remote XP PC's. Ensure that the credentials used for the ActiveXperts Network Monitor service are sufficient.

You can check this out with a simple VBScript program:

  • On the machine that has ActiveXperts Network Monitor installed, log on interactively using the same credentials as used for the Network Monitor service;
  • Run www.activexperts.com/support/network-monitor/wmi/cpu.vbs; when you're prompted for a computer name, specify the remote machine that you cannot monitor using ActiveXperts Network Monitor.

Most probably, you won't be able to monitor the remote machine, just like with ActiveXperts Network Monitor.

Then, use the built-in WMIC command (only available for Windows 2003 and Windows XP) to monitor the remote machine:

  wmic /node:COMPUTERNAME path Win32_Processor where DeviceID='CPU0' get LoadPercentage

WMIC will provide more advanced error information, to help you troubleshooting the problem.

(viewed: 1033)