Get Started with Alloy Navigator Cloud
On this page
The provider supplies your hosted web applications and download links for the Windows administrative tools and optional agents. You do not run server-side setup for Alloy Navigator Cloud. Cloud and on-premises installations use the same software, with Cloud behavior controlled by the license. For Cloud administration, see Administering Alloy Navigator Cloud.
What Alloy Navigator Cloud provisions
On your side, a Cloud installation is the Administrative Tools package plus optional agents. Besides the links to the hosted web applications, the download set is:
- Administrative Tools package (
AlloyAdminTools-<version>.exe) - installs the Windows tools you run locally. - Audit agent (
AlloyAuditAgent.msi) - a preconfigured audit agent for Windows computers. It runs audits regularly and delivers the results automatically to the cloud-hosted Alloy Discovery and Alloy Navigator. It installsina32.exeunderAlloy Shared\Ina32\4.0\Bin. When the package's configuration component is installed, it also registers a daily Run Audit Agent scheduled task that runsina32.exeas SYSTEM. - Audit Snapshot Viewer (
AuditViewer-<version>.msi) - installs the Audit Snapshot Viewer for viewing snapshots outside Alloy products. During installation, leave Associate .adt files with Alloy Audit Snapshot Viewer selected. - Alloy Discovery (
AlloyDiscoverySetup-<version>.exe) - an on-premises Alloy Discovery that can sync data with the cloud-hosted Alloy Navigator. - Database Access Keys (
AlloyNavigatorKey.zipandAlloyDiscoveryKey.zip, typically zipped.regfiles) - must be imported before the first login to Alloy Navigator Settings or Alloy Discovery.
In the Administrative Tools
Install the Administrative Tools package
The Administrative Tools package is an installer around a signed 64-bit (x64)
Windows Installer package. It installs five Windows tools together, into the
Alloy Navigator program folder, plus Utils in the shared Alloy Shared
folder:
| Tool | File |
|---|---|
| Settings App | Bin\AlloyNavigatorMngr.exe, with a Start-menu shortcut Settings under Tools |
| Import tool | Bin\ImportWizard.exe |
| Active Directory Import | Bin\ImportContacts.exe |
| Scheduled Task Agent | Bin\ScheduledTasks.exe, which announces itself as "Alloy Navigator Scheduled Task Agent" |
| Alloy Control Panel | Utils\AlloyControlPanel.exe, with Start-menu and desktop shortcuts |
Before you begin:
- No incompatible Alloy product is installed on the computer.
The installer requires neither IIS nor SQL Server, so you can run it on an ordinary administrator workstation. When it is not already running elevated, it relaunches itself with administrative rights.
Before installing, it checks for incompatible Alloy products and stops if it
finds one, in a silent installation too, where it stops without showing a
message. It also checks for .NET Framework
4.8; if the check does not find it, you see a message asking "Microsoft .NET
Framework 4.8 was not found... Continue the installation?", with a link to
https://go.microsoft.com/fwlink/?linkid=2088631. Answering Yes
continues the installation, and any other answer stops it. In a silent installation this .NET Framework
check does not stop the installation.
After an interactive first installation that the installer relaunched with administrative rights, the Alloy Control Panel starts for the user who ran the installation.
Under a Cloud license, the distribution upload and the automatic upgrade use the Administrative Tools installer instead of the full product installer; see Administering Alloy Navigator Cloud.
Import a Database Access Key
The Administrative Tools connect to the database through a Database Access Key
kept in the computer's registry. The Access Key Import dialog loads a key
into it: click Load from File... to open a key file (*.reg, or any file),
or paste the key text directly into the box. Signing in over the legacy
connection instead installs the key that the database already stores.
For more on Database Access Keys, see Database Access Key and Connections.
Ports to open
Open the following ports for the Cloud components:
- 80 (HTTP) - redirected internally to 443.
- 443 (HTTPS) - used by the product's web components: Web Portal, Self Service Portal, and API.
- 51967 - a custom SQL Server port used by locally installed Windows applications such as the Settings App.
- 22 (SFTP) and 21 (FTP Secure) - used by network inventory components to deliver audit snapshots.
- 49152-65535 - serve passive FTP for the same delivery.
Self-hosted cloud
Self-hosted cloud is an on-premises installation on a rented machine, for example an AWS or Azure instance; the process is very similar to installing on-premises. Follow the on-premises installation; see Installation Overview.
| Decision | Guidance |
|---|---|
| Instance size | AWS t2.medium or Azure B2s with Windows Server 2012 or later; SQL Server Express below 10,000 computers and 100 technicians, Standard or Enterprise above |
| Inbound traffic | Open only the web applications' port to any source; close every other port except to your organization's own public address |
| Database reachability | Open the Database Engine's TCP port to your organization's local network only, so desktop tools can reach it |
| Administration | Remote Desktop with the Settings App on the server, or a local Client installation driven by the imported Database Access Key |
Place the data center as close as possible to your organization's local network: the desktop tools used for administration run over that link.
Create the database against a fully qualified domain name or a static IP
address, together with the instance, for example
alloyserver.mycompany.com\SQLEXPRESS. The Database
Access Key records the server name given at creation time, so a database
created against a short or local name produces a key that desktop tools
outside the cloud network cannot use.
For user authentication, Standard authentication is recommended so the cloud server does not have to join the domain; a server that does join the domain can use Windows authentication. For the authentication options, see Authentication Methods. Active Directory Synchronization requires that the cloud server has access to a domain controller, on-premises or in the cloud.
In a new database created with the Default Workflow (see Default Workflow Configuration), the workflow creates customer accounts for Active Directory users with Windows authentication. With Standard authentication, customize that workflow. An upgraded database need not have this configuration, and an administrator may have changed it.
The Database Management wizard places the Database Access Key generated with
the database on the cloud server's desktop by default, named
AlloyDBAccessKey_[ServerName]_[DatabaseName].reg, with spaces and characters
that file names cannot contain replaced by _. The Settings App on a local
Client installation signs in with it. Every computer that must reach the
database, including the Automation Server host, each web server, and each
technician workstation running the Settings App, needs a registered copy of the key,
distributed as the .reg file or as an encoded string.
Alloy Discovery normally runs on your local network, where it can reach computers without compromising the network. With a cloud database, you install two instances: on the cloud machine, a Full (Client and Server) installation creates the Alloy Discovery database against the server's fully qualified domain name and generates a Database Access Key, then its Inventory Server service is stopped and its startup type set to Disabled. On a local server, a second Full installation skips database creation and has its Inventory Server configured against the cloud database with that key.