If you’re managing Linux servers alongside Windows systems, having everything accessible through a single remote access tool makes life significantly easier.

It's easier to install ScreenConnect on a Windows or a Mac that has a GUI than on a headless Linux server.

There's a copy link option when you use the Build Installer from ConnectWise however, in my case, the link didn't work. Or rather it did work but for some reason it didn't add the Linux server into my ConnectWise instance.

This was how I added an Ubuntu server to ConnectWise ScreenConnect (formerly ConnectWise Control).

Why Use ScreenConnect for Linux?

While ScreenConnect is commonly used for Windows endpoints, it also works well for Linux systems. Even headless servers.

This allows you to:

  • Remotely access servers without SSH only workflows
  • Keep all endpoints in one dashboard
  • Provide quick support without jumping between tools

Step 1: Download the Linux Client

From your ScreenConnect instance:

  1. Log into your ScreenConnect portal
  2. Click Access
  3. Select Build + (or your existing installer group)
  4. Choose Debian Linux (.deb)

This will download a .deb package.

Build Installer screen in ConnectWise ScreenConnect showing Debian Linux (.deb) agent selection
Choose the Debian Linux (.deb) option when generating the installer.

Step 2: Transfer the Installer

Move the file to your Ubuntu server:

scp ScreenConnect.ClientSetup.deb user@your-server:/home/user/

Or download it directly on the server using wget if you have the link.

Step 3: Install the Package

On your Ubuntu server:

sudo dpkg -i ScreenConnect.ClientSetup.deb
sudo apt-get install -f -y

This installs dependencies and registers the agent.

Step 4: Verify the Service

Check that the ScreenConnect service is running:

sudo systemctl status screenconnect.service

If needed:

sudo systemctl start screenconnect.service

Step 5: Confirm in Dashboard

Within a few seconds, the machine should appear in your ScreenConnect portal under the Access tab.

Mine showed up under "unknown" even if I filled in all the other information on the build installer. So you might have to move it into its proper spot on your dashboard.

From there, you can:

  • Open a remote session
  • Run commands
  • Manage the device like any other endpoint

Notes & Gotchas

  • Headless servers: You’ll typically get terminal access, not a full GUI
  • Firewall: Ensure outbound HTTPS (TCP 443) is allowed
  • SSH fallback: Still useful if ScreenConnect isn’t available
  • Host key errors (macOS): If you see SSH issues like:
no matching host key type found

You may need to enable legacy algorithms or update SSH configs.