System Requirements

On this page

The server, database, IIS, HTTPS, and installer prerequisite requirements on this page apply to on-premises installations. For Alloy Navigator Cloud, the service provider meets them; see Administering Alloy Navigator Cloud.

Server requirements

The minimum server below is sized for all components on one machine serving 10-15 technicians and 1,500 computers:

Requirement Minimum
CPU 2.5 GHz quad-core
RAM 8 GB
Free disk space 20 GB
Operating system 64-bit Windows Server 2012 R2 through 2025
IIS 7.5 or later
HTTPS A trusted certificate

For every additional 500 computers and five technicians, add 1 GB of RAM and 5 GB of disk space. A Windows client operating system is for testing and evaluation only.

When SQL Server and IIS are hosted on separate machines, configure the database server and the web server to operate in the same time zone. Otherwise, dates and times can be processed inaccurately, and system functionality can be disrupted. No installer check compares the time zones. You can adjust the time zone of the API manually in the Admin Center, on the API's Timezone tab (see API Settings). Its Timezone list sets the time zone for timestamp values from Alloy Navigator; when no time zone has been set, the list shows the time zone of the computer that hosts the Admin Center.

Database requirements

Engine Supported versions Notes
Microsoft SQL Server 2012, 2014, 2016, 2017, 2019, 2022, 2025, each also in its Express edition The installation package can install SQL Server 2017 Express for you
Azure SQL Azure SQL Database, Azure SQL Managed Instance Service tier S3 or greater is recommended for production; ticket archiving is not supported on Azure

Both 32-bit and 64-bit SQL Server are supported.

A database that the Database Management wizard creates on Azure SQL Database starts on the Basic service objective.

The SQL Server login that creates the database must hold the sysadmin role.

Neither the Web App, Self Service Portal, and API setup programs nor the Web Configuration tool of this release require the installing account to hold the securityadmin role on SQL Server.

The Database Management wizard refuses a SQL Server older than 2012 with the message "Your version of Microsoft SQL Server is not supported. Use Microsoft SQL Server 2012 or later." The wizard offers no override.

IIS requirements

The Web App, the Self Service Portal, and the API rely on the same IIS components:

  • Under Common HTTP Features: Static Content, Default Document, HTTP Errors, and HTTP Redirection
  • Under Application Development: ASP.NET, .NET Extensibility, ISAPI Extensions, and ISAPI Filters
  • Under Security: Request Filtering, and Windows Authentication if a web instance will use Windows authentication
  • The IIS Management Console
  • Static Content Compression

Static Content Compression and HTTP Redirection are alternatives: either one satisfies the requirement.

The installer's IIS check on the Web App, Self Service Portal, and API targets always requires the Windows Authentication role service, whatever authentication method you plan to configure for the instance. If you plan to use Standard authentication and the Windows Authentication role service is not installed, the check fails.

On IIS 7.5, 8.0, 8.5, and 10.0, the installer's IIS check does not verify Static Content Compression or HTTP Redirection, so a passed check does not confirm that either one is installed.

Install the IIS components

On Windows Server, the components above are role services of the Web Server (IIS) role, which you install with the Add Roles and Features Wizard of Server Manager. For the wizard itself, see Microsoft's Add or Remove Roles and Features in Windows Server and Installing IIS 8.5 on Windows Server 2012 R2.

  1. In Server Manager, select Dashboard, and then click Add roles and features.
  2. In the Add Roles and Features Wizard, on the Before you begin page, click Next.
  3. On the Select installation type page, click Role-based or feature-based installation, and then click Next.
  4. On the Select destination server page, click Select a server from the server pool, select the web server, and then click Next.
  5. On the Select server roles page, select Web Server (IIS). When the wizard asks to add the features that Web Server (IIS) requires, keep Include management tools (if applicable) selected and click Add Features. Then click Next.
  6. On the Features page and on the Web Server Role (IIS) page, click Next.
  7. On the Role Services page, expand Web Server and Management Tools, and select the components from the list above:

    • Expand Common HTTP Features, and select Static Content, Default Document, HTTP Errors, and HTTP Redirection.
    • Expand Application Development, and select ASP.NET, .NET Extensibility, ISAPI Extensions, and ISAPI Filters.
    • Expand Security, and select Request Filtering and Windows Authentication. The installer's IIS check requires Windows Authentication whatever authentication method you plan to configure.
    • Expand Performance, and select Static Content Compression.
    • Under Management Tools, select IIS Management Console.

    When a role service you select needs other role services or features, the wizard asks to add them: click Add Features.

  8. Click Next. On the Confirmation page, confirm your selections, and then click Install.

  9. When the installation finishes, click Close to close the wizard.

