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.

Has ConnectWise actually said ScreenConnect will not support Wayland?

Yes, on the ScreenConnect community forum. ConnectWise engineering has stated that supporting Wayland would require a different architecture than ScreenConnect's current approach, and that the Wayland security model is intentionally incompatible with the global input injection and full-framebuffer capture ScreenConnect relies on. The community thread is linked in the sources at the bottom of this page.

Is this only an issue on Ubuntu 26.04, or on every Linux distribution?

It is broader than Ubuntu 26.04, but Ubuntu 26.04 is where it becomes unavoidable for most enterprise fleets. Fedora has been Wayland-only for default GNOME since Fedora 40. RHEL 10 is Wayland-only for default GNOME. Debian 13 ships Wayland by default. Ubuntu 26.04 is significant because it is the first Ubuntu LTS that removes the X11 fallback for the default desktop, which means existing 24.04 deployments using ScreenConnect on the WaylandEnable=false escape hatch lose that escape on upgrade.

Can we keep ScreenConnect on Windows and macOS and use a different tool just for Linux?

Yes, and many organizations do this. You can run ScreenConnect for Windows and macOS unattended (where its track record is strong) and run DeviceView for Linux unattended where ScreenConnect cannot operate on Wayland. The two tools coexist on a shared endpoint roster. The trade-off is operating two consoles and two audit pipelines instead of one.

What about KDE Plasma on Wayland? Is DeviceView's Linux support GNOME-only?

DeviceView's current unattended Wayland capability is purpose-built for the GNOME Wayland desktop, which is the default on Ubuntu 26.04, Fedora, and RHEL. KDE Plasma on Wayland is a different compositor (KWin) with a different protocol surface and is not in the same support tier as GNOME Wayland today. KDE-specific roadmap details are available under NDA.

Does WaylandEnable=false still work on Ubuntu 26.04?

Not for the default GNOME desktop. GNOME 50 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). That is a much larger change than swapping a remote-support tool, and it is one-directional: every Wayland upstream is moving in the opposite direction.

What does ConnectWise do well that we'd give up by switching for Linux?

ConnectWise has a mature unattended product on Windows and macOS, a long-running PSA and RMM ecosystem with deep ConnectWise Manage and Automate integration, an established MSP partner network, and an extension ecosystem. If your operations are anchored to that ecosystem, the parallel-Linux-only path keeps it intact. The consolidation path trades that ecosystem depth for a single-console operating model that covers Linux unattended.

How do we evaluate vendor claims of Wayland support without taking the marketing page at face value?

Test the four unattended scenarios end-to-end on a Wayland-only target: post-login attended, locked-screen handoff, GDM login screen with no user logged in, and after a reboot before any user logs in. The Wayland Remote Access Evaluation Checklist on this site walks through twenty-six concrete questions and tests, vendor-neutral, that any tool should pass before fleet rollout.

If we consolidate onto DeviceView, what is the migration shape?

Common pattern: enroll DeviceView on a Linux pilot ring (often the Ubuntu 26.04 endpoints that are already broken on ScreenConnect), validate the four unattended scenarios on real fleet hardware, expand to the broader Linux fleet over a quarter, then evaluate Windows and macOS consolidation at ScreenConnect renewal. Treating it as two phases (Linux first because it is forced by the platform, Windows and macOS at renewal because that is when economics permit) keeps the change manageable.

Compare · ScreenConnect on Linux Wayland

ScreenConnect Alternative for Linux Fleets on Wayland

ConnectWise's engineering team publicly stated they will not support Wayland. On Ubuntu 26.04 default, your Linux endpoints are unsupportable on ScreenConnect. Here is what to do about it.

What is the situation with ScreenConnect on Wayland Linux, and what should we do about it?

