Windows - Software Lifecycle - Install TeamViewer Host

What the TeamViewer Host deployer does

This Automox Worklet™ deploys TeamViewer Host to Windows endpoints using the latest installer from the Automox software cache. The Worklet checks the OS bitness with [System.Environment]::Is64BitOperatingSystem, requests the matching 32-bit or 64-bit installer payload, and runs TeamViewer_Host.exe silently with the /S switch so end users never see a setup window.

TeamViewer Host is the unattended variant of TeamViewer designed to live on a managed endpoint full-time. The host service is registered with Windows so help desk operators can reach the endpoint by TeamViewer ID at any time, without an end user accepting a session prompt. Account assignment and policy bindings happen in a follow-on Worklet once the binaries are in place.

Why deploy TeamViewer Host for unattended Windows remote access

Remote support breaks down the moment an endpoint is offline, off the corporate network, or stuck behind an end user who cannot run an installer. Without TeamViewer Host already in place, the help desk has to escalate to a site visit, a shipped loaner, or a long screen-share session over a chat tool. Distributed Windows fleets pay this cost on every unplanned incident: a missing remote-access agent on a single laptop becomes a ticket queue that grows during a security event or an outage.

TeamViewer Host enables unattended remote support, and on most fleets the install lives on a one-off scripted job or a help-desk visit. This Worklet installs the latest signed package on every Windows endpoint in scope, picks the right 32-bit or 64-bit architecture based on the OS, and reports the result through the Automox activity log so a 500-endpoint deployment finishes in one policy run instead of 500 manual installs.

How TeamViewer Host deployment works

1. Evaluation phase: The Worklet checks the uninstall registry hives for any DisplayName matching the regex ^TeamViewer.*Host$. On 64-bit Windows it opens HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall through the Registry64 view and also walks HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall. On 32-bit Windows it walks HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall. If no matching DisplayName is found, the endpoint exits 2 and is queued for remediation.

2. Remediation phase: The Worklet re-runs the registry check and exits 0 if TeamViewer Host is already present. Otherwise it reads [System.Environment]::Is64BitOperatingSystem to select arch=32 or arch=64, downloads TeamViewer_Host.exe from the Automox catalog cache (api.automox.com/api/cache, with cmd=downloadLatestVersion, name=TeamViewer_Host, os=Windows, and arch matching the OS) into the working directory using System.Net.WebClient, and runs the installer with Start-Process and the /S silent switch. The Worklet exits 0 on a successful install or 2 if the download or installer call throws.

TeamViewer Host deployment requirements

• Windows 10, Windows 11, Windows Server 2016, 2019, or 2022 with PowerShell 5.1 or later

• Automox agent running with SYSTEM privileges (the default), which has rights to write under Program Files, register Windows services, and write to HKLM

• Outbound HTTPS to api.automox.com on TCP 443 to pull the installer payload, plus *.teamviewer.com on TCP 5938 (with 443 as fallback) for the TeamViewer Host service to register and stay reachable

• Free disk space of at least 100 MB on the system volume for the installer payload plus the installed footprint under Program Files

• A TeamViewer commercial subscription (Business, Premium, or Tensor) if endpoints will run under a managed company account; the personal free tier is not appropriate for business deployments

• Optional: an assignment token from the TeamViewer Management Console, used by a follow-on Worklet so each newly deployed Host registers to your TeamViewer account automatically

Expected TeamViewer Host state after deployment

After the Worklet exits 0, TeamViewer Host is registered in the Windows uninstall hive with a DisplayName matching ^TeamViewer.*Host$, and the TeamViewer host service is installed for unattended access. Subsequent Automox policy runs hit the registry check first, find the matching DisplayName, and exit 0 without re-downloading or re-running the installer.

Validate the deployment on a pilot endpoint by running Get-Service TeamViewer in PowerShell and confirming Status is Running. Check that a TeamViewer Host entry shows up in Settings > Apps > Installed apps or under HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall. From the TeamViewer Management Console, confirm the new TeamViewer ID checks in within a few minutes of installation. Exit code 0 in the Automox activity log means the installer ran cleanly; exit code 2 typically points to a download failure, blocked egress to api.automox.com, or an installer that aborted before completing.