TeamViewer is a comprehensive digital workplace platform used by more than 660,000 customers globally for remote access, IT support, endpoint management, and augmented reality-powered workflows. Founded in 2005 and headquartered in GΓΆppingen, Germany, it operates on a freemium model β free for personal use, paid licenses for commercial use β and achieved EUR 768 million in revenue in 2025. TeamViewer's zero-configuration approach connects through firewalls without manual port forwarding via relay servers and peer-to-peer routing. In 2025, TeamViewer launched TeamViewer ONE, a unified platform combining remote connectivity, Digital Employee Experience (DEX), RMM, and AI-powered tools. Understanding its session types (attended vs. unattended), security layers (end-to-end encryption, two-factor authentication, conditional access), and enterprise capabilities (mass deployment, multitenancy, agentless OT access) transforms TeamViewer from a screen-sharing tool into a strategic IT operations platform.
What This Cheat Sheet Covers
This topic spans 12 focused tables and 129 indexed concepts, 117 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Connection Types and Access Modes
How a session is established determines what permissions are needed and how much configuration is required upfront. The key axis is attended vs. unattended: attended sessions use one-time passwords and require someone present, while unattended access ties a device to an account for anytime connectivity.
| Type | Example | Description | |
|---|---|---|---|
Partner enters ID 123 456 789 + password β Support session starts | β’ One-time remote support where both parties are present β’ temporary password generated per session β’ ideal for troubleshooting end-user issues without pre-configuration | ||
Device assigned to account β Access anytime with account login β No password prompt | β’ Remote access without user intervention β’ requires device assignment to TeamViewer account β’ enables 24/7 access for server maintenance or personal computers | ||
End user downloads TeamViewerQS.exe β Runs without installation β Generates temporary ID | β’ Lightweight executable for spontaneous support sessions β’ no installation or admin rights required β’ automatically deleted after session β’ perfect for customer support where installing software isn't feasible | ||
Install TeamViewer_Setup.exe β Configure as service β Enables incoming/outgoing connections | β’ Complete installation providing both controller and host capabilities β’ runs as Windows service for unattended access β’ supports all features including file transfer, VPN, and terminal | ||
Deploy TeamViewerHost.msi via GPO β Device auto-assigned β Accepts only incoming connections | β’ Dedicated receive-only client for managed devices β’ minimal UI β’ ideal for servers or kiosks β’ reduces attack surface by disabling outbound connection features | ||
Set password on device β Connect by ID without password prompt β Account-based trust | β’ Simplified authentication for frequently accessed devices β’ eliminates repetitive password entry β’ device must be in account's computer list | ||
Both devices on 192.168.1.0/24 β Direct peer-to-peer β No relay server | β’ Optimized local network connection β’ bypasses internet routing for lower latency β’ auto-detected when devices share subnet β’ improves performance for high-bandwidth tasks | ||
Configure WOL in BIOS + TeamViewer settings β Send magic packet β Device powers on remotely | β’ Remotely power on sleeping/shutdown devices β’ requires BIOS support and network configuration β’ TeamViewer delivers WOL packet through relay β’ essential for energy-saving IT infrastructure | ||
Generate link in app β Send via email β Recipient clicks β Browser-based connection (no install) | β’ Web-based connection method β’ user downloads QuickSupport via secure link β’ link expires after use or timeout β’ shows provider name + location to prevent scam abuse | ||
Tensor configured β Connect to PLC/HMI β Control OT device β No software installed on device | β’ Tensor feature for operational technology (OT) environments β’ connect to PLCs, HMIs, and legacy industrial systems without installing an agent β’ enforces zero-trust with granular access controls and full audit logging β’ bridges IT/OT security governance gap |