---
title: "Beam Client: Installation, Deployment, and Configuration Guide"
slug: "beam-client-installation-deployment-and-configuration-guide"
description: "Install and deploy the ScreenMeet Beam Client on Windows and macOS with our comprehensive guide, covering manual and enterprise-scale rollouts."
updated: 2026-08-05T18:12:06Z
published: 2026-08-05T18:12:06Z
canonical: "docs.screenmeet.com/beam-client-installation-deployment-and-configuration-guide"
---

> ## 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.

# Beam Client: Installation, Deployment, and Configuration Guide

## Overview

This guide provides a full walkthrough for installing and deploying the ScreenMeet Beam Client across your organization. It supports both manual installs and enterprise-scale rollouts using deployment scripts or MDM tools. It also covers how to configure or change Beam settings post-installation for both Windows and macOS.

---

## 1. Installing the Beam Client

### Windows (Manual Install)

1. Download the Windows installer: [ScreenMeet.msi](https://downloads.screenmeet.com/windows/prod/v3/support/msi)
2. Follow the guided wizard:
  - Choose install location
  - Select whether to create desktop or Start menu shortcuts
  - Choose features: Remote Support (attended) and/or Beam (unattended)
  - Configure update preferences
3. When prompted:
  - Enter the **Device Group Key**
  - Select authentication method: `No authentication required`, `Windows credentials`, or `Password`
  - Optionally add label, tags, hide UI, and enable logging
4. Complete the install. The device will appear in the corresponding Beam Group within the ScreenMeet console.

---

### macOS (Manual Install)

1. Download the macOS installer: [ScreenMeetBeam.pkg](https://downloads.screenmeet.com/mac/prod/beam)
2. Run the installer and approve permissions for:
  - **Screen Recording**
  - **Accessibility**
3. After install, click the Beam icon in the menu bar and choose **Configure**
4. In the configuration window:
  - Paste in the **Device Group Key**
  - Select authentication method
  - Toggle options for:
    - Hide UI during Beam sessions
    - Check for updates
  - Confirm permissions are granted
5. Click **Save Preferences**

The macOS device will now appear in your Beam Group in the console.

---

## 2. Enterprise Deployment

### Windows (Command-Line Deployment)

Deploy using command-line tools like SCCM, RMM, or Intune.

**Example:**

```plaintext
msiexec /i ScreenMeet.msi /quiet ADDLOCAL="SupportFeature,BeamFeature" \
BEAMGROUPKEY="your-group-key" BEAMAUTHTYPE="password" BEAMPASSWORD="secure123" \
BEAMHIDEUI="1" BEAMFILTERLABEL="Laptop-IT" BEAMFILTERTAGS="it,windows"
```

**Key Parameters:**

| Variable | Description |
| --- | --- |
| `BEAMGROUPKEY` | Required. Binds device to a Beam Group |
| `BEAMAUTHTYPE` | `noauth`, `native`, or `password` |
| `BEAMPASSWORD` | Required if `BEAMAUTHTYPE=password` |
| `BEAMHIDEUI` | `1` hides Beam UI during session |
| `BEAMFILTERLABEL` | Custom label visible in Beam device list |
| `BEAMFILTERTAGS` | Comma-separated tags for sorting/filtering |
| `BEAMENABLELOG`, `BEAMUPLOADLOG` | Enable local or remote logging for support |

> The `Device Group Key` links the device to the correct organizational access group.

---

### macOS (MDM Deployment)

1. Upload the `ScreenMeetBeam.pkg` to your MDM
2. Use a pre-install script to generate the device configuration plist
3. Optional: Add an audit script to detect if Beam is missing and trigger install

**Example Command:**

```plaintext
mkdir -p /Users/Shared/ScreenMeetBeam
PLISTFILE="/Users/Shared/ScreenMeetBeam/Config.plist"
cat > "$PLISTFILE" <<EOF
<?xml version="1.0" encoding="UTF-8"?>
<plist version="1.0">
<dict>
  <key>authMode</key><string>password</string>
  <key>password</key><string>your-password</string>
  <key>groupKey</key><string>your-group-key</string>
  <key>hideUI</key><string>true</string>
  <key>label</key><string>mac-laptop-1</string>
  <key>tags</key><string>mac,finance</string>
</dict>
</plist>
EOF
```

**Key Parameters:**

| Variable | Description |
| --- | --- |
| `groupkey` | Required. Binds device to a Beam Group |
| `authmode` | `noauth` or `password` |
| `password` | Required if `authmode=password` |
| `hideUI` | `true` hides Beam UI during session |
| `label` | Custom label visible in Beam device list |
| `tags` | Comma-separated tags for sorting/filtering |

> Your exact scripts may vary depending on your MDM (Jamf, Kandji, Intune, etc.)

---

## 3. Changing Beam Settings After Installation

### Windows

Open the **Beam Configuration** app (search from Start Menu).

- **General Tab**:
  - Change group key
  - Temporarily disable Beam without uninstalling
- **Security Tab**:
  - Change authentication method
- **Advanced Tab**:
  - Enable/disable updates
  - Enable logging for troubleshooting

Click **Apply Changes** to save.

---

### macOS

Click the Beam icon in the top-right menu bar and choose **Configure**.

You will see:

- **Device Group Key** field and validation
- **Client Authentication Method** dropdown
- Options to:
  - Hide UI during sessions
  - Check for updates

Also confirms whether Screen Recording and Remote Control permissions are granted.

Click **Save Preferences** to apply changes.

---

## Summary

| Task | Platform | Manual | Enterprise Deployment |
| --- | --- | --- | --- |
| Install Beam Client | Windows | MSI installer | Command-line with parameters |
| Install Beam Client | macOS | PKG installer | MDM with pre-configured plist |
| Configure Post-Install Settings | Windows | Beam Configuration app | Overridable with install flags |
| Configure Post-Install Settings | macOS | Beam menu bar > Configure | Via configuration plist |
| Bind to Beam Group | Both | Use Device Group Key | Included in script or installer args |