On a Windows client operating system, which is for testing and evaluation only, turn on the same components under Internet Information Services in Turn Windows features on or off.

HTTPS

Serve every Alloy web application over HTTPS. Obtaining a trusted certificate, binding it in IIS, and redirecting any remaining HTTP traffic to HTTPS are the administrator's work. Self-signed certificates are acceptable for testing and evaluation only.

When someone opens the Web App over HTTP, the Web App shows an HTTP Not Supported page with the text "You are attempting to access Alloy Navigator using the insecure HTTP protocol, which is no longer supported. Please try using the automatically generated link below to access this page via the secure HTTPS protocol, or contact your Alloy Navigator administrator for a new link." The Try this link link below it opens the same page over HTTPS. When the browser is Internet Explorer, the Web App instead redirects the request to the same address over HTTPS. The Self Service Portal and the Admin Center's back end redirect a plain HTTP request to HTTPS.

The installer checks HTTPS only when it finds an installed Web App or Self Service Portal of a version earlier than 2024. A first-time installation is not checked by the installer.

Administrative privileges

The setup programs run with administrative privileges. The Alloy Navigator and Administrative Tools setup programs relaunch themselves with administrative privileges when they are not already running elevated. The Web App, Self Service Portal, and API setup programs require administrative privileges, so Windows asks for elevation when they start.

Prerequisites the installer checks

The installer builds a different prerequisite list for the evaluation route and for each advanced target, so a check that blocks one target is absent for another:

Check Evaluation Alloy Navigator Web App Self Service Portal API SQL Server Express
Product compatibility Yes Yes Yes Yes Yes -
Operating system version Yes Yes Yes Yes Yes Yes
Physical memory Yes Yes Yes Yes Yes Yes
IIS state Yes (fresh install, or a web upgrade) - Yes Yes Yes -
.NET Framework 4.8 Yes Yes Yes Yes Yes Yes
ASP.NET Core Hosting Bundle Yes (fresh install, or a web upgrade without the module) - Yes (fresh install, or an upgrade without the module) Yes (fresh install, or an upgrade without the module) - -
PowerShell Yes Yes Yes Yes Yes -
Free disk space Yes Yes Yes Yes Yes Yes
HTTPS on existing instances On upgrade - On upgrade On upgrade - -

What each check verifies:

Check Passing condition
Product compatibility No incompatible Alloy product is installed on the computer.
Operating system version 64-bit Windows 8 or Windows Server 2012 or later passes. When SQL Server is being installed, anything older fails. Otherwise, 32-bit Windows 8 or Windows 10 and later, and Windows 7 SP1 or Windows Server 2008 R2 SP1, also pass. A domain controller fails on the evaluation route, whether or not SQL Server is installed, and on the SQL Server Express target.
Physical memory 1 GB when SQL Server is being installed, otherwise 500 MB.
Free disk space The free space on the Program Files volume is at least the sum of the budgets of the components being installed (see below).
.NET Framework 4.8 .NET Framework 4.8 is installed.
ASP.NET Core Hosting Bundle The ASP.NET Core Module is at version 16.0.21322.1 or later.
PowerShell The PowerShell 3 engine is registered on the computer. When it is not, the check asks for PowerShell 3.0 or later, up to 5.1.
IIS state IIS is installed and configured, and the World Wide Web Publishing service is running. The installer offers to start the service.
HTTPS on existing instances Every existing Alloy web instance has an HTTPS binding. HTTP together with HTTPS produces a warning; HTTP alone fails the check.

