Windows - Software Lifecycle - Update TeamViewer with Notifications

What the TeamViewer Updater does

This Automox Worklet™ detects outdated TeamViewer installations and updates them to the latest version. The Worklet queries the Automox API cache to determine the current TeamViewer release for the endpoint's architecture (32-bit or 64-bit), then compares it against the installed version.

When an update is needed, the Worklet sends a notification to the logged-in user asking permission to close TeamViewer. If approved, the Worklet terminates both TeamViewer and TeamViewer_Service processes, uninstalls the current version, downloads the latest installer from the Automox cache, and performs a silent installation for all users on the endpoint.

This Worklet only supports EXE-installed versions of TeamViewer. MSI-installed versions use different uninstall and upgrade mechanisms that this Worklet does not handle. Check your installation method before deploying.

Why update TeamViewer through Automox

Outdated remote access software creates security vulnerabilities that attackers actively exploit. TeamViewer is a high-value target because it provides direct remote access to endpoints. When vulnerabilities exist in older TeamViewer versions, adversaries can gain unauthorized remote access to your infrastructure, bypassing other security controls.

The notification-based approach prevents disrupting active remote support sessions. IT staff or end users receiving remote assistance can finish their current session before the update begins. This consideration reduces frustration and support tickets related to interrupted work.

Automating version detection through the Automox API cache removes the need to manually update version numbers in scripts each time TeamViewer releases an update. The Worklet always targets the current stable release without additional configuration.

How TeamViewer updates work

1. Evaluation phase: The Worklet queries https://api.automox.com/api/cache to get the latest TeamViewer version for the endpoint's architecture. It uses Get-Win32App to detect installed TeamViewer and compares versions. If the installed version is older or missing, the endpoint is flagged for remediation. Endpoints without TeamViewer exit as compliant.

2. Remediation phase: The Worklet sends a Yes/No notification to the active user with configurable title, message, and timeout (default 60 seconds). If approved, it stops TeamViewer and TeamViewer_Service processes, removes the existing installation using Remove-Win32App with /S flag, downloads the latest installer to the Worklet cache directory, and runs a silent installation with /S /allusers arguments. A 300-second timeout applies to the installation process.

TeamViewer update requirements

• Windows workstations or servers with TeamViewer installed via EXE (not MSI)

• Internet connectivity to reach api.automox.com for version checks and downloads

• TLS 1.2 enabled for secure connections

• User must be logged in to receive the notification

• Configurable parameters: notification title (default: Automox Notification), message, timeout (default: 60 seconds)

Expected state after TeamViewer update

After successful remediation, TeamViewer runs the latest version with all security patches and feature updates applied. The application installs for all users on the endpoint with TeamViewer services restarting automatically. You can verify the update by checking the version number in TeamViewer's Help > About menu or querying the registry uninstall keys. The application is immediately ready for remote support sessions with the latest security protections active.

If the user declines the notification or the timeout expires, the Worklet exits with code 3 and no changes are made. TeamViewer remains at the current version and can be updated when the user is available. Installation failures log specific exit codes to the Automox activity log for troubleshooting.

How to validate update teamviewer with notifications changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for update teamviewer with notifications.

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 Invoke-WebRequest, Select-Object, ConvertFrom-Json.

4. Validate remediation effects from script operations such as Invoke-WebRequest, Select-Object, ConvertFrom-Json, then rerun evaluation for compliance.