Installing and deploying the agent

What the agent does

The Ubidesk agent is the component installed on machines you administer permanently. Once deployed, it:

stays connected to the workspace and reconnects automatically after a reboot, a network drop or a network change;
stays reachable when Windows boots into Safe Mode with Networking;
responds to Wake-on-LAN requests sent from the console.

The agent is not required for attended sessions: one-off users use a temporary no-install client. It is required for unattended access.

Choose the right package format

Four packages are available, one per platform:

Platform	Format	Mass deployment
Windows	MSI	GPO, Intune
macOS	PKG	Jamf
Debian / Ubuntu	DEB	package manager
RHEL / Fedora / SUSE	RPM	package manager

Download the matching package from your workspace. Each package carries your account binding, so the same package can serve the entire fleet.

Install on Windows

Interactive installation is a double-click on the MSI. For silent deployment, run from an elevated prompt:

msiexec /i ubidesk-agent.msi /qn

The agent registers as a Windows service, started automatically at boot.

Install on macOS

Open the PKG and follow the assistant. For silent deployment:

sudo installer -pkg ubidesk-agent.pkg -target /

The agent installs a daemon launched at login.

Install on Linux

On Debian or Ubuntu:

sudo apt install ./ubidesk-agent.deb

On RHEL, Fedora or SUSE:

sudo dnf install ./ubidesk-agent.rpm

The agent registers as a systemd service and restarts with the machine.

Deploy at scale

GPO (Windows): assign the MSI as a per-computer installation in a domain GPO. It applies at boot, with no local admin rights required.
Intune: publish the MSI as a line-of-business app, target a device group and track deployment state in the admin center.
Jamf (macOS): import the PKG into Jamf Pro, create an install policy and scope it to a static or dynamic group.

Firewall and network requirements

The agent needs outbound HTTPS only, on port 443. No inbound ports need to be opened on the target machine, and no VPN is required. If your environment forces traffic through a proxy, make sure it allows HTTPS to the Ubidesk infrastructure; everything else uses the same TLS 1.3 channel as the console.

Verify the installation

In the console, open the device list: the machine appears within seconds of installation.
Reboot the machine and confirm the device comes back online on its own.
On Windows, test a reboot into Safe Mode with Networking: the device must stay reachable.

Machines that are off or asleep can be woken with Wake-on-LAN if the hardware and BIOS allow it. See Unattended access: configuration.

Uninstall

On Windows, uninstall through the apps panel or the command line:

msiexec /x ubidesk-agent.msi /qn

On macOS, remove the package from the applications folder or through Jamf. On Linux, use the package manager (apt remove or dnf remove). After uninstalling, the device drops out of the workspace device list at the next sync.