The product compatibility check fails when it finds any installed product of the Alloy Navigator Express version 8 lineage (Alloy Navigator Express, its Web App, Self Service Portal, Mobile Portal, or API), an Administrative Tools 8 package of either edition, or the Mobile Portal 8. On the evaluation route only, it also fails when it finds an existing Alloy Navigator 8, Alloy Discovery 8, Web App 8, Self Service Portal 8, or API 8. An installation of Alloy Navigator Express 6 or 7 is not detected.

The Alloy Navigator setup program makes a check of its own when it runs with its user interface: when it finds a product of the Alloy Navigator Express version 8 lineage or an Administrative Tools 8 package of either edition, it lists those products in an error message and stops the installation.

The disk space budget of each component:

Component Budget
SQL Server Express 4300 MB
.NET Framework 4.8 2560 MB
ASP.NET Core Hosting Bundle 390 MB
Alloy Navigator 600 MB
Alloy Discovery 500 MB
Web App 120 MB
Self Service Portal 32 MB
API 32 MB

The evaluation route starts from the Alloy Navigator and Alloy Discovery budgets and adds the three web budgets only after the IIS check has passed, so the disk figure the installer shows changes as the checks run.

On the evaluation route, a failed operating system check or memory check stops the installation. On the advanced route, the same failures produce a warning instead, except that the operating system check still fails on the SQL Server Express target, and a domain controller fails as described for the operating system check.

The checks run when the prerequisites page opens and again each time you click Recheck. Recheck picks up a PATH change made by a prerequisite you just installed, without restarting the installer. Next (Upgrade when the installer upgrades existing products) stays unavailable until no check has failed; a warning does not block it.

Click the message of a check to open its details. The details can show a link and, for the .NET Framework 4.8 and ASP.NET Core Hosting Bundle checks, a button that runs the installer of the missing component and closes the details.

When the installer installs the ASP.NET Core Hosting Bundle (on the evaluation route, or on a Web App or Self Service Portal target whose hosting bundle check failed), it restarts IIS without asking, so every site on the computer stops and restarts during that step.

SQL Server Express Advanced is downloaded at install time. An evaluation installation of SQL Server therefore needs outbound network access, unless a matching setup file is already in the installer's Redist folder.

Node.js is not a prerequisite: the Self Service Portal package installs its own Node.js runtime. The Microsoft OLE DB Driver for SQL Server has no prerequisite check either. The Alloy Navigator, Administrative Tools, Web App, Self Service Portal, and API setup programs each install version 19 of the driver silently, when one of the Alloy products in their list is installed on the computer, neither version 18 nor version 19 of the driver is installed, and the driver's provider is not registered on the computer.

When the installer upgrades existing products, it also checks for running Alloy applications, such as the Database Management wizard and the Web Configuration tool, before it moves past the Upgrade Prerequisites page and again before it moves past the Ready to Upgrade page. It lists each running application with its file name and process ID and does not move on. It does not close them: close the applications yourself and try again. A fresh installation does not make this check, and neither do the targets of the Advanced Installation route.

Client requirements

Web client requirements (Web App and Self Service Portal)

The minimum is the two latest released versions of Microsoft Edge, Google Chrome, and Mozilla Firefox, and the two latest released versions of Apple Safari on macOS. Depending on the browser, you may need to configure it: JavaScript, cookies, and local storage must be enabled.

The Web App shows a dismissible banner for outdated browsers: Internet Explorer 9 and earlier, Firefox below version 16, Chrome below version 16, and Safari below version 5. The banner warns and does not block, and it is not the supported browser list.

Administrator desktop component requirements

For the desktop components used by administrators, such as the Settings App:

