Remote Desktop
View and control a managed device directly from the portal. No third-party tools or VPN required: connections are peer-to-peer and encrypted.
In short
- Start a session with Remote Control on the device page. Read Only and MSP Read Only users can't (see Users & Access).
- Each session opens in its own browser tab. A device has one active session at a time, for at most 2 hours; starting another asks before taking over.
- On a Mac, someone at the device allows Screen Recording and Accessibility for Pckgr once (see Remote desktop on a Mac); a user must be signed in.
- The Pckgr API only sets the session up. Screen content and input never pass through it.
- Remote desktop is on by default and can be switched off per tenant. Every session is recorded in the audit log.
Start a session
Go to Devices and click the device you want to connect to.
Click Remote Control on the device detail page.
The session opens in a new browser tab named after the device, so the device page stays where it was.Choose whether to notify the user.
It is on by default. When enabled, a toast notification appears on the device before the session starts.Click Connect.
The portal waits for the agent to pick up the session, usually a few seconds. Once connected, the device screen appears in your browser.
To work on several devices at once, click Remote Control on each one. Every session gets its own tab, and you switch between them like any other browser tabs.
If the device is already in a session
User notification
When Notify User is enabled, the device shows a notification before the session begins (in Action Center on Windows, Notification Center on a Mac):
Remote Support Session
Turn this off for unattended devices or maintenance windows where no user is present.
Using the viewer
Once connected, you can use your mouse and keyboard on the remote desktop as if you were sitting at the device.
- Mouse and keyboard
- Click, type, scroll and right-click as normal. All input is sent to the remote device in real time. From a Mac, Cmd works as Ctrl on a Windows device, so Cmd+C, Cmd+V, Cmd+A and Cmd+Z do what you expect; on a Mac device Cmd stays Cmd. From a Windows keyboard, the Windows key acts as Cmd on a Mac device. On a Windows device running the latest agent, Caps Lock follows your own keyboard: if it is on at your computer, it is on in the session.
- ClipboardText up to about 200 KB
- Copy text on your computer, click into the remote session and press Ctrl+V (Cmd+V on a Mac) to paste it on the device. Text you copy on the device, Windows or Mac, comes back to your computer's clipboard, ready to paste; this needs the latest agent on the device. If your browser blocks that, a Copy here button appears to finish the copy.
- Multi-monitor
- If the remote device has multiple monitors, a monitor selector appears in the toolbar. Switch between monitors to view any screen.
- Fullscreen
- Click the fullscreen button in the toolbar for a full-screen view. Press Esc to exit.
- Ctrl+Alt+Del
- Pressing Ctrl+Alt+Del on your own keyboard goes to your own computer, so use the Ctrl+Alt+Del button in the toolbar instead. It reaches the sign-in screen, unlocks the device and opens Task Manager. Available on Windows devices running the latest agent.
- Chat
- On a Windows device, the Chat button in the toolbar opens a chat with the person signed in to the device, docked beside the remote screen. It needs chat turned on in Settings and is not shown to Read Only users.
- Connection readout
- The toolbar shows how the session is connected and how it is doing: Direct or Via relay, the round-trip time, the frame rate, the video format and bitrate, and on devices running the latest agent how long the device takes to encode each frame. Click it for the full picture from both ends, including capture and encode times, dropped frames, the send queue, what the connection has been able to carry and the agent's CPU use.
Remote desktop on a Mac
A Mac shows its screen to Pckgr only with the person at the device's say-so: macOS asks for two permissions the first time, and nobody can grant them from the portal, over the network or through device management.
Make sure the Mac has updated its agent.
Remote Control stays disabled on a Mac until its agent has updated itself and checked in; hovering the button says so.Start a session with Remote Control as usual.
The Mac shows a prompt that Pckgr would like to record the screen, and the session ends with a message telling you the same.At the Mac, open System Settings → Privacy & Security → Screen & System Audio Recording and turn on pckgr-agent.
Then do the same under Accessibility, so you can click and type; without it the session is view-only and says so.Click Connect again.
From now on every session on that Mac connects straight away. Agent updates keep the permissions.
What differs from a Windows device:
- Someone must be signed in at the Mac; the login screen is not shown. A locked Mac shows its lock screen: type the user's password in the session to unlock it.
- The Mac and its display stay awake while the session runs, and sleep as usual once it ends. A Mac that is already asleep is offline until someone wakes it.
- There is no Ctrl+Alt+Del button.
- On macOS 15 and later, the Mac may ask the signed-in user now and then to keep allowing Pckgr to record the screen. Sessions carry on either way.
End a session
Any of these ends the session:
- Click End Session in the viewer toolbar (this also closes the tab).
- Navigate away from the remote desktop page.
- Close the browser tab.
In all cases, the session is cleanly terminated and recorded in the audit log.
Session limits
- Connection timeout5 minutes
- How long the agent has to connect after the session is created.
- Maximum duration2 hours
- Per session.
- Sessions per deviceOne at a time
- Starting another asks before taking over the one in progress.
Turn remote desktop off
Remote desktop is on for every tenant by default. If a client doesn't want remote access to their devices, an Owner or Admin can switch it off. The setting applies to that tenant only.
Go to Settings → Remote Access.
Switch off Allow remote desktop.
- The Remote Control button disappears from every device in the tenant.
- No new sessions can start, including from a saved or shared session link.
Warning
Requirements
Device side
- The device must be online: the agent is running and checking in.
- The agent version must support remote desktop. On a Mac the button stays disabled until it does.
- The network must allow outbound UDP or TCP to the STUN/TURN servers.
- A Mac needs a signed-in user, and Screen Recording (plus Accessibility to control it) allowed for Pckgr at the device; see Remote desktop on a Mac.
Browser side
- A modern browser with WebRTC support (Chrome, Edge, Firefox, Safari).
- The network must allow outbound UDP or TCP to the STUN/TURN servers.
How it works
Remote desktop uses WebRTC to set up a direct, peer-to-peer connection between your browser and the device. The Pckgr API is only used for initial session setup and signaling; screen content and input never pass through the server.
If a direct connection cannot be established (for example, both sides are behind restrictive firewalls), the connection falls back to a TURN relay server. The agent gives a direct connection a one-second head start before accepting a relayed one, so a browser on the same network as the device connects straight across it. All connections are encrypted with DTLS.
On Windows the agent captures the screen even when running as a background service, so it can display the Windows login screen, UAC prompts, and applications running as administrator. On a Mac the agent runs a helper in the signed-in user's session, which is the only place macOS allows screen capture, so a session needs someone signed in.
Troubleshooting
| Issue | Resolution |
|---|---|
| Session stuck on “Connecting” | Check that the device is online and the agent is running. The agent polls every 5 seconds, so it should pick up the session shortly. |
| Connection fails after signaling | This usually means a firewall is blocking the peer-to-peer connection. Ensure TURN relay is configured by your administrator, and check that UDP/TCP ports are not blocked on either side. |
| Low frame rate or lag | Click the connection readout in the toolbar. Via relay means no direct path was found, so traffic goes through a relay server; VPNs and strict firewalls do this, and every action takes a little longer. Dropped frames or a growing send queue mean the network cannot carry the bitrate, which the agent lowers on its own. Frames lost on the way mean the network is dropping data; with the latest agent the picture picks up again from a fresh frame each time instead of pausing. A high encode time means the device itself is the limit. |
| Black screen after connecting | The device may be locked or at the login screen. On Windows the agent can capture these screens, but it may take a moment to start streaming. Wait a few seconds; if it’s still blank, end the session and start it again. |
| Keyboard shortcuts not working | Some browser shortcuts (like Ctrl+W) are intercepted by the browser itself. Use fullscreen mode for the best input experience. |
| A Mac session ends at once with a message about Screen Recording | Pckgr has not been allowed to record the screen on that Mac yet. At the Mac, open System Settings → Privacy & Security → Screen & System Audio Recording, turn on pckgr-agent, then connect again. |
| A Mac session ends saying the screen is off or asleep | The Mac’s display is asleep, so there is nothing to capture. This is not a permissions problem; Pckgr can record the screen. Wake the Mac — someone at it presses a key or moves the mouse — then connect again. A Mac running with its lid closed and no external display has no screen to show. |
| A Mac session shows the screen but ignores clicks and typing | Accessibility has not been allowed for Pckgr on that Mac. At the Mac, open System Settings → Privacy & Security → Accessibility, turn on pckgr-agent, then connect again. |
| A Mac session ends saying nobody is signed in | The Mac is at the login window. Sign in at the Mac, then connect again. |
Audit trail
Every remote desktop session is logged in the audit log, including who started the session, which device was accessed, and when the session started and ended.