How can we help?

What Auvik Handle vs What Customers Need to Manage

Follow
  • Auvik-managed (always): Collector software/agent updates happen automatically during maintenance windows. A restart, if needed, is scheduled in that window. No action needed unless Support instructs you. For more information, click here.

  • Sometimes Auvik-managed: On Ubuntu-based OVA and bash-scripted collectors, Auvik also patches the underlying Ubuntu OS (within the supported release track). Major OS upgrades still require your action

  • Customer-managed (You):

    • Windows OS updates/patching. 

    • Docker image pulls/redeploys (Auvik does not auto-update the container image). 

    • Any major OS version change (e.g., 22.04→24.04, Bullseye→Bookworm). 

    • Keeping to supported OS versions—collectors on EOS operating systems must be upgraded to keep working. 

       

Deployment matrix (who updates what)

Deployment type

Underlying OS (examples)

Who updates collector software

Who updates OS (patches)

Who does major OS upgrades

Notes

Windows Service (native)

Windows 10 22H2+; Windows Server 2016+

Auvik (auto)

You (Windows Update/enterprise tools)

You (e.g., Windows 10 →Windows 11 migration or Windows Server 2022 to Windows Server 2025 )

Windows versions & requirements listed in installer docs. For more information, click here.

OVA (virtual appliance)

Ubuntu 22.04/24.04 (Auvik OVA)

Auvik (auto)

Auvik (Ubuntu patches within the supported track)

You (e.g., Ubuntu 22.04→ Ubuntu 24.04 migration)

OVA is not supported on Hyper-V or Raspberry Pi hardware. For more information, click here.

Bash-scripted (dedicated VM/host)

Ubuntu LTS (dedicated system)

Auvik (auto)

Auvik (Ubuntu patches within the supported track)

You (follow migration guides)

Scripted install “takes over” the machine; dedicate the host. For more information, click here.

Docker container (x86_64/ARM64)

Linux host or Raspberry Pi OS

You (pull/redeploy image)

You (host OS patches)

You

Auvik cannot auto-update the Docker image. Keep image current to avoid stability issues. For more information,  click here.

ARM64 (Raspberry Pi) – Docker

Raspberry Pi OS (Bookworm) or Ubuntu

You (pull/redeploy image)

You (Pi OS/Ubuntu patches)

You

ARM64 options and bases are outlined in the ARM64 FAQ. For more information,  click here.

ARM64 (Raspberry Pi) – native package

Debian/Ubuntu on ARM64

Auvik updates the agent package;

Auvik (Ubuntu patches within the supported track)

You

Option provided via native Debian/Ubuntu package; dedicate device if using “take over” style install. For more information,   click here.

 

Note: If you’re ever unsure whether Auvik manages OS patches for your specific Linux deployment, check whether it’s an OVA or bash-scripted Ubuntu install (Auvik patches those), or something you manage (e.g., Docker), which you must patch and update yourself. 

Practical examples

  • Ubuntu OVA on 22.04 → staying on 22.04:
    Auvik updates the collector automatically and applies Ubuntu security patches. No action needed.

  • Ubuntu OVA 22.04 → want 24.04:
    You perform the OS upgrade using Auvik’s migration steps, then Auvik continues patching within 24.04. For more information, click here.

  • Windows Service collector:
    Auvik updates the collector software; you keep Windows patched per your policy. If Windows goes EOS, update Windows to remain supported. For more information, click here.

  • Docker :
    You docker pull auviknetworks/collector:latest and redeploy; you also keep Raspberry Pi OS up to date. Auvik does not auto-update the container image. For more information, click here.

    • for docker, underlying OS / hardware doesn't matter: be it on a VM or Raspberry, etc

  • Running on an EOS Linux (e.g., Ubuntu 20.04 after grace period):
    Collectors will stop connecting; migrate to a supported OS (e.g., 22.04/24.04). For more information, click here.

     

Summary:

  • Collector agent updates: Auvik’s got it.

  • OS patching: Auvik covers it on OVA and bash-scripted Ubuntu collectors; you cover it elsewhere.

  • Major OS version changes: You do them—use the migration docs.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request