Page History

...

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 Enum Classes and select Recursive, then click OK
8. It may take several seconds to respond.
   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.

Testing Remote WMI #2

Open a command prompt and try the following command. Substitute your domain, username, password and target IP.

You should get a result similar to the below.

NOTE - the extra r's and for the (r) registered trademark symbols, no need to be concerned with them.

C:\Users\opDev>wmic /user:YOUR_DOMAIN\YOUR_USERNAME /password:YOUR_PASSWORD /node:YOUR_IP os get name
Name
Microsoftr Windows Serverr 2008 Enterprise |C:\Windows|\Device\Harddisk0\Partition1

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.

...