# TeamViewer Remote Support

> Enable TeamViewer Remote Support for Windows Devices in Applivery — silent install, session types, licensing, and troubleshooting.

Source: https://docs.applivery.com/en/device-management/windows/remote-support/teamviewer-remote-support/  •  Last updated: 2026-08-19

**Key topics:** Enabling TeamViewer Remote in a Policy, Silent installation of TeamViewer Host, Session types and licensing, Troubleshooting remote sessions, Applivery, TeamViewer, Windows, Windows Agent

---

**TL;DR:** Enable TeamViewer Remote in a Policy, let Applivery install TeamViewer Host silently, then start sessions from the Device's Action menu.

:::warning
This is a premium feature that may not be available on your current plan. Check availability on the [Applivery pricing page](https://www.applivery.com/device-management-pricing/).
:::

Enabling **TeamViewer Remote** in a Windows Policy makes Applivery silently install the TeamViewer Host app on every Device that Policy applies to, and register those Devices with TeamViewer. From then on, you start a remote session from the Device's **Action** menu — no setup on the Device itself, and nothing for the person using it to install or accept beforehand.

## Before you start

TeamViewer Remote depends on the [Windows Agent](https://docs.applivery.com/en/device-management/windows/policies/agent/): the Agent is what installs and registers TeamViewer Host on the Device. Before enabling the Policy, make sure the Device's Segment has the **Windows Agent & Self Service** enabled, **with Scripts enabled** — the TeamViewer Host installation is delivered as a Script that the Agent runs.

If either one is missing, the feature won't work even if the Policy itself says **Enabled**. The Policy's own warning links straight to the Agent settings for that Segment, so you can check it without leaving the page.

## Enabling TeamViewer Remote

**Open the Policy**

Once in the [**Applivery Dashboard**](https://dashboard.applivery.io/), go to **Policies** 1 and open the Policy you want to enable Remote Support on.

**Go to the Remote section**

In the left-hand menu, select the **TeamViewer Remote** section and find the **TeamViewer Remote** configuration 2.

**Set it to Enabled**

Choose **Enabled** and save your changes. Every Device that Policy applies to will now get TeamViewer Host installed automatically.

![enable teamviewer](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/98604492-1eba-4788-abb7-62daec53ab16.png)

### The three configuration states

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>State</p></th><th colspan="1" rowspan="1"><p>What it does</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Enabled</strong></p></td><td colspan="1" rowspan="1"><p>Assigns a license from your pool to every Device in the Policy and installs TeamViewer Host on them</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Disabled</strong></p></td><td colspan="1" rowspan="1"><p>Deregisters every Device in the Policy from TeamViewer and releases their licenses</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Not configured</strong></p></td><td colspan="1" rowspan="1"><p>Changes nothing — each Device stays in whatever state it was already in</p></td></tr></tbody></table>

**Not configured** is the one to use when a Policy shouldn't have an opinion on Remote Support: it won't turn it on, and it won't turn it off on Devices that already have it.

### Automatic installation

Applivery deploys TeamViewer Host silently — the person using the Device doesn't have to do anything, and won't be asked to approve anything. The Device shows up as **Ready** once the app has fetched its configuration, which usually takes a few minutes.

### How licenses are counted

Each Device with this Policy set to **Enabled** uses one TeamViewer license from your plan, **whether or not anyone ever actually connects to it**. What counts is the number of Devices with the Policy enabled, not the number of sessions you open.

To free up a license, set the Policy to **Disabled** or move the Device to another Policy — removing a Device from an enabled Policy releases its license automatically.

## Starting a remote session

**Open the Device**

Navigate to any of your Windows **Devices** and click the **Action** button 1. **TeamViewer Remote** 2 is the first option in the menu.

![action button](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/a24909c2-e4a6-402a-9dd8-9272ff9b32fe.png)

**Pick how you want to connect**

The **TeamViewer Remote Support** modal opens. Choose the **Control Type** and the **Open With** option for this session 3.

![controls](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/82cf4d74-3a88-4f31-858b-02887ff88071.png)

**Start the session**

Click **Start remote session**. If you chose **TeamViewer client**, the session is handed off to the TeamViewer desktop app on your machine, which connects to the Device.

![connecting](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/d4eed369-134b-4f38-9c7c-4acca27d3eb4.png)

You don't fix a session type when enabling the Policy — every option is available every time, and you pick per session:

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Setting</p></th><th colspan="1" rowspan="1"><p>Options</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Control Type</strong></p></td><td colspan="1" rowspan="1"><p><strong>Unattended</strong> — connects without anyone accepting on the Device, for machines with nobody in front of them. <strong>Attended</strong> — someone at the Device has to accept the incoming session. <strong>View only</strong> — someone at the Device also has to accept, and you see the screen without any keyboard or mouse input being sent</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Open With</strong></p></td><td colspan="1" rowspan="1"><p><strong>New browser tab</strong> — runs on TeamViewer's web client, nothing to install on your machine. <strong>TeamViewer client</strong> — hands the session to the TeamViewer desktop app, with its full set of features</p></td></tr></tbody></table>

You can change your selection as many times as you like before clicking **Start remote session** — the value showing when you click is the one that gets used.

### What you can do during a session

Once connected, TeamViewer gives you clipboard sharing, black screen, file transfer, chat, audio call, augmented reality, remote reboot, screen recording, and the ability to leave notes for the user.

On the managed Device itself, TeamViewer Host shows up installed alongside the Applivery Agent — both put there by the automatic installation described above.

![teamviewer next to agent](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/c25a6bcc-3d9a-4899-a30d-5f51d1358ed7.png)

## Troubleshooting

The **TeamViewer Remote Support** modal shows a status badge next to the Device, so you can tell at a glance whether a session can start. Hover the ⓘ icon next to the badge for a short explanation.

### Ready

TeamViewer Host is installed and configured on the Device. You can start a session.

### Not enabled in policy

The Device's assigned Policy doesn't have TeamViewer Remote set to **Enabled**. Go back to [Enabling TeamViewer Remote](#enabling-teamviewer-remote) and confirm you're editing the Policy that Device is actually assigned to.

![not enabled in policy](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/42d327ef-ab9f-4377-bf34-f99df4c40ae9.png)

### App not installed

The Policy is enabled, but TeamViewer Host hasn't finished installing on that Device yet — or couldn't. Since the install is silent and can take a few minutes, wait and retry first.

If it persists, check that the Device's Segment actually meets the [Agent and Scripts requirement](#before-you-start). This is by far the most common cause, because the install is delivered through a Script run by the Agent.

![app not installed](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/9961af89-b34b-49cb-a708-e04b0ce736f0.png)

Starting a session against a Device in this state fails, whichever Control Type or Open With option you pick.

### The Device goes offline mid-session

If the Device disconnects right after you click **Start remote session**, the remote session window closes on its own. Wait for the Device to come back online and start a new session.

### Nothing seems to happen when I click Start remote session

Give it a moment before clicking again — double-clicking **Start remote session** won't open two sessions, so a second click doesn't speed anything up.