Skip to content

Remote control (Take Control) ​

Since v3.19.0 Windows computers can be remote-controlled directly in the browser – without RustDesk, RDP tunnels or extra software on the technician's side. Screen, mouse and keyboard run through the DATAZONE agent that is already installed on the computer.

Requirements ​

  • Windows host with agent 3.19.0 or newer (older agent: message "at least 3.19.0 required" → update the agent)
  • Host is online
  • Permission Remote control (windows.takecontrol). Administrators, operators and support have it by default, the Viewer role does not.
  • Two-factor sign-in is set up (if required for the account)

Server Core without a graphical shell is not supported.

Starting a session ​

  • In the Windows list, click the monitor icon in the Remote column, or
  • Right-click the host → Remote control in browser

A separate window opens. After a few seconds the computer's screen appears.

Controls ​

ElementFunction
Display 1 / 2 / … / AllWith several screens: one button per display (since v3.69.5, before a drop-down), resolution in the tooltip. The active display is highlighted
Window icon next to the display numberOpen this display in its own browser window (since v3.39.0, as a button since v3.69.5)
Resolution100 / 75 / 50 % – a lower resolution saves bandwidth (since v3.21.0)
Image qualityLow / Medium / High – choose "Low" on slow connections
Ctrl+Alt+DelSends the key combination to the computer (e.g. to sign in or lock)
KeysAlt+Tab, Alt+F4, Win+R, Win+E, Win+D, Ctrl+Shift+Esc, Ctrl+Esc, Print Screen – combinations the browser would otherwise catch (since v3.21.0)
Text iconSend text: the text is typed character by character, e.g. long passwords in the sign-in field (since v3.21.0)
Fill windowScale the picture up or down to the full window size, keeping the aspect ratio (since v3.69.5, on by default, remembered in the browser). Off = only shrink – a small customer screen then has a black border on a large monitor (e.g. 4K)
Arrows iconSwitch between "fit to window" and actual size
Full screenRemote control in full screen
DisconnectEnds the session

Keyboard and mouse work once you have clicked into the image. Shortcuts the browser handles itself (e.g. Ctrl+W) do not reach the computer – use the Keys menu instead.

Several displays in separate windows (since v3.39.0) ​

Like TeamViewer, every display of the remote computer can be shown in its own browser window, e.g. display 1 on your main screen and display 2 on your second one:

  1. Start remote control as usual.
  2. In the toolbar click the window icon next to the number of the display. Drag the new window to your second screen and use Full screen.

The second window is a companion session of the first one. It uses the same Windows session, the user is not asked again and gets no second notice bar. Input in either window keeps both open (shared 30-minute limit). When the first window ends, also via Disconnect in the user's notice bar, the companion windows close too. The audit log lists every window as its own session referencing the first one. No agent update is needed.

Chat with the user (since v3.70.0) ​

Chat in the toolbar opens a chat with the user at the computer on the right side of the viewer, as in QuickSupport.

  • Windows: a chat window opens for the user ("Chat – company Fernwartung"). They answer there with Enter or Senden. The window runs as the signed-in user, not as SYSTEM, and flashes in the task bar when a message arrives while it is in the background.
  • Linux: each message opens a small reply dialog (zenity or kdialog). Without them there is only a desktop notification without a reply.
  • macOS: a chat window opens for the user ("Chat – company Fernwartung") in front of other windows without taking the keyboard focus. They answer there with Enter or Senden. If they close it, the next message opens it again. Needs the helper "DATAZONE Fernwartung" 3.70.0 or later (installed automatically with the agent update).
  • When: only once the session is connected and the user agreed. With nobody signed in (sign-in screen) the viewer shows "Kein Benutzer angemeldet".
  • Companion windows for further displays show the same chat.
  • After disconnecting the user's window says that remote support has ended and no longer sends answers. The viewer keeps the history readable.
  • Text only, max. 2000 characters per message, 500 messages per session. Control keeps the chat for 90 days.
  • Needs agent 3.70.0; the viewer names older agents with their version.

iPhone and iPad (since v3.71.0) ​

On an iPhone or iPad you control the computer with your finger, both in agent remote control and in QuickSupport. No agent update needed.