ConnectWise has publicly stated, in their own community forums, that ScreenConnect will not support Wayland because the underlying Wayland security model is incompatible with ScreenConnect's screen capture and input injection approach. Ubuntu 26.04 LTS ships GNOME 50 with no X11 backend in Mutter, which means the default Ubuntu desktop is Wayland-only. The two practical paths forward are: keep ScreenConnect for Windows and macOS endpoints while running a Wayland-native tool such as DeviceView for Linux, or consolidate onto a single tool that supports all three platforms including unattended Wayland Linux.

Last reviewed: 5 May 2026 · DeviceView editorial

Replace ScreenConnect on Linux Get the Wayland evaluation checklist

Source: ConnectWise community: ScreenConnect on Wayland.

The platform fact

Why ScreenConnect is not viable on Ubuntu 26.04 default

Two facts compose. First, Ubuntu 26.04 LTS shipped April 23, 2026 with GNOME 50 as the default desktop. GNOME 50 removed the X11 backend from Mutter (the GNOME compositor), which means there is no X11 session for the default desktop and no WaylandEnable=false escape hatch. Second, ConnectWise has publicly stated, on the ScreenConnect community forum, that ScreenConnect will not support Wayland, citing the security and stability properties of the Wayland design that are intentionally incompatible with ScreenConnect's screen-capture and input-injection approach.

Composed: Ubuntu 26.04 default Linux endpoints are unsupportable through ScreenConnect's unattended path. This is not a temporary version-gap or a "next quarter" roadmap item. It is the vendor's stated position about a platform shift that has already happened.

What this means in practice

Three concrete failure scenarios

01
New Ubuntu 26.04 endpoint, ScreenConnect installed.
Connect attempt at the GDM login screen returns a black screen or fails to attach. The agent is running, but it has no X11 server to capture from on the default desktop. Operator cannot reach the endpoint until a user logs in. Unattended is effectively gone.
02
Existing 24.04 endpoint upgraded to 26.04.
ScreenConnect was working on 24.04 because the user (or a config script) had set WaylandEnable=false in /etc/gdm3/custom.conf. After upgrade to 26.04, that setting still exists but no longer produces an X11 session because Mutter has no X11 backend. The endpoint silently falls back to Wayland, and unattended access regresses. Common during rolling upgrades.
03
Reboot during a maintenance window.
On Wayland-only 26.04, ScreenConnect's user-session-bound state does not survive a reboot. The endpoint comes back up at GDM, no user logged in, no captureable X server, no remote operability. The runbook step that says "reboot then reconnect to confirm" stops working.

Operational consequences

Tier-1 escalations on Linux take longer because the operator has to ask a user to log in before they can connect, defeating the purpose of unattended.
Lab and kiosk endpoints (no human present at the keyboard) become unsupportable on Wayland-only Linux through ScreenConnect.
Ubuntu 26.04 fleet rollouts get held back because the remote support tool cannot service them, dragging the broader Linux modernization.
Audit and compliance evidence (proof that an out-of-hours patch deployment happened) cannot be produced for Linux endpoints if the operator could never connect in the first place.

Capability matrix

DeviceView vs. ScreenConnect on Wayland Linux

The lines below the architectural divide are the ones ScreenConnect cannot cross given the vendor's stated Wayland position. The lines above are normal capability comparisons.

Swipe to compare →

Capability	DeviceView	ScreenConnect
Wayland on Ubuntu 26.04 default GNOME	Supported, including GDM login screen and after reboot	Not supported. ConnectWise has stated they will not pursue Wayland support
Unattended at the Linux login screen (no user logged in)	Supported on GNOME Wayland via system-level agent + GDM integration	Requires X11. Fails on Wayland-only Ubuntu 26.04 default
Connection persistence across screen lock	Operator session continues; system-level agent independent of user session	Per-session attended grants drop at lock on Wayland
Reboot resilience	Agent re-establishes operability before any user logs in	User-session-bound state is lost at reboot on Wayland
Windows and macOS unattended	Supported with the same console, RBAC, and audit pipeline used for Linux	Strong, mature unattended on Windows and macOS
Public Wayland roadmap commitment	Wayland-native design; Ubuntu 26.04 GNOME 50 validated at GA	Public statement: not pursuing Wayland support
Security model on Linux	Compositor-level isolation preserved; consent relocated to enrollment-time IT authorization	X11-era input injection and full-framebuffer capture, which the Wayland design intentionally removes
SSO, SCIM, RBAC	SAML 2.0 / OIDC, SCIM, three-axis RBAC, no tier-gating	SSO available; SCIM and granular RBAC vary by edition
Audit logs and SIEM integration	Per-session structured events, signed export, common SIEM formats	Session logs available; depth and format vary by deployment
Session recording	Optional usage-based add-on, configurable per device group	Available; configuration depth varies

