Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For Windows Core servers, ensure you allow the firewall connections as per - http://blogs.technet.com/b/brad_rutkowski/archive/2007/10/22/unable-to-remotely-manage-a-server-core-machine-mmc-wmi-device-manager.aspx

Testing Remote WMI

To test WMI connectivity

  1. RDP to the another Windows machine (if running Open-AudIT on Linux), or if you're running Open-AudIT on Windows, the Open-AudIT server.
  2. Click Start menu, then type: wbemtest
  3. Open the utility.
  4. Click Connect...
  5. Enter the information
    1. Within namespace, type: \\TARGET_DEVICE_IP\root\cimv2  -  where TARGET_DEVICE_IP is the IP of the device not being discovered by Open-AudIT.
    2. For the Username, use the format domain\username
    3. Enter the password
    4. Leave the Authority field blank.
  6. Click connect
  7. Click query
  8. Run the following query: Select * from Win32_ComputerSystem
    1. If it does not work, the target PC has an issue (or something between the target PC and Open-AudIT).
    2. if it does work, please log a support ticket with Opmantek.


AntiVirus

Some antivirus programs have been known to disable DCOM and remote WMI. You might check the settings of your antivirus program and disable them for testing. We recently had a report of Trend AV specifically blocking calls to winexesvc when auditing Windows computers.

...