deploy screenpipe enterprise to every Windows machine in a Microsoft Entra (Azure AD) security group via Intune. no per-laptop install, no IT touching individual devices. end-to-end takes ~10 minutes once you have the enterprise license.Documentation Index
Fetch the complete documentation index at: https://docs.screenpi.pe/llms.txt
Use this file to discover all available pages before exploring further.
this guide is for IT admins on screenpipe enterprise. consumer / team plans don’t ship the .intunewin package. if you don’t have a license yet, email louis@screenpi.pe.
prerequisites
- screenpipe enterprise license (your admin email is on the license’s
admin_emails) - Microsoft Intune subscription (included in Microsoft 365 E3/E5, EMS E3/E5, or Intune standalone)
- a Microsoft Entra security group containing the users that should receive screenpipe
- access to the Intune admin center
step 1 — download the .intunewin
sign in to screenpi.pe/enterprise with the admin email on your license, open the builds tab, and download the latest windows x64intunewin file.
the .intunewin is a Microsoft Win32 Content Prep wrapper around a code-signed NSIS installer (screenpipe_<version>_x64-setup.exe). screenpipe builds this for every enterprise release.
step 2 — create the Win32 app in Intune
in the Intune admin center:upload the package
App package file → upload the
.intunewin from step 1. Intune reads the installer metadata automatically.fill in app information
name, publisher, description as you’d like them to appear to end users in the Company Portal. logo: download from screenpi.pe/icon.png.
step 3 — program (install & uninstall commands)
/S is the NSIS silent-install flag — no UI shown to the user, no prompts. the .exe filename matches the build version inside the .intunewin; Intune autofills it when you upload.
| field | value |
|---|---|
| install behavior | System (machine-wide install — screenpipe enterprise is built perMachine) |
| device restart behavior | No specific action (no reboot required) |
| return codes | leave Intune’s defaults (0 success, 1707 success, 3010 soft reboot, 1641 hard reboot, 1618 retry) |
step 4 — requirements
| field | value |
|---|---|
| operating system architecture | x64 |
| minimum operating system | Windows 10 1809 |
step 5 — detection rules
pick Manually configure detection rules, add one rule:| field | value |
|---|---|
| rule type | File |
| path | %ProgramFiles%\screenpipe |
| file or folder | screenpipe.exe |
| detection method | File or folder exists |
| associated with a 32-bit app on 64-bit clients | No |
step 6 — dependencies & supersedence
screenpipe ships everything it needs (WebView2, ONNX Runtime, ffmpeg) bundled inside the NSIS installer. leave dependencies empty. if you’re updating from an older deployed version, set supersedence to the previous Intune app entry so Intune uninstalls the old version cleanly.step 7 — assignments
assign as Required to the Microsoft Entra security group containing your screenpipe users (e.g.screenpipe-users). Intune will install screenpipe on every device a group member signs into — typically within ~1 hour of next Intune check-in, or immediately if the user clicks Sync in Company Portal.
step 8 — activate the enterprise license
screenpipe needs the license key to enable enterprise mode (centralized telemetry, policy enforcement, dashboard access).- users paste it once
- pre-stage via registry (zero-touch)
after Intune installs screenpipe, users open Settings → Enterprise, paste the license key, and sign in. the key is stored in the Tauri secure store on their device.
verifying the deployment
- in the Intune admin center: Apps → screenpipe → Device install status shows per-device install state
- on the device:
C:\Program Files\screenpipe\screenpipe.exeexists, screenpipe icon appears in the system tray after first user sign-in - in the enterprise dashboard → devices tab: each installed device starts heartbeating within minutes of launch, scoped to your license
troubleshooting
installation succeeds in Intune but screenpipe doesn't open
installation succeeds in Intune but screenpipe doesn't open
NSIS perMachine installs to
%ProgramFiles%\screenpipe but doesn’t add a Start Menu autostart by default. users either launch from Start Menu, or you can enable autostart via the enterprise policy: in the enterprise dashboard → policy → toggle autostart_on_login: true.device shows install failure with exit code 2 or 1603
device shows install failure with exit code 2 or 1603
almost always insufficient privileges — confirm install behavior is System, not User. user-context installs can’t write to
%ProgramFiles%.screenpipe shows 'license invalid' after install
screenpipe shows 'license invalid' after install
either the registry pre-stage didn’t run before first launch (check Intune script assignment / order) or the license key has expired. check expiry in the enterprise dashboard → policy → license info.
audio recording doesn't start
audio recording doesn't start
on Windows, microphone access is permission-gated. either deploy a Windows privacy-settings profile that grants screenpipe microphone access, or have users approve once at first launch. policy-based grant is cleaner for fleet deployments — contact us if you need the AppX-style manifest mapping.
also see
- macOS Jamf / Kandji / Mosyle deployment: contact us —
.pkgdistribution flow is identical in shape to the above but with macOS MDM tooling - enterprise dashboard reference: screenpi.pe/enterprise (members, devices, pipes, policy, builds)
- questions or stuck: louis@screenpi.pe