Update Alloy Audit Tools

On this page

Alloy Audit Tools is a separate installer with its own release cycle. It holds the Inventory Analyzer audit agent (Windows, Linux, and macOS builds), the Audit Snapshot Viewer, and the internal dictionaries used to identify network devices. The installer updates only the components that are already present on the computer you run it on, so the same file behaves differently on an Inventory Server and on a technician workstation.

The update has two parts: you stop the Inventory Server, run the Audit Tools installer, and start the Inventory Server again on every computer that hosts it; then you re-deploy the remote audit agents.

Alloy Navigator has no in-product display of the deployed Audit Tools version.

Before you begin

  • When you run the installer with its full user interface, it checks for an earlier Alloy product on the computer: an Alloy Discovery product with its Audit Tools installation, or Alloy Navigator 6.0 or later. On a computer that has neither, it shows "No previous installations of Alloy Audit Tools exist on this computer." and "The setup will be aborted.", and stops. The same check refuses per-user installations of certain 5.x and 6.x Alloy products.
  • Close all Alloy Navigator applications on the computer before you install the update. The installer does not check for running applications itself; Windows Installer shows its standard files-in-use dialog when files it has to replace are in use.
  • The Audit Tools installer does not stop the Inventory Server service. You stop and start it in the Inventory Server Manager. If your Windows account cannot manage the service, the manager warns "You do not have enough permissions to manage the Alloy Inventory Server."
  • To open an audit source window in Alloy Discovery, you need the right to view the source.
  • To rebuild an Inventory Analyzer package in Alloy Discovery, you need the audit right. Without it, Create Package... in an E-mail or FTP audit source window shows "You do not have enough permissions to perform this action.", and Deploy... in the Portable Audit Source window is unavailable. Deploy... on the Site window's Actions menu checks the same right.

Update Audit Tools on a computer

What the installer updates depends on the computer:

Computer What the installer updates
Alloy Discovery Inventory Server (every instance) All Audit Tools components
Alloy Navigator technician workstation The Audit Snapshot Viewer only

On each computer that hosts the Inventory Server:

  1. Open the Inventory Server Manager from the Alloy Control Panel. The Alloy Control Panel shortcut is in the Alloy Software Start menu folder and on the desktop.
  2. Click Stop. A progress window waits up to 125 seconds for the service to stop.
  3. Run the Audit Tools installer. Its wizard goes from a welcome page to a ready-to-install page, where you start the installation, and, when the installation succeeds, ends with a completion page.
  4. In the Inventory Server Manager, click Start.

On an Alloy Navigator technician workstation, run the Audit Tools installer; it updates the Audit Snapshot Viewer only.

Also run the Audit Tools installer on each Alloy Discovery technician workstation.

Each run of the installer, including a repeat run on the same computer, goes through the same installation wizard.

To stop or start the service without opening the manager's main window, run the manager, DataCollectorMngr.exe, with the argument stop or start. The progress window still appears. The manager exits with 0 on success, 2 when the wait ends before the service reaches the new state, and 1 on failure.

If several computers host an Inventory Server for the same database, the manager must be run on each of them.

The Inventory Server Manager behaves as follows during the update:

  • When the manager opens and no valid Database Access Key is imported, it shows "Unable to find a valid Database Access Key. Please import your Database Access Key before configuring the Inventory Server." and opens the key import.
  • Stop is available while the service is started or paused. Start is available while the service is stopped; for a paused service, the button reads Resume.
  • Start first saves the connection settings shown in the form, and does not start the service if saving fails, for example when no key is imported.
  • The status line reads Inventory Server followed by the service state, such as Started or Stopped. When the service is running or stopping but the manager is not connected to the database, the computer is not registered, or the server has not reported in the last 180 seconds, the line reads Inventory Server Running with Errors (Offline).
  • A warning panel lists the problems the manager finds: "Inventory Server was not found. Inventory data cannot be loaded to the database." when the service is missing, in which case Start and Stop are unavailable; "There is no connection to the database." when no database is named; a license error; and "Database connection failed. Please check with your <product> administrator that your Database Access Key is valid.", with the product name filled in, when the connection test fails.
  • If the service fails to start or stop, the manager shows "Inventory Server is not started." (or "Inventory Server is not stopped."), the error, and "The Inventory Server writes more detailed error information to the Event Log.", and offers to open Event Viewer. The service writes its start, stop, and error events to the Windows Application log under the source name AlloyInventoryServer.

Re-deploy remote audit agents in Alloy Discovery

There is no direct link between the Inventory Server and a deployed agent over which an update could be pushed. Agents that are not directly connected have to be re-deployed by hand:

  • For FTP and e-mail audit sources, rebuild the Inventory Analyzer package and re-deliver it, or re-create the agent installer and re-run it on each remote machine.
  • For portable audit media, refresh the media with a rebuilt package.

