Skip to content
All systems operationalv0.16.68FREE TIER · 3 DEVICESTENVO AI · MCP FOR CLAUDE & CURSOR
Back to BlogAnalysis

ConnectWise Control Alternative: Leaving the RMM Bundle

Tenvo Editorial Team10 min read
ConnectWise Control Alternative: Leaving the RMM Bundle

The renewal quote for the ConnectWise bundle lands, the number is higher than last year, and someone asks the obvious question: can we leave? The RMM and the PSA are painful to replace, but the piece that actually keeps people awake is remote access.

The renewal quote for the ConnectWise bundle lands, the number is higher than last year, and someone asks the obvious question: can we leave? The RMM and the PSA are painful to replace, but the piece that actually keeps people awake is remote access. ConnectWise Control, which has since gone back to its original name ScreenConnect, is the only way your technicians reach several hundred machines in offices they will never visit. Cancel things in the wrong order and on the morning after the contract ends you have no unattended access and no way to push a new agent. This article is about the order of operations, not about which logo to pick.

If what you want is a shortlist of tools, start with our ScreenConnect alternatives roundup. Here we assume you have more or less decided to leave and need an exit plan that does not cost you a single endpoint on the way out.

Why remote access is the hardest piece of the bundle to leave

In a bundled stack the access agent rarely stands alone. On most fleets the ScreenConnect client was installed by the RMM agent, through a policy or a deployment script, and it is the RMM agent that would also install whatever replaces it. That means the channel you use to deploy software and the channel you use to reach a machine are both owned by the vendor you are leaving. When the contract ends, both go dark on the same day. Every endpoint you have not converted by then becomes a site visit or a phone call to a user who has to read out a code.

The second problem is wiring. Over a few years the bundle grows integrations: a button in the PSA ticket that launches a session, session logs attached to the ticket automatically, technician roles mirrored from ConnectWise security groups, client and site names synced from the PSA company list. None of that moves with you, and each one needs either a replacement or an explicit decision to live without it.

The third is history. In February 2024 ConnectWise disclosed CVE-2024-1709, an authentication bypass in on-premises ScreenConnect 23.9.7 and earlier rated CVSS 10.0, alongside a path traversal bug, CVE-2024-1708. Exploitation began within days of the advisory. ConnectWise patched its cloud-hosted instances itself; the servers that got hit were mostly self-hosted ones that had not been updated in time. For a lot of teams the decision to leave dates from that week, and it is worth reading our piece on supply-chain risk in remote tools before you choose a replacement, because the same questions apply to whoever you move to.

What to inventory before you sign anything

Most migrations that go wrong go wrong because nobody knew how many machines there really were. Before you talk to a single vendor, export the following from the tools you still have:

  • Endpoint count by last check-in. Split it into seen in the last 7 days, seen in the last 30 days, and older. The old bucket is usually bigger than anyone expects: laptops that were replaced, servers that were decommissioned, a whole client you lost two years ago. Do not pay to migrate machines that no longer exist.
  • Unattended versus attended use. Which machines are reached without a user present (servers, kiosks, back-office PCs), and which only ever get ad-hoc support sessions. The first group is the one that must not lose its agent.
  • Operating system mix. Windows is easy to deploy silently. macOS needs Screen Recording and Accessibility permissions that a user or an MDM profile has to grant; our note on the macOS screen recording permission explains why. Linux machines on Wayland need their own check.
  • Who has access. Every technician account, every shared login, every former employee whose account was disabled in the PSA but not in the access tool.
  • What runs through the access tool. Toolbox scripts, backstage commands, saved credentials. Anything that lives only inside ScreenConnect disappears with it.
  • Contract terms. End date, notice period, auto-renewal clause, and whether the access product can be dropped separately from the RMM.

That last line matters more than it looks. If the notice period is 60 or 90 days and you miss it, you buy another year of the stack you are trying to leave. Put the notice deadline in the calendar first and plan backwards from it. Our list of procurement questions for remote access covers what to ask the new vendor so you do not sign yourself into the same corner again.

Decide what you are actually replacing

ConnectWise sells three things that look like one: remote monitoring and management, a professional services automation system, and remote access. A remote-access product replaces exactly one of them. Say so to whoever signs the budget, or someone will discover in week three that the new access tool does not patch Windows.

Piece of the bundleWhat it does for youWhat replaces it
ScreenConnect (Control)Attended and unattended sessions, file transfer, session logsA dedicated remote-access tool
Automate or ConnectWise RMMPatching, monitoring, alerting, scripted maintenanceAnother RMM, or Intune for Windows-heavy fleets
Manage (PSA)Tickets, contracts, time tracking, billingAnother PSA or a helpdesk tool

You do not have to replace all three at once, and usually you should not. Moving remote access first, while the RMM still works, is the safer order for the reasons in the next section. If you are wondering how much of the RMM's scripted work an AI agent can absorb, our comparison of RMM and AI agent automation gives an honest answer: one-off troubleshooting, yes; patch compliance reporting across a fleet, no. And if the project is really about having fewer tools overall, read helpdesk tool consolidation before you replace one bundle with another.

