E-Z Audit On Demand Updates & Support
E-Z Audit On-Demand Updates
Module Revision Updated on Download
Full install
10.0.1001
06 November 2007
Read the User's Guide
which contains information on installing, deploying and using E-Z Audit On-Demand
Most asked question:
I am not getting all my PCs reported using the E-Z Audit On-Demand add on.
Are these users logged off? If they log out of their PCs, the machine is not available to audit.
Have they rebooted or logged off and back on since you first implemented On-Demand? On-Demand does not take effect until the user has logged in and the logon script has run.
Do your users have the correct permissions set for the folders on your server where you launch On Demand and where the audits are saved to? Review the E-Z Audit Quick Start Guide (PDF) to set up the E-Z Audit folders, as these are the same ones you use for the On Demand audit modules.
In the “ezaudit” folder you should have odstart.exe, ondemand.exe, ezstart.exe and ezscan.exe, and a configuration file. For On-Demand prior to Version 9 the configuration file must be a separate one for On Demand and it must be called ondemand.ezc.
Next ensure that this folder has read, write, create, delete, execute permissions explicitly declared for all your users, typically the “Everyone” group. “Full Control” does not always grant all these permissions, so add these as explicitly granted to “Everyone”.
Ensure that the “audits” file has the same explicit permissions, less “execute” as it is not needed there.
Ensure that you have added On-Demand to your logon script, like:
“\\your_server_name\ezaudit\odstart.exe”
If the permissions are not correct, that will cause the problem you are experiencing.
If the above are in place and correct, then in the \\your_server_name\ezaudit folder look for oderrlog.txt. This file would log problems launching On-Demand at the PC.
If users do not have the correct permissions, then they cannot write to the error log file and/or launch the audits. Most of the support issues we get for On-Demand are resolved via fixing permissions.