---
title: "Preinstall the ScreenMeet Remote Support Client (Windows, macOS, and Linux)"
slug: "deploying-a-pre-installed-client"
description: "Deploy the ScreenMeet desktop client with ease using our guide on installation, organization restrictions, and command-line parameters for Windows, macOS, and Linux."
updated: 2026-08-12T22:01:58Z
published: 2026-08-12T22:01:58Z
canonical: "docs.screenmeet.com/deploying-a-pre-installed-client"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenmeet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Preinstall the ScreenMeet Remote Support Client (Windows, macOS, and Linux)

### Overview

Deploy the ScreenMeet desktop client in a preinstalled configuration so employees can enter support codes directly in the installed client without downloading the on-demand client each session. This article covers client download locations, the full set of Windows MSI and Beam command-line parameters, macOS PKG installation and organization restrictions, and Linux DEB installation.

---

### Prerequisites

- Administrative rights on target devices, or an MDM/deployment tool (Intune, Jamf, SCCM, Tanium, or similar).
- Network access to `*.screenmeet.com` and `*.scrn.mt` on port 443 (TCP and UDP).
- Your ScreenMeet Organization ID, if you plan to configure organization restrictions.
- Beam licensing, if you plan to install the Beam feature for unattended remote access.

Upgrade Requirement

If upgrading from a client version below `2.61.6`, uninstall the previous version before installing the new client.

---

### Deployment Command Generator

The preinstalled client supports a wide range of configuration options, so to simplify deployment we have created a deployment command generator. Select the options for your platform and the tool outputs a ready-to-use command that can be pasted into your MDM or deployment tool of choice.

You may open the generator using the link below, or opt to build your deployment command manually using the parameter tables in this article.

