For business scenarios when a centralized management system is not available or has limited access, AVIcode's Incident Utilities provide a method to store data locally for subsequent forwarding. This feature allows users to address disconnected desktop installations, network traffic optimization and troubleshooting processes.

Components and Uses

The Incident Utilities are made up of two components: The AVIcode Incident Snapshot Utility is an optional utility for consolidating locally stored events into snapshots for uploading into SE-Viewer. The AVIcode Incident Upload Utility for uploaded captured snapshots into a centralized management server.

Disconnected Desktops

For mobile users, a centralized management server is not always available. When the user is out of the office, it is still important to be able to detect and monitor LOB applications installed on his/her desktop. The AVIcode Incident Utilities provide Store and Forward functionality to address this need. By enabling this feature, the agent will store events locally and periodically, every X minutes, forward the events to the centralized management server.

Network Traffic Optimization

For highly congested networks, or to limit network utilization during business hours, the AVIcode Incident Utilities provide the ability to store events locally and upload them during off-peak hours.

Troubleshooting Process

To support troubleshooting processes when a centralized management server is not available, the AVIcode Incident Utilities support local storage with the ability to manually forward data to a support technician via email. When a user experiences a problem, he/she can click on the Incident Snapshot Utility () to open an email with the problem information. The system tray application will also have an option to automatically () notify users of an application problem. The notification will pop-up a message, and allow the user to click on the message to launch a support email. Intercept Studio will automatically attach local storage, application event log as well as custom event logs to the email. It also puts relevant information in human/machine readable format into the email body. This email can be sent to help desk personnel to provide complete information about the issue.


When local storage is enabled through the Intercept MMC, events generated from the Agent are stored on the local disk as XML files. One XML file is generated for each event.

By default, these files are stored in [drive]\\Program Files\Avicode\Intercept\Agent\[version-number]\Storage\Events.  Please note that on x64 installation, the server agent and its associated configuration files may be found under "Program Files ", while other components will be under "Program Files (x86)". The Incident Snapshot Utility provides access to this data by converting all of the current XML files to an Incident Snapshot file with the extension '.is' and storing it, by default, in the [drive]\\Program Files\Avicode\Intercept\IncidentSnapshotUtility\Snapshots folder. Therefore, each incident snapshot will contain multiple events. Using the Incident Snapshot Utility menu, you may then:

The Incident Upload Utility provides you with the ability to upload the events contained in a snapshot file into the SE-Viewer database and the SE-Viewer event browser. Events are sent to the SELog  web service via either http or https. The Upload Utility is accessible either through the 'Start' menu or by double-clicking on a snapshot file, and should be installed on all computers used by Help Desk and Support personnel.

Note: You can switch on manual delivery mode during silent installation of ServerAgent by defining an optional parameter in the command line: msiexec /I SrvAgent4_0_0.msi LOCALSTORAGE=True

Last update: Tuesday, June 08, 2010 03:19:15 PM