How auditing works in the console

Geovariances · October 9, 2020 - 5:14 PM

Hello,

We've started using auditing features for our packages to verify their proper installation and to mitigate the risk of user deletions.
For example, I've added an audit for the presence of an executable in c:\programfiles\XXXX\XXX.exe, which returns an "ERROR" audit if it doesn't exist.
The audit runs during installation and then again after 60 minutes in case of accidental deletion (a delay specified in my control file).
I expect two things: first, that my package will change to an "ERROR" audit status, which is indeed the case, and second, that my overall machine status will also change to "ERROR," which is not happening. When I look at my console, I initially see an OK status for my entire network, while some machines are actually showing an "ERROR" audit status for certain packages.
I also have a number of machines with a "WARNING" audit status, even though all my packages are either "OK" or have an empty field.

1. How can I get my audit status to display a red or orange alert on my computer with a "WARNING" or "ERROR" status?
2. Shouldn't a package with a failed audit be offered for reinstallation?

Thank you for your help!

October 15, 2020 - 3:04 PM

Hello geovariance,
if you are using the community version (or an expired trial version), the Audit feature is no longer supported. I don't know how the functionality behaves with an expired trial version (since it's not included in the community version).
If you reinstall the community version, the Audit column will disappear, preventing the message from appearing.
If you upgrade to the enterprise version and the problem persists, you can contact support to see if it's a bug.
Sincerely,
Denis Cardon