Linux - Software - Install TeamViewer Host

What the TeamViewer Host deployer does

This Automox Worklet™ deploys TeamViewer Host to Linux endpoints so IT teams can stand up unattended remote access without an SSH session per host. The Worklet sources /etc/os-release to identify the distribution family, then chooses apt for Debian and Ubuntu, yum/dnf for RHEL, CentOS, and Fedora, or zypper for SUSE and openSUSE. The endpoint never has to be manually inspected before the policy runs.

After the package manager is known, the Worklet calls uname -m and picks the matching architecture build from TeamViewer's official download host. x86_64, i686/i386, aarch64, and 32-bit ARM (armv7hl) are all covered, which keeps Raspberry Pi and small-form-factor edge endpoints in scope alongside standard servers and workstations. The Worklet downloads the correct package over HTTPS using curl -L -O against download.teamviewer.com.

Installation is delegated to the native package manager. The Worklet runs apt-get install -f -y, dnf localinstall -y, or zypper install -y against the freshly downloaded file. A final verification step queries the package database with rpm -qa, apt list --installed, or zypper search --installed-only and exits 0 only when teamviewer-host is present on the endpoint. The endpoint is then ready for the TeamViewer assignment step that links it to your account.

Why deploy TeamViewer Host to every Linux endpoint

TeamViewer Host is the unattended-access build of TeamViewer. It is the package that gives a support technician a remote session into a Linux workstation, server, or kiosk endpoint without an end user clicking accept. Without it, an admin handling a Linux incident falls back to SSH, a console, or a coordinated screen-share, which extends mean time to resolution and limits which team members can take the ticket. Deploying the host build across the fleet ahead of time is the prerequisite for unattended remote support coverage.

Apply this Worklet to the Linux server, workstation, and edge-device groups in one policy; the uname-driven architecture picker handles a Raspberry Pi, an Ubuntu developer workstation, and a RHEL build server from the same policy artifact, and the rpm -qa or apt list --installed verification confirms teamviewer-host on each one.

How TeamViewer Host deployment works

1. Evaluation phase: The Worklet sources /etc/os-release and inspects $ID and $ID_LIKE to pick apt, yum, or zypper. It then checks the package database: rpm -qa | grep -qi teamviewer-host on yum endpoints, apt list --installed | grep -qi teamviewer-host on apt endpoints, and zypper search --installed-only | grep -qi teamviewer-host on zypper endpoints. The endpoint exits 0 (compliant) if teamviewer-host is already present and exits 2 (remediation scheduled) if it is not. An unsupported distribution exits 2 with a diagnostic message in stdout.

2. Remediation phase: The remediation script re-resolves the package manager and reads the architecture from uname -m. For apt, it pulls teamviewer-host_amd64.deb, teamviewer-host_i386.deb, teamviewer-host_arm64.deb, or teamviewer-host_armhf.deb. For yum/dnf, it pulls the .x86_64.rpm, .i686.rpm, .aarch64.rpm, or .armv7hl.rpm build. For zypper, it pulls the matching teamviewer-host-suse.<arch>.rpm. Installation then runs apt-get install -f -y, dnf localinstall -y, or zypper install -y on the downloaded file. The final block re-queries the package database and exits non-zero if the package is missing, so failures surface in the Automox activity log instead of going silent.

TeamViewer Host deployment requirements

• Linux distribution supported by TeamViewer: Debian, Ubuntu, RHEL, CentOS, Rocky, Alma, Fedora, openSUSE, or SUSE Linux Enterprise

• CPU architecture in the supported set: x86_64, i686/i386, aarch64, or 32-bit ARM (armv7hl, mapped from arm5l/arm6l/arm7l)

• Outbound HTTPS reachability from the endpoint to download.teamviewer.com on port 443

• curl available on the endpoint; on minimal images, install it ahead of this Worklet with a companion policy

• Root context for package installation (the Automox agent already runs as root, so no additional privilege escalation is required)

• A TeamViewer account or company profile ready to receive the assignment step after the package is installed; this Worklet handles delivery, not licensing or device pairing

Expected state after TeamViewer Host deployment

After remediation, the teamviewer-host package is present in the endpoint's native package database. Validate by running rpm -q teamviewer-host on RPM-based endpoints, dpkg -l teamviewer-host on Debian-based endpoints, or zypper info teamviewer-host on SUSE endpoints. The TeamViewer daemon installs as a systemd unit, so systemctl status teamviewerd confirms the service is enabled and active. Binaries land under /opt/teamviewer/, with the user-facing CLI available as /usr/bin/teamviewer.

Subsequent Automox policy runs report the endpoint as compliant without applying remediation again, because the evaluation phase finds the teamviewer-host package already registered. To complete unattended access, follow this Worklet with the TeamViewer assignment command (teamviewer assignment --token <token>) or your standard enrollment automation; the Worklet purposefully stops at install so the assignment credential is not baked into a shared policy. The deployment survives reboots and package upgrades; the endpoint only drops out of compliance if an admin or upstream image refresh removes the package, at which point the next evaluation re-schedules remediation.