Linux - Software - Install TeamViewer Host

What the TeamViewer Host Installer does

This Automox Worklet™ installs TeamViewer Host on Linux endpoints to enable remote access and support capabilities. The Worklet identifies your Linux distribution by reading the /etc/os-release file and determines whether to use apt, yum/dnf, or zypper for package installation.

The Worklet also detects the CPU architecture using uname -m and downloads the matching package from TeamViewer's official download repository. This approach supports x86_64, i686/i386, aarch64, and various ARM architectures, making it suitable for both standard servers and ARM-based endpoints like Raspberry Pi endpoints.

After downloading, the Worklet installs the package and verifies successful installation by checking for the teamviewer-host package in the system's package database.

Why deploy TeamViewer Host through Automox

Remote access software forms the foundation of efficient IT support for distributed Linux environments. Manually installing TeamViewer Host across endpoints with different distributions and architectures creates complexity and delays deployment timelines.

Automating TeamViewer Host deployment through Automox provides consistent installation across your entire Linux fleet. You can target specific endpoint groups, track deployment status, and verify successful installations through the Automox console. This centralized approach reduces the time IT teams spend on repetitive installation tasks.

The Worklet handles the complexity of distribution detection, architecture matching, and package manager selection automatically, so a single policy works across Ubuntu, Debian, RHEL, CentOS, Fedora, and SUSE endpoints.

How TeamViewer Host deployment works

1. Evaluation phase: The Worklet reads /etc/os-release to identify the Linux distribution and package manager. It then checks if the teamviewer-host package is already installed using rpm -qa (for yum/dnf systems), apt list --installed (for Debian/Ubuntu), or zypper search --installed-only (for SUSE). If the package exists, the endpoint is compliant.

2. Remediation phase: The Worklet determines the CPU architecture and downloads the appropriate .deb or .rpm package from download.teamviewer.com using curl. It then installs the package with apt-get install -f, dnf localinstall, or zypper install depending on the distribution. A final verification check confirms successful installation.

TeamViewer Host deployment requirements

• Linux distribution supported by TeamViewer: Debian, Ubuntu, RHEL, CentOS, Fedora, or SUSE

• Supported CPU architectures: x86_64, i686/i386, aarch64, or ARM (armv7hl)

• Network access to download.teamviewer.com for package downloads

• curl installed on the endpoint

• Root or sudo privileges for package installation

Expected state after TeamViewer Host installation

After successful remediation, TeamViewer Host is installed and available on the endpoint. The teamviewer-host package appears in the system's package manager database, and the TeamViewer service can be configured for unattended access.

You can verify the installation by running the package query command for your distribution or by launching the TeamViewer Host application. The endpoint becomes available for remote connections once you complete the initial TeamViewer configuration and link it to your TeamViewer account.

How to validate install teamviewer host changes

1. Run this Worklet on a pilot Linux endpoint and review evaluation output for install teamviewer host.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as function, source, elif.

4. Validate remediation effects from script operations such as function, source, elif, then rerun evaluation for compliance.