Installation
Access Analyzer runs on a single Linux server that you own. You download one installer binary, run it as root, and answer a few prompts. The installer downloads the release's offline media from Netwrix (or reads media you downloaded for an air-gapped server), checks the server, sets up every service, and prints the address and credentials you use to sign in.
An installation takes three steps, each on its own page.
- Requirements—pick a size, confirm the server has enough CPU, RAM, and disk (including about 16 GB for the install media), and gather the license key, hostname, TLS certificate, and first administrator's email address before you start.
- Install Access Analyzer—copy the certificate to the server and run
dspm-installer, either answering the prompts or passing everything as flags. - Sign in for the first time—open the web application, change the first administrator's one-time password, and either connect Active Directory or Entra ID or skip that step for later.
After the first sign-in, the Guides show you how to scan your first source.
Once Access Analyzer is running, see Upgrade to a new version for how new releases roll out and when you need to act, or Rolling back to a previous version if an upgrade causes problems. To move a registry install onto downloaded media, or to connect an air-gapped install, see Convert or connect an install. To replace the TLS certificate without reinstalling, see Rotate the TLS certificate.
People You Need
You need an administrator with root access to the Linux server, either signed in as root or using sudo. The installer writes to /etc/dspm, /var/log, and /usr/local/bin, so a non-root account can't complete it.
You also need someone who can issue a TLS certificate for the server's hostname and someone who can open firewall ports. The Requirements page lists exactly what to ask for.
Scripting or Troubleshooting an Installation
The Installer reference lists the flags, environment variables, exit codes, and preflight checks, for when you script an installation or need to find out why one stopped.
To read a service's logs on the server, or to collect a support bundle for Netwrix Support, see View and export logs.