This is the administrator documentation for Vizrt Asset Management (VAM): installing it, operating it, and using the Configuration Service that ships with it.

Start with the section that matches the task in front of you. Each section stands on its own, so there is no need to read them in order.

Sections

Installer

End-to-end guide for installing VAM on a Windows host using the vamctl installer.

  1. Installer Overview
  2. Prerequisites
  3. OIDC Authentication Provider Configuration
  4. Running the Installer
  5. Post-Install Validation
  6. Upgrading
  7. Uninstalling
  8. Troubleshooting the Installer
  9. Identity Provider Setup
  10. VMware vSphere Deployment
  11. Offline (Air-Gapped) Installation
  12. Existing Kubernetes Cluster

Configuration Service

Operator guide for the Configuration Service — the in-cluster web UI used to manage packages, platform settings, certificates, backups and cluster health after installation.

  1. Configuration Service Overview
  2. Signing In
  3. Managing Packages
  4. Platform Settings
  5. Backup and Restore
  6. Cluster and Health
  7. Troubleshooting the Configuration Service

Conventions

  • Screenshots are taken from the latest released installer and configuration UI. If a screen in your installation looks different, check that you are on the matching VAM version (the installer's status bar and the configuration UI's footer both show the version number).
  • Code-style boxes show literal text — file paths, command lines, or values you type into a UI field.
  • Where a step requires elevated privileges or affects a running production cluster, it is marked with a Warning callout.

Getting Help

For support, contact your Vizrt support representative. When opening a support case, include:

  • The VAM version (visible in the installer status bar and the Configuration Service footer).
  • The installer log bundle, produced by Help → Export logs in the installer, or located at %APPDATA%\Vizrt\vamctl\logs\ on the installer host.
  • A description of what you were doing when the issue occurred.