What platforms does DeviceView support?

DeviceView supports Android, iOS, macOS, Windows, and Linux from a single platform. All platforms are included at no extra cost, including full unattended remote control for Android Enterprise corporate-owned devices.

How does DeviceView compare to TeamViewer?

DeviceView includes mobile support, SSO (SAML 2.0 and OIDC), and SCIM provisioning as standard features. TeamViewer charges extra for mobile device support, locks SSO behind its most expensive Tensor tier, and does not support Android Enterprise corporate-owned devices even through Intune integration.

Does DeviceView include SSO and enterprise identity?

Yes. SAML 2.0, OIDC, and SCIM provisioning are included in every DeviceView plan. There is no separate enterprise tier required for SSO or directory sync.

Is DeviceView HIPAA-ready?

DeviceView is designed for HIPAA-regulated environments. Privacy Mode blacks out patient-facing screens during remote sessions, preventing PHI exposure. Optional session recording with full audit logs including operator, device, and timestamp is available and exportable for compliance audits.

Does DeviceView support unattended Android remote control?

Yes. DeviceView provides full unattended remote control for Android devices, including Android Enterprise corporate-owned (COPE and fully managed) devices. No end-user interaction is required to start a session.

What MDM and EMM integrations does DeviceView offer?

DeviceView integrates natively with Microsoft Intune, VMware Workspace ONE, SOTI MobiControl, Jamf Pro, and Samsung Knox. Remote view and control launch directly from your existing MDM console.

How does DeviceView handle session security?

DeviceView uses WebRTC peer-to-peer connections so sessions never route through DeviceView servers. Multi-tenant data is separated with cryptographic isolation. Every session is recorded with exportable audit logs.

Is DeviceView built for MSPs?

Yes. DeviceView supports multi-tenant environments with cryptographic isolation between tenants, making it suitable for managed service providers supporting multiple client organizations from a single platform.

Platform compatibility · Linux

Unattended Remote Control on Ubuntu 26.04 Wayland

Compatibility, deployment, and what changed in the first Wayland-only Ubuntu LTS for default GNOME.

Does DeviceView support Ubuntu 26.04 LTS for unattended remote control?

DeviceView's unattended remote control is purpose-built for the GNOME Wayland desktop on Ubuntu 26.04 LTS ("Resolute Raccoon"), which ships GNOME 50 with no X11 backend in Mutter. The four supported scenarios on the default desktop are post-login, locked screen, GDM login screen, and after reboot before any user logs in. Legacy tools that relied on WaylandEnable=false or a fallback X11 session do not work on Ubuntu 26.04 default, because that escape hatch no longer exists.

Last reviewed: 3 May 2026 · DeviceView editorial

Validate Wayland support for your fleet Get the Wayland evaluation checklist

Ubuntu 26.04 LTS ("Resolute Raccoon") shipped April 23, 2026 with GNOME 50 as the default desktop and Wayland as the only supported display protocol for that desktop. The X11 fallback workaround that most legacy remote-support tools relied on, WaylandEnable=false in /etc/gdm3/custom.conf, does not work for the default GNOME desktop on this release. There is no X11 backend in Mutter to fall back to. DeviceView's unattended remote control is purpose-built for the GNOME Wayland desktop on this stack, including connection to the GDM login screen and after a reboot, on the supported configurations listed below.

Compatibility status

What is supported on Ubuntu 26.04

The four-value status legend used across DeviceView platform pages: Supported works without configuration changes. Supported with configuration works with a documented setup step at install. Partially supported means specific scenarios in limitations do not work. Not supported means the listed scenario does not function.

Configuration	Value
Default desktop	GNOME 50
Display server	Wayland (only)
Default greeter	GDM
Default init system	systemd
Default firewall	UFW (Uncomplicated Firewall)
Default mandatory access control	AppArmor

Scenario	Status
Post-login session (user logged in, attended)	Supported
Locked screen (operator session continues across screen lock)	Supported
Login screen / GDM (no user logged in, unattended)	Supported
After reboot, before any user logs in	Supported

What changed in Ubuntu 26.04

Three architectural shifts that break legacy tools