Migration paths

Three options, ordered by change-management cost

01
Parallel-Linux-only.
Keep ScreenConnect for Windows and macOS unattended. Run DeviceView for Linux unattended on Ubuntu 26.04 and other Wayland-only distributions. Two consoles, two audit pipelines, no contractual disruption to the ScreenConnect side. Lowest-friction option for organizations whose Linux footprint is small relative to Windows and macOS, and whose ConnectWise PSA/RMM integration is operationally critical.
02
Pilot at renewal.
Run a parallel pilot of DeviceView on Linux through the next ScreenConnect renewal cycle. At renewal, evaluate consolidating Windows and macOS onto DeviceView based on pilot evidence (operator NPS, MTTR, audit completeness, IT total cost of operating two consoles vs. one). Decision is informed by data from production rather than vendor demos. Common shape for mid-market and enterprise fleets where renewal cycles are quarterly or annual.
03
Full consolidation.
Consolidate Windows, macOS, and Linux onto DeviceView in a single migration. Higher upfront change-management cost; single console, single RBAC model, single audit pipeline at the end. Common for organizations that are already Linux-heavy, that have a single operations team supporting all three OS families, or that are simultaneously evaluating ConnectWise Manage / Automate alternatives.

Most organizations land on Path 2 (Pilot at renewal). It treats the Linux problem as the urgent forced move (because Ubuntu 26.04 is already breaking it), and treats Windows and macOS consolidation as an opportunity, not an obligation, evaluated when contract economics align.

A balanced view

What ConnectWise does well

ScreenConnect has a mature unattended product on Windows and macOS, with a long history of MSP-friendly licensing, partner ecosystem, and integration with the broader ConnectWise PSA / RMM stack (Manage, Automate). For organizations whose operating model is anchored on those integrations, the loss of Linux Wayland support is a single capability gap rather than a wholesale displacement. The honest framing is: this page is about Linux on Wayland specifically, not a general claim that DeviceView replaces every ScreenConnect use case.

FAQ

ScreenConnect on Wayland Linux questions

Where to go from here

Ubuntu 26.04 Wayland Unattended

Compatibility, deployment, and security details for Ubuntu 26.04 default GNOME.

Unattended Remote Control for Wayland Linux

Cross-distribution compatibility matrix and the security and consent model.

Audit, RBAC, and Consent Controls

How DeviceView relocates the unattended consent decision to IT without weakening Wayland.

Why unattended remote desktop is hard on Wayland

The architectural background for why every X11-era tool faces this same wall.

Wayland Evaluation Checklist

Twenty-six vendor-neutral questions to ask any tool claiming Wayland support.

Sources

Public references for the claims on this page

Claim	Source
ConnectWise will not support Wayland; security and stability risk cited.	ScreenConnect community thread on Wayland support.
GNOME 50 removed the X11 backend from Mutter.	Phoronix: GNOME Mutter 50 Alpha released with X11 backend removed.
Ubuntu 26.04 LTS is Wayland-only for default GNOME.	Ubuntu 26.04 LTS release notes.

This page is reviewed every 90 days against ConnectWise's public position and current GNOME and Ubuntu releases. Next review: August 2026.