GestureAction
TapLeft click, double tap = double click
Long pressRight click
Long press and dragDrag / select text
Two-finger tapRight click
Two fingers up/downScroll (zoomed in: move the view)
PinchZoom the picture in/out, only on your side
Three-finger tapOn-screen keyboard on/off
  • Input mode: Switch at the top between Direct (click where the finger is) and Trackpad (one finger moves the pointer like a laptop touchpad, tap clicks at the pointer). iPhone starts in Trackpad because Windows buttons are too small for a finger, iPad in Direct. The browser remembers your choice. In Trackpad mode the view follows the pointer when zoomed in.
  • Keyboard: The keyboard button opens the on-screen keyboard. Text is sent as characters, including umlauts, @ and €. Above it is a bar with Ctrl, Alt, Win (⌘ on Mac), Shift, Esc, Tab, arrow keys, Del, Home/End, PgUp/PgDn, F1–F12 and (Windows) Ctrl+Alt+Del. Tap Ctrl/Alt/Win/Shift once = applies to the next key, again = lock, again = off. Example Ctrl+C: Ctrl, then c.
  • Reset zoom: When zoomed in, a magnifier button appears at the top.
  • Narrow screen: On iPhone and iPad in portrait, monitors, scaling, quality, keys, clipboard and full screen are behind ⋯. The chat lies over the picture.
  • On the first connection a short hint explains the gestures; the question mark in the menu shows it again.
  • Nothing changes on a PC with mouse and keyboard.

Clipboard (since v3.21.0) ​

