Windows - Software - Install TeamViewer (64-Bit)

What the TeamViewer Windows deployer does

This Automox Worklet™ deploys the full TeamViewer remote support client to Windows workstation and server endpoints. The Worklet pulls the latest 64-bit TeamViewer.exe installer from the Automox cache. It then runs the installer with the /S and /allusers flags, so the client installs silently and is available to every user account on the endpoint. The target install path is the standard C:\Program Files\TeamViewer\ directory used by the full client, not the lightweight Host build.

Before the installer runs, the Worklet inspects two registry hives to detect any existing TeamViewer installation. It walks HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for 64-bit entries and HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall for 32-bit entries. Both sweeps match the DisplayName property against TeamViewer. Any match short-circuits remediation. The Worklet never re-runs an installer on top of an existing client, and it never replaces a 32-bit TeamViewer build with a 64-bit one.

Remediation downloads TeamViewer.exe from the Automox API cache, writes it to the Worklet's working directory, and invokes Start-Process with -Wait. The Worklet exits 0 on a clean install or on a detected existing install. It exits 1 if the download or installer call throws. Both paths log a one-line result to Automox activity output, so the run is auditable in policy history.

Why deploy TeamViewer fleet-wide instead of per-laptop

Helpdesk teams that rely on TeamViewer for remote sessions cannot afford a gap between a ticket opening and the client being installed. Manual rollouts produce mixed-version fleets, mixed 32-bit and 64-bit installs, and a slow tail of endpoints that never get the client. Those tail endpoints are usually the laptops that were offline the day the deployment script ran. The first time a technician needs to reach one of them, the session waits while the installer is emailed and walked through by phone. That delay defeats the point of having TeamViewer in the first place.

Support teams need every Windows endpoint to land on the same TeamViewer build, deployed the same way, on the same cadence. This Worklet pulls the TeamViewer.exe installer from the Automox cache, installs the full remote-support client with consistent silent parameters, and re-validates the install on each evaluation pass. Schedule the policy on a recurring cadence and a newly enrolled laptop is support-ready before the first ticket is filed against it.

How the TeamViewer deployment works

1. Evaluation phase: The Worklet checks [System.Environment]::Is64BitOperatingSystem to choose its detection path. On 64-bit Windows it opens the Registry64 view of HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, enumerates every subkey, and matches each DisplayName against "TeamViewer". It then sweeps HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall for any 32-bit TeamViewer install left over from a prior deployment. On 32-bit Windows it inspects HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall directly. Any DisplayName hit exits 0 with "TeamViewer is already installed"; an empty sweep exits 1 and queues the endpoint for remediation.

2. Remediation phase: The Worklet re-runs the same registry check, then downloads TeamViewer.exe from https://api.automox.com/api/cache?cmd=downloadLatestVersion&name=TeamViewer&os=Windows&arch=64 using System.Net.WebClient. The installer is written next to the Worklet script and launched with Start-Process -ArgumentList ("/S", "/allusers") -Wait. /S triggers the silent NSIS installer flow, and /allusers writes registry entries under HKLM rather than HKCU so every account on the endpoint sees TeamViewer in the Start menu. A successful install logs "TeamViewer 64-bit installed." and exits 0; any exception in the download or install block logs "Failed to install TeamViewer 64-bit." and exits 1.

TeamViewer deployment requirements

• Windows workstation or server endpoint; 64-bit Windows is the supported target, with 32-bit Windows handled by the fall-through branch of the script

• Network reachability from the endpoint to api.automox.com over HTTPS so the cache download succeeds

• Administrative privileges for the Automox agent context, which are required to write to C:\Program Files\TeamViewer\ and to create HKLM uninstall entries

• A valid TeamViewer license for any commercial use; the installer itself does not gate on license state, so license assignment is handled out of band

• No policy variables to edit; the Worklet ships ready to run with the installer name, cache URL, and silent flags hard-coded against the supported full-client build

Expected endpoint state after the TeamViewer deployment

After a successful run, TeamViewer is installed under C:\Program Files\TeamViewer\ and registered in HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall with a DisplayName containing "TeamViewer". The TeamViewer service is registered with the Service Control Manager and starts automatically; the Start menu shortcut is available to every user account because the installer was invoked with /allusers. The application appears in Settings, Apps, and Installed apps, and an end user can launch the client and initiate or accept a remote session immediately.

To validate from PowerShell, use the following command: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object { $_.DisplayName -match 'TeamViewer' } | Select-Object DisplayName, DisplayVersion, InstallLocation. The InstallLocation should resolve to the TeamViewer Program Files directory, and DisplayVersion should match the build that the Automox cache last published. Check the service state with Get-Service TeamViewer; a healthy install reports Status Running and StartType Automatic. Subsequent Worklet runs against the same endpoint return the "already installed" exit-0 branch from evaluation and remediation, so the policy is safe to leave on a recurring schedule for fleet-wide drift coverage.