Skip to main content

Deploy with AXIS Device Manager

AXIS Device Manager (ADM) is Axis's on-premises tool for Windows. It installs apps and pushes settings to many cameras at once. You need the Anava .eap file from anava.ai/download. To get ADM, see axis.com/products/axis-device-manager.

Deploy with AXIS Device Manager4 minWalkthrough video coming

Before you start​

  • Use ADM 5.34 or later, on a Windows PC that can reach the cameras over HTTPS.
  • Copy the .eap file to a local drive of that PC. ADM can hang when it installs from a network share or a remote-desktop path.
  • Clear stale camera passwords from every other tool on that PC: AXIS Camera Station, VMS servers and scripts. Hardened Axis cameras block a PC after a few failed logins. One tool that keeps retrying a wrong saved password locks ADM out too.

Install the app on many cameras​

  1. Open ADM and go to Device Manager. Make sure the cameras are listed and you are signed in to them.
  2. Select the cameras. The package must match each camera's chip and AXIS OS version, so sort the list by model and install one family at a time. See Which package fits which camera.
  3. Right-click the selection and choose Install App....
  4. Choose the Anava .eap file.
  5. ADM asks a question about a license. Answer No. Anava does not use an Axis license key.
  6. Select Finish and watch the Tasks tab until every camera reports success.

Then check that the app runs. On one camera, open Apps in the camera's web page and look at the status of Anava Agent. Start it if it is stopped.

Open the console on one camera​

Open the console on one camera and set it up the way the whole fleet should run: rules and plate settings. This camera is your reference camera.

  1. In the camera's web page, go to Apps, select Anava Agent, then Open.
  2. Sign in with the camera's administrator account.
  3. Set up the camera. See Open and sign in to the console if you need help finding your way.

Make the settings file​

  1. In the console, go to Fleet template, then Exports.
  2. Select Download .cfg.
  3. Save the file. It is an ADM configuration file that holds the Anava settings.

Passwords and secrets are never in the file. The camera name, its image channels, its SD card settings and any LLM gateway token also stay out. Set those per camera in ADM.

Push the settings​

  1. In ADM, select the cameras that should receive the settings.
  2. Right-click and choose Configure Devices, then Configure....
  3. Select Use configuration from: Configuration File and choose the file you saved. The Anava parameters it carries are ticked.
  4. Select Next, then Finish. Watch the Tasks tab.

Each camera applies the settings within about 15 seconds, with no restart.

warning

Never tick every row. ADM lists every camera setting, including the network and user settings, and a push with all of them ticked overwrites all of them on every camera it reaches. The Anava file ticks only the Anava rows. If you pick rows yourself, type Lite in the search box, click any row, press Ctrl+A, then Space.

Skip the file: copy from a camera​

You can also let ADM read the settings from the reference camera.

  1. In the console, go to Fleet template, then Publish and lock, and publish the template on this camera.
  2. In ADM, choose Configure Devices, then Configure..., then Use configuration from: Device, and pick the reference camera.
  3. Tick only the Anava rows, as the warning above says.

Check that it took​

ADM does not show the policy status, so read it from one camera. Open this address in a browser, signed in as the camera's administrator:

http://<camera-ip>/axis-cgi/param.cgi?action=list&group=root.AnavaAgent.LitePolicyStatus

The value is one of these:

  • applied <name> v<number> <time>: the camera runs the settings.
  • ... (changed on camera: ...): someone changed that setting on the camera. The next push puts it back.
  • rejected <name>: <reason>: nothing changed. The camera keeps its last good settings, and the reason names the value to fix.

You can also check from a camera's own console: Fleet template, then Status, says whether the camera runs the template as applied.

Upgrades and resets​

Upgrading, reinstalling the same version and installing an older version all keep the app's settings. Only removing the app clears them.

To start a camera over, remove the app, install it again, then push the configuration file.

Open the console​

On each camera, open the console from Apps, then Anava Agent, then Open, or go to http://<camera-ip>/local/AnavaAgent/web/. See Open and sign in to the console.

Go further​

  • Want the cloud to check a specific thing about a frame, or speak a warning through a speaker? That is Hybrid Edge. The trial starts from the camera's console.
  • Hidden parameters, such as an LLM Gateway token, are not part of the downloaded file. See Enterprise LLM Gateway.
  • Many sites, an audit log, Ask Anava and a VMS replacement, in your own Google Cloud project? That is Anava Vision.