Articles in this section

See more

Install Rise Player on Windows or Linux using an MDM

Last updated

Follow

This guide shows how to install and mass-activate multiple displays running the Rise Vision Electron Player using an MDM on Windows or the system command line on Linux.

Prerequisites

  • An MDM capable of remote script execution (e.g., Intune, Jamf, etc.) for Windows devices.
  • Shell access for Linux devices (or an MDM that can push and run shell scripts).
  • Your Rise Vision Company Claim ID.

Find your Rise Vision Company Claim ID

  1. Go to the Rise Vision Home page.
  2. Navigate in the left side panel to Settings → Company Settings.
  3. Copy your Claim ID from the bottom right side of the screen — you’ll need it below.

What the Claim ID does: When supplied to the installer, every device that runs the script will auto-activate into your company.

Mass Activation Overview

You’ll deploy a small script via your MDM (Windows) or run a shell script (Linux) that:

  1. Downloads the correct installer for the device.
  2. Runs the installer with the Claim ID and recommended flags.

Common flags:

  • --force-auto-start=true → ensures Player starts on login/boot.
  • --claim-id=<YOUR_CLAIM_ID> → activates the Player to your company.
  • --no-sudo (Linux only) → runs install steps without elevating with sudo (use when running as the user who will run Player).

Windows (MDM Remote Execute)

Use your MDM’s Remote Execute feature to run the following script on selected devices. Replace the placeholders before running.

:: ======== CONFIGURE THESE ========
set rise_claim_id=YOUR_CLAIM_ID
set rise_installer_path=PATH_FOR_EXECUTABLE   
:: e.g. %TEMP%\installer-win-64.exe
set rise_installer_url=https://storage.googleapis.com/install-versions.risevision.com/installer-win-64.exe
:: =================================
powershell Invoke-WebRequest "%rise_installer_url%" -OutFile "%rise_installer_path%"
"%rise_installer_path%" --force-auto-start=true --claim-id=%rise_claim_id%

MDM execution tips

  • In your device list, select the target devices → More Actions → Remote Execute (naming varies by MDM).
  • Ensure the script runs as the signed-in user or in a context that has access to the user profile where Player will run.

Linux (Ubuntu/Debian, Desktop)

Run the script as the user who will run Player (or push via MDM). Select the right installer URL for your architecture.
 

# ======== CONFIGURE THESE ========
export rise_claim_id=YOUR_CLAIM_ID
export rise_installer_path=PATH_FOR_EXECUTABLE   
# e.g. /tmp/installer-lnx-64.sh
export rise_installer_url=https://storage.googleapis.com/install-versions.risevision.com/installer-lnx-64.sh
# (For Raspberry Pi 32-bit use installer-lnx-armv7l.sh, for 64-bit use installer-lnx-arm64.sh)
# =================================
wget "$rise_installer_url" -O "$rise_installer_path"
chmod a+x "$rise_installer_path"
"$rise_installer_path" -- --force-auto-start=true --claim-id="$rise_claim_id" --no-sudo

Execution notes

  • Run as the target user (the account that will run Player) so auto-start and user-context settings apply correctly.
  • If your MDM supports privilege elevation, you can omit --no-sudo and allow the script to elevate where needed.

Optional: System Optimizations (Linux)

To apply recommended OS-level optimizations, create a privileged task to run:

$HOME/rvplayer/scripts/os-privileged-optimizations

Run this with your MDM’s Run With High Privileges (or equivalent) enabled.

Validation & Troubleshooting

  • After deployment, verify devices show as Active in Rise Vision and are associated with your company.
  • Confirm Rise Player starts automatically after reboot/login.
  • If activation fails, double-check:
    • The Claim ID was set correctly in the script.
    • The installer URL matches the device architecture.
    • The script ran as the correct user context.
    • Network access to storage.googleapis.com is allowed.

Appendix: Installer URLs

Related articles