01
GNOME 50 ships without an X11 backend in Mutter.
The Mutter compositor's X11 backend was removed in November 2025 and the change landed in GNOME 50 (released March 18, 2026). Ubuntu 26.04 ships GNOME 50 as default. The "switch to Ubuntu on Xorg" option that earlier LTS releases offered at the login screen is gone for the default desktop.
02
XWayland is still present, but XWayland is not an X11 session.
XWayland is a compatibility layer that runs X11 applications inside a Wayland session. Legacy remote tools that depend on attaching to an X11 server have nothing to attach to on Ubuntu 26.04 default; XWayland does not expose the framebuffer to the host the way an X server did.
03
The escape hatch (WaylandEnable=false) is gone for the default desktop.
Setting the GDM configuration option no longer produces an X11 session because Mutter has no X11 backend to start. Users who need an X11 session on Ubuntu 26.04 must move to a non-default desktop environment (Xfce, MATE, Cinnamon, LXQt), a much larger change than swapping a remote-support tool.

The practical implication: any remote-support tool whose Wayland posture in 2025 was "use the Xorg session" stops working on Ubuntu 26.04 default desktops. Tools that integrated with xdg-desktop-portal for attended use cases continue to work for attended scenarios but typically not for unattended (no user to dismiss the consent dialog at the greeter, after reboot, or on a headless endpoint). Tools with system-level integration that operates independent of a logged-in user session, including gnome-remote-desktop paired with GDM (GNOME 46+) and DeviceView, continue to work across the unattended scenarios.

For the architectural background, see Why unattended remote desktop is hard on Wayland.

Deployment requirements

DeviceView's Linux agent on Ubuntu 26.04

Requirement	Detail
Package format	.deb for apt-based installation. The agent is not currently distributed as a snap.
Privileges at install	The agent installs system services and integrates with GDM. Install requires sudo or root.
Init system integration	systemd (Ubuntu 26.04 default).
Networking	Outbound-initiated agent connectivity to the DeviceView control plane. NAT traversal and proxy configurations should be validated against your network topology before fleet rollout. The agent does not require an inbound listener on a public-facing port.
GNOME version	GNOME 50 is the validated default for Ubuntu 26.04. Ubuntu Pro environments running custom GNOME backports should be validated separately.
Architectures	x86_64 and arm64. Validate other architectures with the DeviceView Linux team.
MDM integration	Ubuntu 26.04 endpoints managed via Workspace ONE, Intune, Jamf, or other MDM/UEM platforms can have the DeviceView agent deployed through the MDM's package distribution flow. Agent enrollment can use MDM-supplied identity tokens.

Security considerations

Items shaped by Ubuntu 26.04 defaults

Area	Detail
AppArmor (default mandatory access control)	Ubuntu uses AppArmor, not SELinux. The DeviceView agent ships with AppArmor profiles aligned to its system-service surface. Custom AppArmor policies in your environment should be reviewed against the agent's published policy.
UFW (default firewall)	UFW is disabled by default on a fresh Ubuntu Server install and disabled on most Desktop installs. If your fleet enables UFW, the agent's outbound connectivity requirements must be allowed.
GDM authentication and unattended consent	The unattended authorization decision is made at agent enrollment, by IT, on a known device. End-user consent dialogs from xdg-desktop-portal are not part of the unattended path. Privileged actions inside the session (privilege elevation via sudo, pkexec, or unlocking GNOME Keyring) still go through PAM and polkit. Wayland's compositor-level isolation (per-app input scoping, mediated screen capture) is preserved.
Snap confinement	DeviceView is not distributed as a snap on Ubuntu 26.04. Tools that ship as confined snaps and expect to capture screen content will hit xdg-desktop-portal boundaries; this is not a DeviceView constraint, but worth knowing if you are evaluating snap-distributed remote-support tools alongside.
Audit and session evidence	Per-session connection events, operator identity, and where enabled, in-session activity and session recording, are written to the audit trail and exportable in formats compatible with common SIEM and ITSM ingestion.

For the cross-cluster security and consent model, see audit, RBAC, and consent controls for unattended Wayland access.

Common troubleshooting scenarios

Four failure modes that are specifically Ubuntu-26.04-shaped