Clipboard text is synchronised automatically: what you copied locally is available on the computer after switching back to the remote window; what is copied on the computer ends up in your local clipboard. Browsers only allow this over HTTPS (https://control.datazone.de) and ask for permission the first time. Without HTTPS use Send text and the Clipboard from the computer button (shows the text last copied on the computer with "Copy", since v3.22.4).

Drag files onto the screen (since v3.21.0) ​

Drag files from your explorer onto the remote image: they are placed on the desktop of the signed-in user (permission Manage files).

Choose session (since v3.21.0) ​

If users are signed in on a server via Remote Desktop, remote control asks which session to show before connecting: the console (sign-in screen or the user signed in there) or a Remote Desktop session (active or disconnected). A disconnected session is moved to the console when connecting (like tscon <id> /dest:console), because Windows does not render disconnected sessions. When the user signs in via Remote Desktop again, they get their session back as usual (since v3.22.3).

Sign-in and UAC screen ​

Remote control also works on the Windows sign-in screen, the lock screen and User Account Control (UAC) prompts. The header then shows "Sign-in or UAC screen". If nobody is signed in, remote control connects straight to the sign-in screen.

Notice for the user (since v3.21.0) ​

What the user at the computer sees is configurable:

ValueBehaviour
Notice bar (default)First a bar at the top for 5 seconds "<technician> from <company> is connected" with a Disconnect button, then only a small semi-transparent tab "<company> connected"; hovering expands it again (since v3.22.4). The company name comes from the instance's branding
Ask the userBefore connecting a Yes/No prompt appears (60 seconds). No or no answer = no connection. Afterwards the notice bar
No noticeNothing

If nobody is signed in (sign-in screen) there is never a prompt and no bar.

Where to set it:

  • On the computer (since v3.51.0): host panel → menu "…" → "Remote control: notice to the user". A value here applies to this computer only and takes precedence over groups and customer, even if those are stricter. "Inherit" shows what would apply without it. Only administrators may change it; every change is written to the audit log.
  • Edit a Windows group → "Remote control: notice for the user" (e.g. workstations: ask, servers: no notice)
  • Edit a customer → same field
  • Default: Settings → Parameters → takecontrol_consent (none, banner, prompt)

If nothing is set on the computer, the strictest setting of the customer and all groups of the computer applies (since v3.48.16 – before, a group replaced the customer setting). The default from the settings only applies if neither computer, customer nor group sets one. Only administrators may change the customer and the group setting (groups since v3.65.11, even for users who may otherwise manage groups). Removing computers from a group with its own setting, or deleting that group, is also limited to administrators. A second window for another display opens only after the user has consented. The audit log entry takecontrol_start records which mode applied and where it came from.

Security and audit ​

  • Every session needs a one-time ticket valid for 60 seconds. Control issues it only after sign-in, two-factor check, permission check and customer check.
  • MCP tokens cannot start remote control.
  • Image data runs through a dedicated relay service (takecontrol-relay), not through the agents' realtime service.
  • No video is recorded. The audit log contains start (takecontrol_start) and end (takecontrol_end) with user, host, duration and reason.
  • After 30 minutes without mouse or keyboard input the session is disconnected (since v3.31.5, before 15), after 8 hours at the latest. Just watching does not count as input.

Linux desktops (since v3.28.0) ​

Linux computers with a graphical desktop can be remote-controlled as well – right-click the host in the Linux list → Remote control in browser.

  • Requirements: agent 3.28.0 or newer (X11) or 3.50.0 or newer (Wayland), a user is logged in to a graphical session on the computer, permission Remote control (linux.takecontrol; administrators, operators and support by default).
  • Wayland (since v3.50.0, e.g. KDE Plasma or GNOME with default settings): picture and input go through the desktop's screen sharing (xdg-desktop-portal). The first time, the desktop shows a dialog "DATAZONE Fernwartung wants to share the screen / control the computer". The user picks the screen and confirms, ideally with Remember / Remember permission. After that the desktop does not ask again until the permission is revoked in the system settings. Meanwhile the viewer shows "Waiting for consent". If the user declines, the session ends with "Declined by the user".
  • Wayland needs on the computer: xdg-desktop-portal with the desktop's backend (xdg-desktop-portal-kde or -gnome) and GStreamer with the PipeWire module: gst-plugin-pipewire (Arch/CachyOS), gstreamer1.0-pipewire (Debian/Ubuntu), pipewire-gstreamer (Fedora/openSUSE). If it is missing, Control names the package.
  • Which session: if a user is logged in directly at the computer, that session is controlled. If nobody is logged in directly, the agent (since v3.51.1) takes the newest remote session (e.g. RDP or GNOME remote login on VMs).
  • Unsupported desktops: Wayland window managers without a remote control interface (niri, Sway, Hyprland and others) – Control reports "The desktop … does not offer remote control via the portal". KDE Plasma and GNOME are supported.
  • Wayland limits: exactly one monitor (the one chosen in the dialog). During the session the desktop shows its "screen is being shared" indicator. Without a confirmation at the computer there is no picture the first time, so have unattended computers approved once beforehand.
  • How it works: the agent (root) starts itself as helper on behalf of the logged-in user in that user's session. Only this program and only this user may connect to the agent (checked via the socket credentials).
  • Notice for the user: Notice shows a desktop notification (notify-send). Ask opens a yes/no dialog (zenity or kdialog). If neither is installed, Ask does not connect.
  • Drag files onto the screen (since v3.70.0): the file lands on the signed-in user's desktop (XDG_DESKTOP_DIR, else ~/Desktop) and belongs to them. The agent does not write it as root but through a helper process with the user's rights. An existing file with the same name is not replaced. Permission manage files.
  • Not on Linux: Ctrl+Alt+Del, session choice, sign-in screen (no picture without a signed-in user) and clipboard. Several displays appear as one picture, so there is no window per display.
  • Log on the computer: ~/.cache/datazone-kvm-helper.log of the logged-in user, lines with Linux Take Control in the agent log.

Troubleshooting ​

MessageCause / solution
"at least 3.19.0 required"Update the agent on the host
"Agent is offline"Host is not connected
"not set up (TAKECONTROL_SECRET missing)"The entry in .env is missing on the Control server; update.sh creates it
"The computer did not connect in time"Agent cannot reach …/takecontrol/ (proxy/firewall at the customer)
Antivirus flags the agentUntil the agent is code-signed, add an exclusion for C:\Program Files\DATAZONE\Agent\ if needed

Origin ​

The image protocol and parts of the Windows logic are derived from MeshCentral / MeshAgent (Apache License 2.0), see third_party/meshcentral/NOTICE.

DATAZONE Control Documentation