ScreenConnect Integration on the Device

Summary:

octoja comes with its own remote maintenance solution. Nevertheless, many partners also use ScreenConnect (ConnectWise Control)—for unattended access, for devices without an RMM agent, and for customer environments where the tool has been in use for years. What’s missing is a way to bridge these two worlds: a button on the device that opens a ScreenConnect session for that specific computer.

In other RMMs, this is a basic setting: enter the instance URL and instance ID once, and then a connection point is available on every device.

Suggestion

• An entry for the ScreenConnect instance in the administration settings: base URL, instance ID, and optionally credentials for the ScreenConnect API.

• Device-to-session mapping. The agent detects the installed ScreenConnect service; the session can be established using its instance ID and the machine identifier. At the simplest level, a link following the pattern https://<instance>/Host#Access/All%20Machines//<GUID>/Join is sufficient.

• Access from the device page and device list so that switching to the other tool requires just one click and avoids having to search in a second console.

• Display whether the ScreenConnect agent is installed and running. This allows you to see where it is missing during a rollout and where it remains behind when decommissioning.

Why This Is More Than Just Convenience

Anyone who uses two remote maintenance tools wastes time on mapping: The alert is in the RMM, the session is in the other tool, and the machine names don’t always match. During an incident, that’s exactly the minute nobody has to spare.

For partners switching from another RMM, there’s an added consideration: the ScreenConnect integration is standard there. Losing it during the switch is immediately noticeable.

Implementation suggestion: generic over individual

The board already lists “TeamViewer Integration” (10 votes) and “Integrate Rust Desk remote maintenance tool.” That’s the same request three times over. Instead of three individual solutions, a general tool integration would be the better approach:

Field Content Name Button display name URL template with placeholders for device name, serial number, instance ID, device GUID Service or process name for the “installed / running” display Visibility per customer or globally

This way, each partner can enter their own tool—ScreenConnect, TeamViewer, RustDesk, or whatever else they use—and octoja doesn’t have to maintain a separate integration for every product.