...
On Windows, Open-AudIT uses WMI via VBscript as it's primary method of auditing. SNMP is also supported (and as detailed below). Windows has a notorious reputation where remote WMI is concerned. It's tends to either "just work" or some mystery item on the target requires changing. If you are experiencing difficulty auditing remote Windows PCs, we have created a script called test_windows_client.vbs. You can run this script LOCALLY on the machine in question, after signing on as the user that is used by Open-AudIT to perform the audit. The script makes NO CHANGES to the target system. It checks most (not all) of the items below and generates PASS, FAIL and INFO tags for various properties. NOTE - If your target system is being audited correctly, you should not change any settings. Some of the below do not exist on Windows PCs that are able to be audited and some do exist. Only change settings if yours audits on particular PCs are not working as intended.
In addition to the below, other items that should checked are the time between the client and the domain controller and that DNS is resolving correctly (both forwards and backwards).
Some users have also stated removing and then rejoining the client PC to the domain has enabled auditing to work.
Note - All commands below should be entered into an elevated command prompt. To do this click Start -> All Programs -> Accessories -> Command Prompt, right click then "Run as administrator".
...