[](https://cdn.document360.io/9da39725-20e5-434f-83a4-d630456099dc/Images/Documentation/screenmeet-deploy-generator.html)screenmeet-deploy-generator15.32 KB[](https://cdn.document360.io/9da39725-20e5-434f-83a4-d630456099dc/Images/Documentation/screenmeet-deploy-generator.html)

---

### Client Downloads

The links below always provide the most up-to-date version of the ScreenMeet desktop client for each operating system.

| Operating System | File Type | Download Link |
| --- | --- | --- |
| Windows | MSI | [Download Windows MSI](https://downloads.screenmeet.com/windows/prod/v3/support/msi) |
| macOS | PKG | [Download macOS PKG](https://downloads.screenmeet.com/mac/prod/pkg/latest) |
| Linux (Debian-based) | DEB | [Download Linux DEB](https://downloads.screenmeet.com/linux/support/installer) |

---

### Windows Deployment

The Windows MSI installs the ScreenMeet Remote Support client and can optionally install the Beam service for unattended remote control. Use the command-line parameters below to tailor installation and behavior.

Best Practice

For most environments, enable `AUTOUPGRADE=true` so clients receive the latest features and security updates automatically. If auto-upgrade is disabled, plan to upgrade all clients every 3 to 6 months to maintain compatibility and stability.

#### Common MSI Settings

| Argument | Values | Description | Default |
| --- | --- | --- | --- |
| `APPLICATIONFOLDER` | Path | Installation folder | `[ProgramFilesX86]\ScreenMeet` |
| `PROGRAMMENUSHORTCUT` | `1` / <empty> | Add Program Menu shortcut | `1` |
| `DESKTOPSHORTCUT` | `1` / <empty> | Add Desktop shortcut | `1` |
| `AUTOCHECKUPDATES` | `true` / `false` | Enable update checks | `true` |
| `AUTOUPGRADE` | `true` / `false` | Auto-download and install updates (requires `AUTOCHECKUPDATES=true`) | `true` |
| `ADDLOCAL` | `SupportFeature[,BeamFeature]` | Features to install. Include `BeamFeature` only if licensed. | `SupportFeature,BeamFeature` |
| `ORGRESTRICT` | `True` / `False` (case sensitive, first letter uppercase) | Restrict usage to organizations in `ORGRESTRICTLIST` | `False` |
| `ORGRESTRICTLIST` | Comma-separated IDs | Allowed organization IDs | None |

#### Beam Service Settings

Beam Feature Licensing

Beam is ScreenMeet's unattended remote access tool and applies only if your organization has purchased Beam licensing. Customers without this licensing should omit `BeamFeature` and all Beam parameters from deployment commands.

The parameters below apply only when you install the `BeamFeature`.

| Argument | Values | Description | Default |
| --- | --- | --- | --- |
| `BEAMGROUPKEY` | String | Beam group key | Empty |
| `BEAMAUTHTYPE` | `noauth` / `native` / `password` | Authentication type | `noauth` |
| `BEAMPASSWORD` | String | Password for `password` auth | Empty |
| `BEAMHIDEUI` | `1` / `0` | Hide UI | `0` |
| `BEAMENABLELOG` | `1` / `0` | Enable file logging | `0` |
| `BEAMUPLOADLOG` | `1` / `0` | Upload logs to ScreenMeet | `0` |
| `BEAMFILTERLABEL` | String | Filter label | Empty |
| `BEAMFILTERTAGS` | Comma-separated | Filter tags | Empty |
| `BEAMNOTIFICATIONTYPES` | Comma-separated | Visible notification types (e.g., `error,info,warning`) | Empty |

#### Windows Example Commands

Silent install of the Support feature only, with a desktop shortcut:

```powershell
msiexec /i ScreenMeet.msi /quiet APPLICATIONFOLDER="C:\Program Files\ScreenMeet" ADDLOCAL="SupportFeature" DESKTOPSHORTCUT="1"
```

Silent install including Beam with password authentication and logging enabled:

```powershell
msiexec /i ScreenMeet.msi /quiet APPLICATIONFOLDER="C:\Program Files\ScreenMeet" BEAMGROUPKEY="abc123" BEAMAUTHTYPE="password" BEAMPASSWORD="securePass" BEAMENABLELOG="1" BEAMUPLOADLOG="1"
```

---

### macOS Deployment

The following command installs the ScreenMeet PKG from the current user's Downloads folder. Adjust the path based on your environment and deployment method.

```bash
sudo installer -pkg ~/Downloads/ScreenMeetSupport.pkg -target /
```

#### Supported Parameters

| Argument | Value | Description |
| --- | --- | --- |
| `code` | <session pin> | Connects automatically on startup |
| `confirmconsent` | `true` / `false` | Skip consent screen if `false` |
| `fileLogsLevel` | `1` to `4` | Logging level (1=Critical, 4=Debug) |
| `proxy_url` | URL | Proxy server URL |
| `proxy_username` | Username | Proxy username |
| `proxy_password` | Password | Proxy password |

#### macOS Example Command

Launch the installed client, connect to session PIN `977113`, and skip the consent screen:

```bash
open -n -a "/Applications/ScreenMeetSupport.app" --args code="977113" confirmconsent="false"
```

#### Organization Restrictions (macOS)

Organization restrictions provide an additional layer of security by allowing connections only to sessions generated from the specified Organization IDs. Add your production Organization ID to all applicable devices. Add lower-environment Organization IDs only to devices used to run and test sessions from those environments.

- Set or update Org IDs: `/Applications/ScreenMeetSupport.app/Contents/MacOS/ScreenMeet setAllowedOrgIDs=12345,54321`
- Remove Org IDs: `/Applications/ScreenMeetSupport.app/Contents/MacOS/ScreenMeet setAllowedOrgIDs=`
- Get currently allowed Org IDs: `/Applications/ScreenMeetSupport.app/Contents/MacOS/ScreenMeet getAllowedOrgIDs`

The following script applies organization restrictions after installation and confirms the configured IDs:

```bash
#!/bin/bash
SCREENMEET="/Applications/ScreenMeetSupport.app/Contents/MacOS/ScreenMeet"
ALLOWED_ORG_IDS="12345,54321"
if [[ ! -x "$SCREENMEET" ]]; then
    echo "ScreenMeet client is not installed or the executable could not be found."
    exit 1
fi
echo "Applying ScreenMeet organization restrictions..."
"$SCREENMEET" setAllowedOrgIDs="$ALLOWED_ORG_IDS"
echo "Configured organization IDs:"
"$SCREENMEET" getAllowedOrgIDs
```

---

### Linux Deployment

The Linux client is distributed as a DEB package for Debian-based distributions. Install it with your deployment tool or from the command line:

```bash
sudo dpkg -i screenmeet-support.deb
```

Supported Distributions

The ScreenMeet client supports Ubuntu 18.04.3 and later. For other distributions or deployment questions, contact [support@screenmeet.com](mailto:support@screenmeet.com).

---

### Verification

1. Launch the installed ScreenMeet client on a target device.
2. Generate a session code from your agent console and enter it in the client.
3. Confirm the session connects and, if organization restrictions are configured, confirm codes from other organizations are rejected.
4. If Beam was installed, confirm the device appears in your Beam group in the ScreenMeet console.

---