01
Black screen at the GDM greeter on remote connect.
Almost always a tool that ships only the X11 path. Verify the tool has a current Wayland implementation; if not, the only fix on Ubuntu 26.04 default is a different tool.
02
"It worked on 24.04, not on 26.04."
The X11 session that handled unattended on 24.04 does not exist on 26.04 default. Either the tool needs a Wayland implementation, or the fleet needs to migrate to a tool that has one.
03
Session drops at screen lock.
Tools depending on per-session xdg-desktop-portal grants typically lose the grant when the screen locks. System-level integrations that operate outside the user session generally do not. Confirm the lock-screen behavior of any tool against your operations runbooks.
04
Reboot and "the agent stops responding."
Tools that store unattended state inside a user session lose that state at reboot. A reboot-resilient agent operates independent of any user session and re-establishes operability when the OS is back up, before any user logs in.

For a vendor-neutral evaluation framework that catches each of these failure modes, see the Wayland Remote Access Evaluation Checklist.

FAQ

Ubuntu 26.04 questions

Does DeviceView support Ubuntu 26.04 LTS?

DeviceView's unattended remote control is purpose-built for the GNOME Wayland desktop, which is the default on Ubuntu 26.04. The supported scenarios (post-login, locked screen, GDM login screen, after reboot) are listed in the compatibility table on this page.

Can I still set WaylandEnable=false on Ubuntu 26.04 to use X11?

Not for the default GNOME desktop. GNOME 50 (which Ubuntu 26.04 ships) removed the X11 backend from Mutter, so there is no X11 session for GDM to start. The configuration option still exists but no longer produces an X11 session for default-GNOME users. To use X11 on Ubuntu 26.04 you must install and switch to a non-default desktop environment that still ships an X11 session (Xfce, MATE, Cinnamon, LXQt, others), a much larger change than swapping a remote-support tool.

What happens to existing X11-dependent remote-support tools on Ubuntu 26.04?

They typically fail. Tools that captured screen content via the X server, injected input via X protocol primitives, or accessed the login screen via XDMCP have nothing to attach to on the default Wayland-only desktop. The path forward is a tool that has shipped Wayland-native unattended capability, or moving the fleet to a non-default desktop environment that still ships an X11 session.

Does DeviceView require GNOME, or does it work on Ubuntu MATE / Ubuntu Studio / Kubuntu / Xubuntu variants?

DeviceView's current unattended Wayland capability is purpose-built for the GNOME Wayland desktop, which is the default on Ubuntu 26.04 (the standard "Ubuntu" desktop variant). Kubuntu (KDE Plasma), Ubuntu MATE, Xubuntu (Xfce), and other variants are not in the same support tier today. KDE-specific roadmap details are available under NDA. For variants shipping X11 desktop sessions (MATE, Xfce on current versions), legacy X11-era remote tools may continue to work, but the broader Wayland transition is one-directional.

What is the GNOME version on Ubuntu 26.04?

GNOME 50, released upstream March 18, 2026. This is the GNOME release that removed the X11 backend from Mutter.

Does the DeviceView agent install via apt, snap, or both?

apt (.deb package). The agent is not currently distributed as a snap. The install requires sudo or root because the agent registers system services and integrates with GDM.

How does DeviceView authorize unattended access at the GDM login screen on Ubuntu 26.04?

The authorization decision is made at agent enrollment, by IT, on a known device, not at session time by an absent end user. The Wayland compositor-level isolation properties (per-app input scoping, mediated screen capture) are preserved; what changes is that the unattended consent layer is IT-managed rather than user-prompted. Operator authentication (SSO + MFA), authorization (RBAC), session logging, and (where enabled) session recording all apply.

How does Ubuntu 26.04 affect existing 24.04 deployments using DeviceView?

DeviceView's Linux agent is validated on both Ubuntu 24.04 (GNOME 46 default, Wayland with X11 session still available) and Ubuntu 26.04 (GNOME 50, Wayland-only for default desktop). The agent install path is the same. Tenants migrating fleets from 24.04 to 26.04 should plan to confirm agent versions across the fleet and validate that any custom AppArmor or UFW policies applied during 24.04 deployment carry forward correctly.

Does the DeviceView agent on Ubuntu 26.04 require a specific kernel version?

DeviceView is validated against the kernel shipping in current Ubuntu 26.04 (Linux 7.0 family at release). Out-of-band kernels (HWE backports, Ubuntu Pro custom kernels, third-party real-time kernels) should be confirmed with the DeviceView Linux team.