Requirement Minimum
Operating system 64-bit only: Windows 7, 8, 8.1, 10, and 11; Windows Server 2008 R2, 2012, 2012 R2, 2016, 2019, 2022, and 2025
CPU 2 GHz dual-core
RAM 1 GB
Free disk space 600 MB, plus up to 750 MB for extracting the installation files, which is freed after installation
Display WXGA (1366 x 768); FHD (1920 x 1080) is recommended

To view and print reports from these desktop components, the computer also needs Microsoft .NET Framework 4.8 and Microsoft System CLR Types for SQL Server 2016. The Alloy Navigator setup program installs System CLR Types and Microsoft Report Viewer 2016 itself: after the package installs, it adds each one that is missing, provided one of the Alloy products in its list is installed on the computer. No prerequisite check tests for either, and no page of the setup lets you choose them. During an interactive installation that is neither a repair or change of the installed package nor an upgrade of the same product line, the package also installs Report Viewer and System CLR Types itself, before its finish page, when Report Viewer is not yet installed. When Report Viewer is still missing after that step, the finish page shows "Microsoft Report Viewer for SQL Server 2016 was not installed."

Of these figures, the installer's Alloy Navigator target tests only the disk space as published: the 600 MB is its Alloy Navigator disk budget. It tests memory at 500 MB rather than 1 GB, and a computer below that gets "Not enough physical memory. 500 MB physical memory is required." It sets the operating system floor at Windows 7 SP1 or Windows Server 2008 R2 SP1, and it tests neither the CPU nor the display. On this target, a failed operating system or memory check produces a warning, not a stop.

The Administrative Tools package checks two things before it installs: that no incompatible Alloy product is installed, and that .NET Framework 4.8 is installed. Its incompatible products are Alloy Navigator 8, Alloy Navigator Express 8, and the other edition's Administrative Tools 8 package. It requires neither IIS nor SQL Server, which makes it installable on an administrator workstation that works with an Alloy Navigator Cloud tenant (see Administering Alloy Navigator Cloud). The Administrative Tools package and the full Alloy Navigator package cannot be installed on the same computer.

In an interactive installation of the Administrative Tools package, when .NET Framework 4.8 is missing, the package asks "Microsoft .NET Framework 4.8 was not found... Continue the installation?" in a dialog that also holds a link to a Microsoft page, and stops unless you answer Yes. In a silent installation, the .NET Framework check is skipped. The incompatible products check stops the installation in both cases.

Mobile client requirements

Three mobile apps work with Alloy Navigator. They are separate products with their own version lines, distributed through the app stores, and no server package installs them.

App For Account Minimum iOS version
Alloy Navigator Technicians and managers Technician account iOS 15.0
Alloy Self-Service End users Self Service Portal customer account iOS 15.0
Alloy Inventory Scanner Technicians doing physical inventory Technician account iOS 13.0

The iOS minimums apply to Alloy Navigator 2.4.91, Alloy Self-Service 1.1.43, and Alloy Inventory Scanner 2.0.50.

Each app reaches the server through the API, which must be configured for Access Token authentication (see Authentication Methods). When the URL entered in the Alloy Navigator or Alloy Self-Service app answers with a Windows authentication challenge, the app shows "Make sure the URL points to Alloy Navigator API configured for Access Token authentication". Alloy Inventory Scanner 2.0.50 shows "Unable to access this address. Make sure the URL points to Alloy Navigator API configured for Access Token authentication." when the server answers its sign-in request with a Windows authentication challenge.

Before sign-in, Alloy Navigator app 2.4.91 also checks the API version. A connection failure, a TLS handshake failure, a Windows authentication challenge, and an HTTP 505 response each produce their own error. Any other failure, and an API earlier than 8.7.0, produce "The specified URL does not point to Alloy Navigator API version 8.7.0 or later. Make sure the URL is correct." Alloy Inventory Scanner 2.0.50 reads the API version only after sign-in and refuses no server for its version.

Supported audit clients

The audit agent, Inventory Analyzer, has versions for Windows, Linux, and macOS. It is part of Alloy Audit Tools, a separate package with its own release cycle.