Platform Support
The operating systems and architectures the agent supports, further platforms the agent runs on, and the prerequisites for Remote Screen Control on Linux (Wayland) and macOS, and what Android devices support.
Platform Support
The agent runs on x64 and arm64 architectures and needs no third-party runtime dependencies. The server is distributed as a container image and is installed with Docker.
The operating systems below are officially supported. Where the notes state that troubleshooting support has ended, the agent still runs on that version but issues specific to it are not investigated.
For where each feature is available per platform, see the Feature Matrix.
X.8.1 Windows
| Operating system | Notes |
|---|---|
| Windows 11 | |
| Windows 10 | |
| Windows Server 2025 | |
| Windows Server 2022 | |
| Windows Server 2019 | |
| Windows Server 2016 | |
| Windows Server Core 2025 | |
| Windows Server Core 2022 | |
| Windows Server Core 2019 | |
| Windows Server Core 2016 | |
| Windows Nano Server 2025 | |
| Windows Nano Server 2022 | |
| Windows Nano Server 2019 | |
| Windows Server 2012 (R2) | All updates must be installed. No troubleshooting support. |
| Windows 8.1 | All updates must be installed. No troubleshooting support. |
| Windows 7 | All updates must be installed. No troubleshooting support. |
The audio call from the end user chat (A.7.7) is available for Windows devices only and needs agent 3.3.0.5 or later. Linux and macOS devices show no call button in the console and answer a call as not supported.
X.8.2 Linux
| Operating system | Supported versions |
|---|---|
| Ubuntu | 20.04, 22.04, 23.10, 24.04, 26.04 |
| Debian | 11, 12, 13 |
| RHEL | 8, 9, 10 |
| Oracle Linux | 8 |
| Rocky Linux | 8 |
| AlmaLinux | 8 |
| CentOS Stream | 9, 10 |
| Fedora | 39, 40, 42, 43, 44 |
| Alpine | 3.21, 3.22, 3.23 |
| SUSE Linux Enterprise | 15.7, 16.0 |
| openSUSE Leap | 16.0 |
| Azure Linux | 3.0 |
The Linux agent needs glibc 2.28 or later; Alpine uses its own musl build. Ubuntu 20.04, Debian 11, RHEL 8 and its rebuilds (Oracle Linux, Rocky Linux, AlmaLinux 8) need agent 3.3.0.11 or later. Devices there on an older agent do not update themselves and need a one-time reinstall, see Debug an agent.
SELinux in enforcing mode needs agent 3.3.0.11 or later; no policy module or relabeling is needed. Devices with SELinux enforcing on an older agent need a one-time reinstall, see Debug an agent.
X.8.3 macOS
| Operating system | Version | Notes |
|---|---|---|
| macOS Golden Gate | 27 | Apple silicon only; Intel Macs stay on Tahoe. |
| macOS Tahoe | 26 | Last release available for Intel Macs. |
| macOS Sequoia | 15 | |
| macOS Sonoma | 14 | |
| macOS Ventura | 13 |
The macOS programs of the agent (3.3.0.11 or later) are signed with an Apple Developer ID and notarized by Apple. Remote Screen Control and the tray icon on macOS need agent 3.3.0.11 or later (X.8.6). Remote Screen Control uses ScreenCaptureKit, which every macOS version in the table has. Intel Macs get the same signed build (osx-x64).
X.8.4 Additional confirmed platforms
The agent also runs on the platforms below. They are outside the supported set and not covered by troubleshooting support.
| Platform | Notes |
|---|---|
| Proxmox | Not officially supported. |
| Synology DSM | Not officially supported. |
| TrueNAS | Not officially supported. |
X.8.5 Remote Screen Control prerequisites on Linux
Remote Screen Control on Linux is supported on Wayland sessions: GNOME and KDE Plasma, and wlroots desktops with grim and ydotool (see the table below). Unlike on Windows, where capture and input are built in, the Linux agent relies on the Wayland desktop portal and a few host tools. Install the packages below on the controlled device (the one running the agent's user process), not on the operator's machine. Linux devices can be controlled from the web console, the Relay App (3.3.0.11 and later) and the NetLock app; all three show the consent and start states described below. Full feature detail is in A.7.
To confirm the device is running a Wayland session, run:
loginctl show-session "$(loginctl | awk '/ seat/{print $1; exit}')" -p TypeThis prints Type=wayland for the active graphical seat session.
Remote Screen Control on Linux has two independent layers, screen capture and input injection. Each tries a preferred path first and uses a fallback only when the preferred path is unavailable. The agent decides this automatically at runtime; you do not configure which path is used. The installed packages determine which paths are possible.
What runs out of the box, and what is a fallback
| Layer | Preferred path (tried first) | Fallback (only if the preferred path is unavailable) |
|---|---|---|
| Capture | ScreenCast portal, bridged by PipeWire + GStreamer | CLI screenshot tools: grim, scrot |
| Input | RemoteDesktop portal (NotifyPointer/NotifyKeyboard) | ydotool (writes to /dev/uinput) |
When the fallback engages:
- Capture falls back on desktops other than GNOME and KDE if the portal/PipeWire prerequisites are missing or the portal capture ends without a picture. It does not fall back when the user declined the screen-sharing dialog or left it unanswered. On GNOME and KDE the agent never switches to the command-line tools, because they cannot capture there; a missing prerequisite or a capture that delivers no picture is reported in the remote control window instead (see Troubleshooting).
- Input falls back if no portal input session is active (portal not running, permission not granted, or a session that only provides capture).
Where it works — display server and desktop
Whether Remote Screen Control works is decided by the display server and the desktop's portal backend, not by the distribution itself.
| Wayland desktop | Capture | Input | Result |
|---|---|---|---|
| GNOME | ScreenCast portal | RemoteDesktop portal | Full |
| KDE Plasma | ScreenCast portal | RemoteDesktop portal | Full |
| wlroots (Sway, Hyprland) | grim | ydotool (wlroots has no RemoteDesktop portal) | Works (mixed path) |
| No portal backend | — | ydotool | Not supported (no capture) |
On GNOME and KDE Wayland only the portal path works; the command-line capture fallbacks do not apply there (grim needs wlroots; scrot only sees XWayland windows). On those desktops the portal bridge packages below are required.
Applies to graphical desktops only. Remote Screen Control needs a screen to control. Headless server and cloud installs, common for RHEL/CentOS Server, SUSE Linux Enterprise Server, Alpine, Azure Linux, and Ubuntu Server, have no display server, so the feature does not apply there even though the agent itself runs.
The package names below are for Debian and Ubuntu (apt). Other distribution families ship the same tools under their own package managers (dnf, zypper, apk).
Required packages (Wayland portal path)
The preferred path is the desktop portal: org.freedesktop.portal.ScreenCast provides the screen and org.freedesktop.portal.RemoteDesktop injects input, without ydotool and without uinput access. The agent drives the portal through a small Python helper and bridges the PipeWire video stream with GStreamer.
Install the full portal path on the controlled device. On Debian and Ubuntu:
sudo apt install -y \
pipewire xdg-desktop-portal xdg-desktop-portal-gnome \
gstreamer1.0-tools gstreamer1.0-pipewire \
gstreamer1.0-plugins-base gstreamer1.0-plugins-good \
python3 python3-dbus python3-gi gir1.2-glib-2.0On KDE, install xdg-desktop-portal-kde instead of xdg-desktop-portal-gnome. A standard GNOME or KDE desktop already ships pipewire, xdg-desktop-portal, and its portal backend; the packages that are usually still missing are the GStreamer plugins (gstreamer1.0-plugins-base and gstreamer1.0-plugins-good, which provide the videoconvert / videoscale / videorate and jpegenc / multifilesink elements the capture pipeline uses) and the GStreamer↔PipeWire bridge with the Python bindings the helper uses.
Package names for other distribution families:
Debian / Ubuntu (apt) | Fedora / RHEL (dnf) | openSUSE (zypper) | Alpine (apk) |
|---|---|---|---|
pipewire | pipewire | pipewire | pipewire |
xdg-desktop-portal (+ -gnome / -kde) | xdg-desktop-portal (+ backend) | xdg-desktop-portal (+ backend) | xdg-desktop-portal (+ -gtk) |
gstreamer1.0-tools | gstreamer1-tools | gstreamer-utils | gstreamer-tools |
gstreamer1.0-pipewire | gstreamer1-plugin-pipewire (or pipewire-gstreamer) | gstreamer-plugin-pipewire | gst-plugin-pipewire |
gstreamer1.0-plugins-base | gstreamer1-plugins-base | gstreamer-plugins-base | gst-plugins-base |
gstreamer1.0-plugins-good | gstreamer1-plugins-good | gstreamer-plugins-good | gst-plugins-good |
python3 | python3 | python3 | python3 |
python3-dbus | python3-dbus | python3-dbus | py3-dbus |
python3-gi + gir1.2-glib-2.0 | python3-gobject | python3-gobject | py3-gobject3 |
Clipboard sync needs one of the clipboard tools of the session. On Wayland wl-clipboard is preferred and is the only tool that reports a clipboard change on its own, without polling; xclip (which works through XWayland) and xsel are the alternatives and the X11 path. Without any of them the device cannot reach its clipboard at all, and the viewer reports that; see A.7.6.
sudo apt install -y wl-clipboard # Wayland
sudo apt install -y xclip # X11 / XWaylandPasting files
Files pasted into a session (A.7.10) need agent 3.3.0.11 or later. On a GNOME or KDE Wayland session the device puts them on the clipboard with wl-copy from wl-clipboard (in the format Nautilus reads on GNOME, as a URI list on KDE and other desktops) and presses Ctrl+V through the desktop portal, so the open file manager window pastes them. wl-clipboard is not installed on a standard Ubuntu desktop; install it to get the paste:
sudo apt install -y wl-clipboardThe device copies the files into the user's Downloads folder instead when:
wl-clipboardis not installed,- the session is not a Wayland session, or
wl-copyfails or does not finish within five seconds.
The Downloads folder is the one from ~/.config/user-dirs.dirs, otherwise ~/Downloads. The files are readable for that user only, a name that already exists gets the form name (2).ext, and the viewer shows the path. On GNOME, wl-copy waits while the Activities overview is open, so a transfer during the overview ends up in Downloads. When the clipboard was set but the keystroke could not be sent, the files are on the clipboard and the user can paste them.
The transfer folders below /var/0x101 Cyber Security/NetLock RMM/Remote Agent/Clipboard Files/ belong to the user the files are pasted for (0700, files 0600); other accounts of the device cannot read them.
Unattended access on Wayland
The Wayland portal is built around user consent, which shapes how unattended access behaves:
- First connection to a device shows a one-time screen-sharing dialog that must be accepted on the controlled device. The agent requests a persistent grant. While the dialog is open, the remote control window in the console shows that it is waiting for the user on the device; the dialog stays until it is answered.
- Every connection after that runs without a prompt. Once the first picture has arrived, the agent stores the restore token the portal returned (per user, under
~/.config/netlock/pipewire_restore_token) and replays it on later connections, so the grant is restored without a prompt. This survives reboots: the grant persists until it is explicitly revoked. - Re-approval is only needed if the user revokes the grant (GNOME Settings → Sharing / Privacy → Screen Sharing, or the equivalent on KDE), a different user or application identity is used, or, rarely, a desktop update invalidates the token. If a stored token fails to restore, or restores without a picture arriving, the agent asks again with a fresh prompt on the same connection, and the new grant takes the place of the stored one once it has delivered a picture.
Limitation: the login screen is not covered. Because the portal lives inside the user's session, unattended capture covers a logged-in user (including after a reboot, once that user's session is back). It does not cover the login screen (GDM) or a state with no logged-in user. To guarantee a session always exists for unattended access, enable autologin on the device.
Wayland fallback (only if the portal path is unavailable)
If the portal cannot be used, for example in a session with no portal backend or in a locked-down or headless-style setup, the agent falls back to ydotool for input and CLI tools (grim, scrot) for capture. The capture tools are of use on wlroots desktops only; on GNOME and KDE they capture nothing and the agent does not use them. Install these only if you need that fallback to work:
sudo apt install -y ydotool grim scrotydotool injects at the kernel level through /dev/uinput, which needs two extra steps:
| Step | Command |
|---|---|
| Enable and start the daemon | sudo systemctl enable --now ydotool |
Grant access to uinput | sudo usermod -aG input "$USER", then sign out and back in |
Troubleshooting Remote Screen Control on Linux
Remote Screen Control on Linux works in Wayland sessions only, on the desktops in the table above. This section applies to agent 3.3.0.11 or later.
What a connection looks like
- On the first connection to a device, the desktop shows its screen-sharing dialog on the device. Someone at the device has to accept it. The dialog stays open until it is answered; the desktop portal ends an unanswered request by itself after about a minute.
- While the dialog is open, the remote control window (in the console, the Relay App or the NetLock app) shows "Waiting for the user to accept screen sharing on the device." Nothing needs to be done in the viewer during that time. Before the dialog opens, the window can briefly show "Starting the screen capture on the device." while the device prepares the request.
- After the dialog was accepted, the window shows "Starting the screen capture on the device." until the first picture arrives. On most devices that takes a moment; a slow or busy device is given up to 30 seconds.
- The permission is stored only once the first picture has arrived. Later connections restore it without a dialog; the window then shows only "Starting the screen capture on the device." until the picture is there. A stored permission that the desktop no longer accepts, or that brings no picture within 30 seconds, is followed by a fresh dialog on the same connection, and the new permission takes the place of the stored one once it has delivered a picture. You do not need to delete a file or restart the device for that.
| Message in the remote control window | Meaning | What to do |
|---|---|---|
| Waiting for the user to accept screen sharing on the device. | The screen-sharing dialog is open on the device and has not been answered. | Ask the person at the device to accept it. |
| Starting the screen capture on the device. | The device is starting the capture and the first picture is not there yet. It appears briefly before the screen-sharing dialog opens on a first connection, after the dialog was accepted, and on its own when a stored permission is restored without a dialog. | Wait. After the dialog was accepted, a slow device is given up to 30 seconds. |
| Screen sharing was not accepted on the device. | The dialog was declined or closed, or nobody answered it within about a minute. | Press Retry and accept the dialog on the device. |
| Screen capture components are missing on the device. See the Linux prerequisites in the documentation. | A program, Python module or GStreamer element of the portal path is not installed, or PipeWire or the desktop portal is not available in the user's session. The same text appears in the session selection when no session of the device can be captured for that reason. | Install the required packages and run the checks below. The device checks again half a minute after a failed check; nothing has to be restarted. Then press Retry. |
| No signal from the selected session. | No picture arrived within 30 seconds after sharing was granted, the capture stopped delivering, or the device stopped answering. | Press Retry. If it repeats, run the checks below and collect a debug log. |
Checks on the device
The commands work in a terminal of the desktop user and in a root shell alike, for example in the NetLock remote shell, which runs as root. Where a command reads data of the desktop user, it names that user explicitly: replace <user> with the user's name and <uid> with the numeric id that id -u <user> prints. In a root shell, ~ is root's home and journalctl --user is root's journal, so neither shows the desktop user's data.
Session type: must print Type=wayland (see the command at the top of this section).
Installed packages:
dpkg -l | grep -E 'xdg-desktop-portal|pipewire|gstreamer1.0|python3-dbus|python3-gi'GStreamer elements the capture pipeline needs. gst-inspect-1.0 evaluates only its last argument, so each element is checked on its own:
for e in pipewiresrc jpegenc videoconvert videoscale videorate multifilesink; do gst-inspect-1.0 --exists "$e" && echo "OK $e" || echo "MISSING $e"; doneEvery line must start with OK. A MISSING line names the element; pipewiresrc comes with gstreamer1.0-pipewire, videoconvert, videoscale and videorate with gstreamer1.0-plugins-base, jpegenc and multifilesink with gstreamer1.0-plugins-good.
PipeWire and the desktop portal in the user's session: pipewire, wireplumber, xdg-desktop-portal and the portal backend of the desktop (xdg-desktop-portal-gnome or -kde) must be listed:
ps -u <uid> -o pid=,args= | grep -E '[p]ipewire|[w]ireplumber|[x]dg-desktop-portal'Journal of the desktop user. Start a connection from the console first, then run this right afterwards and read the lines of xdg-desktop-portal, the portal backend, pipewire and gnome-shell:
journalctl -b _UID=<uid> --since "-10 min" --no-pagerThe line Failed to associate portal window with parent window is expected on every connection: the agent has no window of its own to attach the dialog to. It is not an error.
Stored permission of the user:
ls -la /home/<user>/.config/netlock/pipewire_restore_token is the stored screen-sharing permission. It exists only after a connection that delivered a picture. A logs folder next to it holds the debug log of the User Process once debugging was switched on (see below).
Asking for the permission again
The agent asks again by itself when a stored permission no longer works. To force a fresh dialog on the next connection anyway, revoke the permission in the desktop settings (GNOME Settings → Sharing / Privacy → Screen Sharing, or the equivalent on KDE), or delete the token file:
rm /home/<user>/.config/netlock/pipewire_restore_tokenNo restart is needed for either.
Collecting a debug log
Screen capture and input run in the User Process, inside the desktop session of the signed-in user. With debugging switched on it writes every step of a capture start to its log: the check of the prerequisites with the name of what failed, the portal requests and their answers, the time each stage took, the GStreamer pipeline with its error output, whether a stored permission was used, and the reason whenever the capture is stopped.
Switch debugging on as root with a marker file. Nothing has to be restarted:
sudo touch "/var/0x101 Cyber Security/NetLock RMM/User Process/debug.txt"Start a connection from the console. The User Process runs as the desktop user and writes its log below that user's home, next to the stored permission: Debug.txt and Error.txt, readable for that user and root only, in:
ls -la /home/<user>/.config/netlock/logs/The log holds neither what was typed or clicked during a session (only the kind of an input command and the kind of an error) nor the stored permission token, so it can be sent to support as it is.
Remove the marker file afterwards to switch debugging off; the log grows without a limit:
sudo rm "/var/0x101 Cyber Security/NetLock RMM/User Process/debug.txt"The Remote agent's log records the capture results the User Process reports to it; Debug an agent describes how to switch on debugging for the agent services and, under Debug the User Process, the same steps as above.
X.8.6 Remote Screen Control on macOS
Remote Screen Control on macOS needs agent 3.3.0.11 or later on the device. The console, the Relay App and the NetLock app offer screen control and the end user chat for a macOS device only once the device reports that agent version; a Mac on an older agent shows neither entry. Full feature detail is in A.7.
What runs on the device
Screen control runs in the User Process of the agent, which starts in the session of every signed-in user. The tray icon shows the consent prompt, the support badge and the end user chat. Nothing has to be installed in addition on the device.
The programs of the agent are signed with the Apple Developer ID of the publisher and notarized by Apple. The permissions below are granted to the signed program, so an agent update keeps them.
Permissions on the Mac
macOS hands out the screen and the input only to programs that are allowed in System Settings. The User Process asks the system once after it starts, which shows the system's own notice; nothing waits for an answer, and the agent never opens System Settings by itself. An administrator at the Mac allows both entries once:
| Permission | Where | What it is needed for |
|---|---|---|
| Screen & System Audio Recording | System Settings > Privacy & Security > Screen & System Audio Recording, entry NetLock RMM User Process | The picture. Without it the session shows no signal. |
| Accessibility | System Settings > Privacy & Security > Accessibility, entry NetLock RMM User Process | Mouse and keyboard input. Without it the picture runs and the input is dropped. |
Both switches ask for an administrator password on the Mac. When the screen recording permission is given while the User Process runs, the User Process restarts itself once so that the permission takes effect; a session that is open at that moment shows the picture after Retry. Until a permission is given, the remote control window names it:
| Message in the remote control window | Meaning | What to do |
|---|---|---|
| Screen recording is not allowed for NetLock RMM on this Mac, or has to be confirmed there again. … | The screen recording permission is missing, or macOS asks for it to be confirmed again (see the next section). The same text appears in the session selection when no session of the device can be captured for that reason. | Allow the entry in System Settings on the Mac, then press Retry. |
| Mouse and keyboard input is not allowed for NetLock RMM on this Mac. … (line at the lower edge of the picture) | The Accessibility permission is missing. The picture runs; clicks and keys do not reach the Mac. | Allow the entry in System Settings on the Mac. The line disappears on its own once the Mac accepts input again. |
| No active session — the display may be off or the device is at the login screen. | No user is signed in on the Mac, or the signed-in user's User Process is not running. | Sign a user in on the Mac. The login screen is not covered (see Limits). |
| No signal from the selected session. | The capture stopped delivering or the device stopped answering. This is also what the window shows when someone at the Mac stops the recording with the screen recording indicator in the menu bar: macOS ends the capture for that session, and the device does not start it again on its own. | Press Retry; a new session starts the capture again. If it repeats, run the checks below and collect a diagnosis. |
The recurring confirmation on macOS 15 and later
macOS 15 (Sequoia) and later show the notice "NetLock RMM User Process is requesting to bypass the system private window picker and directly access your screen and audio" about once a month for programs that capture the screen without the system picker, more rarely while the capture is used regularly, and sometimes after a system update. Someone at the Mac has to choose Allow for one month; until then the remote control window shows the screen recording message above. Unattended access to a Mac with nobody in front of it can therefore be interrupted about once a month. On managed Macs the MDM key forceBypassScreenCaptureAlert suppresses the notice (see the next section).
Deployment with MDM
On Macs under device management a configuration profile can set what an administrator would otherwise click. The profile names the program by its bundle identifier and its code requirement. Both are read from an installed agent on any Mac, so the values in the profile are exactly those of the signed program:
B="/usr/local/bin/0x101_Cyber_Security/NetLock_RMM/User_Process/NetLock RMM User Process.app"
codesign -dv --verbose=4 "$B" 2>&1 | grep -E "^Identifier|^TeamIdentifier|^Authority"
codesign -d -r - "$B" 2>&1 | sed -n 's/^designated => //p'The first command prints the identifier com.netlock.rmm.user.process, the Team ID and the certificate chain (Developer ID Application: …, Developer ID Certification Authority, Apple Root CA); the second prints the designated requirement, which goes into the profile as the code requirement. For the tray icon use the bundle Tray_Icon/NetLock RMM Tray Icon.app in the same folder (identifier com.netlock.rmm.tray.icon).
- Accessibility can be granted in advance with a Privacy Preferences Policy Control (PPPC) payload (
com.apple.TCC.configuration-profile-policy) for the identifiercom.netlock.rmm.user.process, identifier type bundle ID, the code requirement from above, serviceAccessibility, allowed. - Screen recording cannot be granted by a profile; Apple requires the click on the Mac. The PPPC payload can set
Allowed Standard User To Set System Servicefor the serviceScreenCapture, so that a standard user may allow it without an administrator password. - Background items: a Service Management payload (
com.apple.servicemanagement) with a rule of typeTeamIdentifierand the Team ID from above keeps the LaunchAgents and LaunchDaemons of the agent enabled and hides them from Allow in the Background in System Settings > General > Login Items. - The monthly notice is suppressed with
forceBypassScreenCaptureAlert(payloadcom.apple.applicationaccess), available from macOS 15 on.
NetLock does not ship a ready-made profile.
Keyboard, mouse and clipboard
The device applies the modifier keys of a Windows or Linux keyboard as follows: Ctrl becomes Command, the Windows or Meta key becomes Control, Alt becomes Option. Ctrl+C, Ctrl+V and the other shortcuts of the viewer therefore reach the Mac as Command shortcuts, and Control+C in a Terminal is sent with the Windows key. When the viewer itself runs on a Mac and the device is a Mac, nothing is translated: Command stays Command and Control stays Control. The Ctrl+Alt+Del button of the viewer opens Force Quit Applications (Command+Option+Esc) on the Mac. The keyboard shortcut menu of the viewers lists Mac shortcuts such as Command+Tab, Spotlight and Mission Control in Mac terms and sends them as listed (A.7.8). Text is typed as the characters that were typed, independent of the keyboard layout of the Mac.
The clipboard works as described in A.7.6, with one difference on macOS 15.4 and later: macOS asks the user before a program reads the clipboard. The automatic sync of what the user copies therefore stays off on such a Mac until someone at the Mac sets the clipboard access of NetLock RMM User Process to Always Allow (System Settings > Privacy & Security > Paste from Other Apps); the entry appears there after the first time macOS asked. Taking the remote clipboard with Ctrl+C and the view dialog still read it on request, and macOS may ask the user at the Mac each time. On macOS before 15.4 the clipboard works without a question.
Files pasted into a session (A.7.10) are put on the general pasteboard as file URLs and pasted with Command+V into the application in front: a Finder window pastes into its folder, the Finder without a window onto the desktop, Mail adds an attachment. The Finder is not brought to the front. Writing to the pasteboard needs no permission; the keystroke needs the Accessibility permission. Without it the files stay on the clipboard and the viewer says that the user can paste them. This needs agent 3.3.0.11 or later.
Unattended access
Once both permissions are given, every connection to a signed-in user runs without a prompt and needs nobody at the Mac, apart from the monthly notice above on macOS 15 and later. The consent prompt and the support badge follow the policy of the device as on the other platforms (Policy > Tray Icon > Remote Screen Control); the tray icon shows both.
Limits
- The login screen is not covered. The User Process runs inside a user's session, so a Mac with nobody signed in, and a Mac at the FileVault pre-boot screen, shows No active session. A Mac that is locked with a user signed in can be captured.
- With fast user switching, every signed-in user has a session of their own in the session selection; the one that owns the screen is the one to pick.
- Audio calls and Backstage are not available on macOS.
- Intel Macs (
osx-x64) get the same signed build.
Checks on the Mac
Run as the signed-in user in a Terminal on the Mac:
# Is the User Process registered and running in this user's session?
launchctl print "gui/$(id -u)/com.netlock.rmm.user.process" | grep -E "state|pid|path"
# Signature and notarization of the program
B="/usr/local/bin/0x101_Cyber_Security/NetLock_RMM/User_Process/NetLock RMM User Process.app"
codesign --verify --deep --strict --verbose=2 "$B"
spctl -a -t exec -vv "$B"codesign --verify answers valid on disk and satisfies its Designated Requirement; spctl answers accepted with source=Notarized Developer ID.
To make macOS ask for a permission again, remove the entry in System Settings or reset it on the Mac:
tccutil reset ScreenCapture com.netlock.rmm.user.process
tccutil reset Accessibility com.netlock.rmm.user.processCollecting a diagnosis
The User Process has a diagnosis mode that checks, step by step and without a session from the console, what a screen control session needs: the process and how it was started, the code signature, the GUI session, the permissions, the displays, ScreenCaptureKit and the content it can share, a short stream with the number of pictures and the time to the first one, the encoding of a picture, the stop of the stream, the capture backend and single pictures. Every step ends with OK, WARN, FAIL or SKIP and the reason; the exit code is 0 when no step failed (WARN counts as passed).
NetLock_RMM_User_Process --diagnose [--seconds N] [--screen I] [--out FILE] [--input] [--clipboard] [--request]--seconds N: how long the stream runs and is counted, 1 to 120, default 5.--screen I: the display to capture, counted from 0, default 0.--out FILE: writes the report to this file as well, line by line, so the file holds everything up to a step that does not return.--input: sends a small mouse movement there and back.--clipboard: writes a marker to the clipboard, reads it back and restores the previous content; skipped when the clipboard holds anything but plain text.--request: lets the system show its notices for the missing permissions.
The diagnosis does not connect to the agent and leaves a running User Process alone. Started from SSH it has no GUI session and stops after the session check. Started from a Terminal on the Mac, the permissions it reports are those of the Terminal, not those of the User Process; the report says so in its Process step (not started by launchd). For the real picture, start it once through launchd in the session of the signed-in user. As that user, in a Terminal on the Mac:
P="/usr/local/bin/0x101_Cyber_Security/NetLock_RMM/User_Process/NetLock RMM User Process.app/Contents/MacOS/NetLock_RMM_User_Process"
cat > /tmp/com.netlock.rmm.diagnose.plist <<PLIST
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key><string>com.netlock.rmm.diagnose</string>
<key>ProgramArguments</key>
<array>
<string>$P</string>
<string>--diagnose</string>
<string>--seconds</string><string>10</string>
<string>--out</string><string>/tmp/netlock-diagnose.txt</string>
</array>
<key>RunAtLoad</key><true/>
<key>StandardOutPath</key><string>/tmp/netlock-diagnose.out</string>
<key>StandardErrorPath</key><string>/tmp/netlock-diagnose.err</string>
</dict>
</plist>
PLIST
launchctl bootstrap "gui/$(id -u)" /tmp/com.netlock.rmm.diagnose.plist
sleep 20; cat /tmp/netlock-diagnose.txt
launchctl bootout "gui/$(id -u)/com.netlock.rmm.diagnose"; rm /tmp/com.netlock.rmm.diagnose.plistAdd --input and --clipboard to the arguments to test input and the clipboard as well. The report holds no picture content, nothing that was typed and no clipboard content, so it can be sent to support as it is.
The User Process also writes a debug log when debugging is switched on; see Debug the User Process.
X.8.7 Android devices
Android phones and tablets run the NetLock RMM app instead of an agent. They are enrolled with a code from the console (Deploy your first agent) and sync on their own interval, at least every 15 minutes.
| Function | Android |
|---|---|
| Inventory, battery, storage, network, compliance | Every Android version the app supports |
| Locate, ring, message | Every supported version |
| View the screen | Every supported version; the user agrees for every session |
| Control the screen: taps, swipes, scrolling, system buttons | Every supported version, with the app's remote control service switched on and the policy switch on |
| Control the screen: typing text and editing keys | Android 13 and later |
| Endpoint protection (anchor, grants for screen sessions) | Every supported version, with the current NetLock RMM app; the app's data is not part of backups or device transfers, so a new phone is enrolled again (A.13.11) |
Notes for screen control (A.7.12):
- An app installed from an APK file shows the remote control service as Controlled by Restricted Setting until
Allow restricted settingsis chosen inSettings→Apps→NetLock RMM Agent App→⋮. - The app opens Android's list of accessibility services; the service is switched on there.
- A control session always shares the entire screen. A view session shares what the user chooses; from Android 15 the prompt preselects a single app.
- On Android 16 and later the service cannot be switched on during a phone call.
- On recent Android versions locking the screen ends a screen session; the phone cannot be unlocked remotely.
- Apps that protect their content appear black, and some system dialogs accept no remote input.
- Android may show its own reminder that an accessibility service has access to the device.
- Devices with Android's advanced protection mode may block accessibility services that are not accessibility tools; the viewer then reports that the service is not enabled.
Related chapters
- Chapter 3 — Devices — device inventory and remote access.
- A.7 — Remote Screen Control — session switching, recording, and unattended access.
- X.7 — Feature Matrix — per-feature platform availability.
Feature Matrix
A scannable overview of every NetLock RMM feature area and its platform support, with links to the chapter that documents each in full.
Public API
The REST API of the server: tokens, scopes and rate limits in brief, where the Swagger reference lives, the custom field endpoints with level values and effective values, and the automation rules.