Deploy the virtual appliance: step-by-step guide

Which edition and format

Edition	Choose it if
Standalone	You're a business monitoring your own network. It can be a server, collector, log collector or both
MSP	You're a managed service provider. Adds the router software for MSP master collectors and router mode

Your platform	Download
VMware vSphere, ESXi, Workstation, Fusion	`.ova`
Microsoft Hyper-V	`.vhdx` (Generation 2 VM)
Proxmox, KVM, Nutanix	`.qcow2`
Physical server or anything else	`.iso` installer

Download from the customer portal's Downloads page.

Role	vCPU	Memory	Disk
Server with collector (up to 250 devices)	4	8 GB	100 GB
Collector (up to 500 devices)	2–4	4–8 GB	64 GB
Log collector	4	8–16 GB	64 GB system disk plus a separate log disk (see the log collector guide)
MSP master collector	8–16	16–32 GB	250–500 GB
MSP router	8 (with AES-NI)	16 GB	64–128 GB, 2–4 network adapters

In the vSphere Client, right-click your host or cluster › Deploy OVF Template.
Choose Local file and select the .ova. Click Next through the name, location and resource pages.
Accept the license (it's the Uplivra terms of service; you accept them again during setup).
Pick a datastore and Thin provision, and the network the appliance should use.
Before powering on, Edit settings to set CPU, memory and disk size from the table above. For a log collector, add a second hard disk.

Copy the .vhdx to where you keep VM disks.
In Hyper-V Manager: New › Virtual Machine, Generation 2, memory from the table, your virtual switch, and Use an existing virtual hard disk pointing at the .vhdx.
In the VM's Settings › Security, set the Secure Boot template to Microsoft UEFI Certificate Authority.
Set the processor count, and expand the disk if needed (Edit Disk).

Create a VM with no disk (OS: Do not use any media), CPU type host, network model VirtIO.
Copy the .qcow2 to the Proxmox host and import it:

qm importdisk 120 uplivra-standalone-26.10.1.qcow2 local-lvm

(Replace 120 with your VM's ID.) In the VM's Hardware, attach the unused disk, and under Options › Boot order put it first.

Start the VM and open its console. Uplivra's setup starts by itself and asks the same questions as the server guide, plus a few for the appliance:

Question	Answer
Terms of service	Type `I agree`
What should this computer be?	Server, collector, log collector, both, or (MSP edition) MSP master collector or router
Network	The appliance asks for its address, gateway and DNS. A fixed address is recommended
Appliance administrator password	For the `uplivra-admin` account on the console. At least 12 characters. Keep it safe
Allow SSH?	no unless you need remote command-line access
Networks allowed to manage this appliance	Your admin network, for example `10.0.0.0/24`. Enter for any. Also limits the collector's status page
Port for the collector's status page	Collector roles: Enter for 8444, or `0` for off; then its password
Ubuntu Pro token	Optional: extended security maintenance from Canonical. Enter to skip
Security updates automatically	yes

When it finishes, a server appliance shows the address to open in your browser; a collector appliance confirms it has connected.

Ubuntu LTS hardened to CIS Level 1: root can't sign in, strong passwords with lockout, AppArmor enforcing, audit logging, no unused services.
SSH is off unless you turn it on; the host firewall is closed except the ports the chosen role needs.
A legal warning banner at sign-in.
Operating system updates are managed by Uplivra: the appliance installs Ubuntu updates only up to the version Uplivra has tested with this release, every night. Ubuntu's own security updates keep running as a safety net.

sudo uplivra setup

What you see	What to do
Setup stopped or didn't finish	Restart the VM: setup runs again on every boot until it completes
No network adapters found	Add a network adapter to the VM (VMXNET3 or VirtIO) and reboot
Hyper-V says "No operating system was loaded"	Set Secure Boot to Microsoft UEFI Certificate Authority, or turn Secure Boot off