Unattended Installation

On this page

Each Alloy Navigator distributable is an .exe bootstrapper that hands its package to msiexec. For an unattended installation, you run these .exe files with msiexec switches.

In the installer packages

Install, uninstall, and log

  • To install, run each product's .exe file with /i /qn, and name the features to install with ADDLOCAL=.
  • To write an installation log, add /lvx <file>.
  • To uninstall, run the product's .exe file with /x /qn.

For example:

<product>.exe /i /qn ADDLOCAL=<feature list> /lvx <log file>

Nothing configures the installation after an unattended installation: the database and the web instances still need to be set up, and the Automation Server service started, by other means. On an upgrade, an Automation Server that was running before the upgrade is started again afterward, and uninstalling the Automation Server also removes its Windows service. The Web App, Self Service Portal, and API packages install templates, not running sites; the Web Configuration tool turns a template into an IIS application. On an upgrade, each of these three packages saves the configuration of its existing instances before the older version is removed, and recreates the instances from that configuration afterward. Uninstalling one of these packages removes the instances published from its template. The Web App package also delivers the Admin Center, which has no package of its own. For the server components, see Install the Server Components.

An unattended run does not upgrade the database either; the database is upgraded with the Database Management wizard. While the database version differs from the version of the installed components, the Settings App, the Automation Server Manager, the Import Wizard, the command-line tools, the Web App, the Self Service Portal, and the API refuse the database, and the Automation Server service logs the mismatch and keeps retrying. The Settings App and the Automation Server Manager show an error that names both versions.

Previous version removal

  • When a later argument is /quiet, /passive, /qn, or /qb, the Alloy Navigator .exe file silently uninstalls each installed Alloy Navigator version 6 or 7 product before the new package starts.
  • To keep the version 6 or 7 installation, also pass OLD_PRODUCT=Keep. The value is compared without regard to letter case.
  • This removal is done by the .exe file. A silent msiexec run of the package's extracted MSI does not remove a version 6 or 7 product.
  • When the setup runs interactively, the .exe file removes no older product itself. On a first installation that finds a version 6 or 7 product, the setup's Previous Installations page offers the removal instead; the page is not shown when OLD_PRODUCT is set, and OLD_PRODUCT=Keep keeps the older product.
  • Of the product .exe files, only the Alloy Navigator one removes a version 6 or 7 product. The Self Service Portal .exe file, for example, removes no older product.
  • An installed earlier release that the package upgrades directly is upgraded in place, also silently, and cannot stay beside the new version.

How the .exe files read the command line

Every Alloy Navigator product .exe file reads its command line the same way:

  • Run with no arguments, it installs, as with /i.
  • Otherwise, its first argument must be /package, /i, /a, /j, /ju, /jm, /uninstall, /x, or an argument that starts with /f. Any other first argument, /qn included, opens the msiexec /help window and installs nothing.
  • Every later argument is passed on to msiexec, quoted when it contains a space. The .exe file then adds SETUPEXEDIR, set to its own folder.
  • /quiet, /q, and /qn hide the extraction dialog and the bootstrapper's own messages. /passive and /qb are passed on to msiexec but still show the extraction dialog.
  • Only one of these .exe files runs at a time. A second one started while another runs stops. When the run is not silent, it shows "Another installation is in progress. You must complete that installation before continuing this one."
  • The exit code is the exit code of msiexec, or 1 when msiexec did not run.

What the .exe files do before installing

  • The Alloy Navigator and Administrative Tools .exe files relaunch themselves with administrative rights when they are started without them, and return the exit code of the relaunched run. Windows asks for elevation when a Web App, Self Service Portal, or API .exe file starts.
  • When a legacy version 8.x product is installed, the Alloy Navigator .exe file changes conditions in that product's cached Windows Installer package in place before it runs the new package.
  • When an Alloy web product of version 8.7.2 or 2024.2 (24.2.0) is installed, the Web App, Self Service Portal, and API .exe files replace that version's Web Configuration tool before they install. They first close every running copy of the Web Configuration tool, from any folder, without a prompt. When the old tool cannot be deleted, it stays in place and no message is shown.

Client and server installation

Setting AN_SETUP_TYPE on a silent command line does nothing: a silent install without ADDLOCAL installs the entire feature tree. Use ADDLOCAL to choose the features.

The interactive setup types start from the full feature tree: Client leaves out the AutomationServerNew subtree, Server leaves out the MainConsole feature, and Full leaves out nothing.

Installation ADDLOCAL value Compared with the interactive setup type
Client only AlwaysInstallNew,AdminTools,AdminManager,DBTools,SLQTools,System,MainConsole Matches the interactive Client setup type. MainConsole installs the report viewer, the Audit Viewer parts, the English spell-check dictionary, and the barcode font.
Server only AlwaysInstallNew,AdminTools,AdminManager,DBTools,SLQTools,System,AutomationServerNew,ServerManager,ImportContactsNew,MailConnectorNew,AlloyDAS,DiscoveryConnector,ScheduledTasks,AsScanConn Matches the interactive Server setup type, including the Scheduled Task Agent and AlloyScan Connector.

What the features in these lists hold:

  • AdminTools holds Settings and Database Tools. Database Tools includes the Database Management wizard, the Import wizard, and the database backup tool.
  • AutomationServerNew holds the Automation Server and the Server Manager, Active Directory Import, Mail Connector, Data Archiving Service, Scheduled Task Agent, Alloy Discovery Connector, and AlloyScan features. Its child features ImportContactsNew, MailConnectorNew, AlloyDAS, ScheduledTasks, DiscoveryConnector, and AsScanConn can be selected one by one, so an installation can have the Automation Server without a given job executable.

Alloy Discovery package

Alloy Discovery is a separate product. The only Alloy Discovery part of the Alloy Navigator package is the Alloy Discovery Connector feature, a tool for importing inventory data from Alloy Discovery.

The Alloy Discovery package has two features, Client and Server. ADDLOCAL=Client installs the client feature. As in the Alloy Navigator package, a silent run that omits ADDLOCAL installs both features, and setting AD_SETUP_TYPE does not narrow a silent install. On an upgrade from Alloy Discovery 6 or 7, the package sets the features itself: both features when the old installation had the Data Collector component locally, otherwise the client feature.