User-Defined Fields and audit data you can edit


ez
audit allows you to set and edit a number of User-defined fields at all stages of the audit process

Custom data you can associate to all audits before auditing


You can store 2 fields of data that will be added to all audit results via the configuration file.

These cannot be changed post-audit and they are not visible at the user's PC even if you run an audit where the user must interact with the scanner to enter answers to questions you want to ask them.

You set these in the Configuration tool when creating a configuration.

Some uses for this might include notes for yourself about that series of audits, like "San Jose branch audit" or "Pre-hardware upgrade initial audit".

 

Fields that can be entered at audit time by the user being audited or your tech support staff


There are four fields that can be entered manually at the PC being audited. 

You can ask your users to enter information into these fields when you
configure your scan, including the option to require answers before they continue, or you can use these yourself if doing a hands-on scan to enter anything you want.


In a configured audit for your users you can also set whether you want them to answer the questions each time an audit is run, or to retain the answers for future audits.

For more details read about configuring audits


Fields you can add information to post-audit


You can add four
Admin Notes at the Admin console to each audit.  These are your notes related to the specific PC that remain even when the PC is audited again. 

Example: to note when that PC was put in service, an in-house service tag, etc.

You can add Generic Notes that apply to all PCs in the folder you have opened that remain with these audits even when the PCs have been audited again.

Example: The location name for those audits, the reason for those audits, etc.

Additionally, you can edit the User name, Make/Model/Serial Number for any PC.  These are also retained for that particular machine across new audits.

 

Store static data on a PC before deployment


UPDATE 27 June 2018 - The old ezaudit.ini file in the root of C:\ has been deprecated.  See the information below for the new and enhanced method of storing data on PCs when you deploy them or at any time thereafter.

Note: to handle PCs already deployed with the ezaudit.ini file method, the scanner module as of 12 July 2018 will first check the registry and if nothing found, then check the for the .ini file.  Moving forward you should deploy PCs that you want to store information on using the registry method, below.  They will co-exist nicely with older PCs that have the .ini file.



You can store four fields that are PC specific at deployment or at any time.

They can contain whatever information is relevant to your needs.

The information is stored in the registry and below are example .REG files that you can create to enter the data for your PCs:

On 64-bit Windows:

Windows Registry Editor Version 5.00
;------------------REMARKS--------------------
;You can enter any information into each line
;This is just an example
;---------------------------------------------

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\EZAudit]
"Note1"="(Example) Deployed 2016-04-01"
"Note2"="(Example) Internal Asset Tag: ABC123"
"Note3"="(Example) Location: San Jose office - Accounting"
"Note4"="(Example) Image file accountng01"

On 32-bit Windows:

 

Windows Registry Editor Version 5.00

;------------------REMARKS--------------------
;You can enter any information into each line
;This is just an example
;---------------------------------------------

[HKEY_LOCAL_MACHINE\SOFTWARE\EZAudit]
"Note1"="(Example) Deployed 2016-04-01"
"Note2"="(Example) Internal Asset Tag: ABC123"
"Note3"="(Example) Location: San Jose office - Accounting"
"Note4"="(Example) Image file accountng01"


These cannot be changed post-audit at the Admin Console.