The cutover order that keeps unattended access alive

The whole trick fits in one sentence: use the deployment channel you are leaving to install the tool you are moving to, while it still works. Everything else is bookkeeping. In practice the sequence looks like this:

  1. Pilot on machines you can reach physically. Pick 10 to 20 endpoints across your OS mix, including at least one Mac and one server, and install the new agent by hand. Confirm unattended sessions survive a reboot, a user logout and a Windows update.
  2. Push the new agent through the old RMM. Package it as a silent install and deploy it as an RMM script or software policy to everything seen in the last 30 days. For Windows, a signed MSI with the right parameters is the cleanest route; our guide to deploying remote desktop via MSI walks through it. For macOS, pair the package with an MDM profile that pre-approves the permissions.
  3. Reconcile against the inventory. Export the device list from the new tool and diff it against the inventory export. Every machine on the inventory but not in the new tool goes on a gap list.
  4. Run both in parallel. Keep the old agent in place for at least two to four weeks. Technicians open the new tool first and fall back to ScreenConnect only when something fails, and every fallback gets noted.
  5. Chase the gap list. The stragglers are laptops that were off during the push, machines with a broken RMM agent, and devices behind a proxy that blocks the new relay. Use an attended ScreenConnect session to install the new agent by hand while you still can.
  6. Revoke, then uninstall. Disable technician accounts in ScreenConnect first, so nobody keeps using it out of habit. Then remove the old agent with an RMM script. Removing the old agent is the last step, not the first.
  7. Let the contract lapse. Before it does, export session logs and audit history you are obliged to keep.

For fleets in the hundreds or thousands, our piece on unattended access fleet deployment covers naming, grouping and access policies so the new tool is not a flat list of 800 hostnames on day one.

Things that bite during the parallel run

  • Firewall and proxy rules. The new agent needs outbound access to its own relay. Client sites with strict egress filtering will block it until someone adds the rule, and that someone is often the client's other IT provider. A tool that connects outbound, with no port forwarding, saves you from opening anything inbound, but the outbound rule still has to exist.
  • Credentials that lived in the toolbox. Local admin passwords and service accounts saved inside ScreenConnect need a proper home before you switch it off. Move them to a vault; credential vaulting for MSPs explains the options.
  • Session history. Contracts and some regulations require you to show who connected to what and when. Export the old logs and make sure the new tool records the same fields; our remote desktop audit logging guide lists what auditors usually ask for.
  • Accounts nobody remembers. A migration is the cheapest moment to clean up access. Run through an offboarding checklist for every former technician and every shared login, and do not recreate them in the new tool.

Where Tenvo fits, and where it does not

Tenvo is a managed remote-access service built on RustDesk. The client is licensed under AGPL-3.0, installers are signed, and there are native clients for Windows, macOS and Linux, plus a browser client in public beta. We run the relay: two servers in Frankfurt, Germany. Sessions use TLS with a per-device certificate. When two devices connect directly, peer to peer, the session is encrypted between those two devices only. When traffic has to fall back to the relay, TLS terminates at the relay, which means we, as the operator, are in a position to see that session.

Pricing is flat and public: Free at $0, Lite at $2.99 a month, Pro at $7.99 a month. Unattended access, file transfer and session history are part of the product, and the Tenvo AI agent can work on a remote machine with an explicit approval step before each action and a full audit log afterwards.

What Tenvo is not: it is not an RMM, it does not patch or monitor, it is not a PSA, and it does not come with an SLA. If you need patch management you will run an RMM next to it, and that is a normal setup, not a compromise.

A word on self-hosting, since teams leaving on-premises ScreenConnect often consider running their own server next time. February 2024 is a good illustration of what that choice costs: the exposed servers were the ones whose owners had to patch them themselves. Self-hosting makes sense when a written requirement forces it, such as a compliance rule that bars third-party infrastructure or an isolated network; in that case self-hosted RustDesk is the route to look at. Otherwise a managed relay costs less once on-call, patching, key custody and certificate renewal are counted, which is the argument in the hidden costs of self-hosting.

A realistic timeline

For a fleet of 300 to 500 endpoints across a dozen clients, six weeks is a reasonable plan. Week one: inventory, stale-agent cleanup and the pilot. Week two: mass deployment through the old RMM. Weeks three to five: parallel run and the gap list. Week six: revoke ScreenConnect accounts, uninstall the old agent, export logs. Add the contract's notice period on top, and start the clock early enough that week six lands before the renewal date, not after it.

When you price the move, compare the whole thing rather than the per-seat line: technician time for the migration, any RMM you still need, and what you stop paying for. Our remote access total cost of ownership breakdown gives you a worksheet for that.

The cheapest way to find out whether Tenvo fits your exit plan is the pilot step above. Grab the installer from the Tenvo download page, put it on ten machines you can walk up to, and try to break unattended access before you push it to the rest of the fleet.

Get Tenvo

Ready to try it yourself?

Free for 3 devices, no credit card. Up and connected in two minutes.

All articles