TeamViewer Unattended Access Goes Offline When V2 Cloud Session Disconnects

This article explains a known issue affecting unattended access in TeamViewer when used with V2 Cloud.

---

Main Issue

• Unattended access becomes unstable and TeamViewer shows as ONLINE only while an active V2 Cloud (HTML5/RDP) session is open.
• When the V2 Cloud session is disconnected, TeamViewer immediately goes OFFLINE.
• This causes loss of unattended access and may disrupt critical services (e.g., live radio systems going “OFF AIR”).

---

Root Cause

TeamViewer generates two different IDs:

• User ID
  • Linked to the active RDP session
  • Goes offline immediately when the session is closed
• Server ID / Console ID
  • Linked to the physical machine
  • Remains active even when no users are logged in

---

Resolution

1. Open the remote machine.
2. Launch TeamViewer.
3. Go to Help → About TeamViewer.
4. Identify the Server ID / Console ID.
5. Always use the Server ID / Console ID for unattended access connections.

---

Result

• Using the Server/Console ID ensures TeamViewer remains available even when all V2 Cloud sessions are disconnected.
• This restores stable unattended access and prevents unexpected disconnections.