You rebuild agent packages and installers in the Alloy Discovery console.

Open an audit source

  1. In the Sidebar's Sites tree, open the pop-up menu of the Site and click Properties. The Site window opens.
  2. On the Audit Sources tab, double-click the source, select it and press Enter, or select it and click Edit.

The window that opens depends on the source type: the E-mail, FTP, or Portable Audit Source window.

Rebuild the Inventory Analyzer package

  1. Start the deployment in one of these ways:
    • In an E-mail or FTP audit source window, click Create Package... in the Package group.
    • In the Portable Audit Source window, on the General tab, click Deploy... in the Inventory Analyzer package group.
    • In the Site window, select a single E-mail, FTP, or Portable source and click Deploy... on the Actions menu.
  2. In the Deploy Agents dialog, enter a folder in Folder:, or click Browse... to choose one.
  3. Select the platforms: Windows, Mac OS, Linux.
  4. Click Deploy.

In the Portable Audit Source window, Deploy... is available only when the window has no unsaved changes (the record is not being edited and is not new). Deploy... on the Site window's Actions menu has no such condition.

The Deploy Agents dialog restores the last folder and platform selection you used. The first time, Windows is selected and Linux and Mac OS are cleared. Deploy stays unavailable while Folder: is blank. A folder that does not exist is refused with "Folder "<path>" doesn't exist." Your choices are saved only after the deployment completes.

The deployment writes a runnable Inventory Analyzer folder, not an installer. All selected platforms share the chosen folder:

  • Windows: the agent ina32.exe, copied from the Audit Tools installation, with its configuration, built from the source's audit profile with interactive mode on; the AuditData and Log folders; and an autorun.inf file that starts ina32.exe /interactive. For a Portable source, the e-mail, FTP, excluded-machines, and bypass sections of the profile are left out.
  • Linux: the lina, lina24, and lina26 agents with a lina.ini configuration and an AuditData folder.
  • Mac OS: the ina_mac agent with an ina_mac.ini configuration and an AuditData folder.
  • In every case, the Audit Snapshot Viewer files, copied last. If Alloy Discovery cannot find the viewer, it reports "The Audit Snapshot Viewer was not found." after the agent files are already written.

The package carries no schedule.

Re-create the agent installer for an E-mail or FTP source

The E-mail and FTP audit source windows have an Audit Agent Installer group. It holds a Windows schedule (every 1 to 365 days, 1 by default, at a start time), a Mac OS schedule (chosen weekdays at a start time), and the Create Installer... button. The Portable Audit Source window has no such group.

  1. In the E-mail or FTP audit source window, click Create Installer... in the Audit Agent Installer group. You can also use Create Installer... on the Actions menu of the audit-source toolbar in the Site window.
  2. In the Deploy Agents dialog, which offers no Linux option, choose a folder and select Windows, Mac OS, or both.
  3. Click Deploy.

Alloy Discovery writes:

  • Windows: AlloyAuditAgent.msi in the chosen folder, a copy of the agent installer that Audit Tools installed, with the source's audit profile and Windows schedule embedded. If the PrepareAuditAgent.cmd script in the Alloy Discovery folder contains a line that is not blank and does not begin with ' or REM, Alloy Discovery runs the script and passes it the path of the new file. The Alloy Discovery installer creates this script when it installs and never overwrites an existing one.
  • Mac OS: AlloyMacAuditAgent.zip, which holds the agent package, its configuration, and the Mac OS schedule.

Re-run the new installer on each remote machine.

Associate snapshot files with the Audit Snapshot Viewer

Audit snapshot files have the .adt or .adtx extension. The Audit Tools installer associates .adt files with the Audit Snapshot Viewer, with the Open with Alloy Audit Snapshot Viewer command. It does not associate .adtx files.

To register the .adt association again, start the Audit Snapshot Viewer, AdtViewer.exe, with the argument /REGISTER (or -REGISTER). The viewer associates .adt files only; it registers no other extension. If that registration fails, the viewer registers the association for the current user instead, and its confirmation message ends with "(for the current user)." In both cases, the viewer clears the current user's earlier Windows choice of application for .adt files.

To associate .adt or .adtx files by hand, use either procedure below. Neither the installer nor the viewer associates .adtx files, so associate them this way.

In Windows 10 and later:

  1. In Windows Settings, go to Apps > Default apps and click Choose default apps by file type.
  2. For the .adt or .adtx extension, choose Alloy Audit Snapshot Viewer as the default application.

From a snapshot file's properties:

  1. Open the Properties of an .adt or .adtx file.
  2. In the Opens with field, click Change.
  3. Under Other options, click Alloy Audit Snapshot Viewer.
  4. Click OK twice.