Skip to main content
This guide walks you through deploying the Origin Windows agent to managed endpoints using Microsoft Intune. The Origin installer is delivered as a standard Windows MSI — Intune accepts it directly as a line-of-business app with no wrapping or repackaging required. The provisioning JWT is passed as a command-line argument at install time.

​
Prerequisites

Confirm the following before proceeding:
  • Intune admin role (or a scope that permits app creation and assignment).
  • A valid Origin provisioning JWT (install token) — obtain from the Origin console under Settings → Installers.
  • An Entra ID security group scoped to your target devices.
  • The Origin installer MSI — download from the Origin console under Settings → Installers.
Both the installer binary and the provisioning JWT live in the same place in the Origin console: Settings → Installers. Download the MSI and copy the provisioning token from that screen before moving to Intune.

​
Packaging — Upload the MSI to Intune

Intune accepts the Origin installer as a Windows MSI line-of-business app — no wrapping or prep tool required. Intune auto-populates the product code, version, and basic detection rules from the MSI metadata. Line-of-business app: Upload the MSI directly to Intune. Detection, uninstall, and version tracking are handled automatically via the embedded product code. Upload path: Intune admin center → Apps → Windows → Add → Line-of-business app → upload origin-installer-windows-x64.msi directly.

​
Configuration — Configure the App in Intune

The wizard presents four tabs: App information, Scope tags, Assignments, and Review + create. Work through each tab in order.

​
1. App information

Fill in the fields as shown below. Fields not listed here can remain at their defaults.
Command-line argument noteReplace install_token_here with the JWT from Settings → Installers in the Origin console — the same screen where you downloaded the MSI. Keep the quotes around the token value. Do not include msiexec or /qn; Intune constructs the full install command automatically.

​
2. Scope tags

​
3. Assignments

Rollout hygieneStart with a small pilot group (2–5 test devices), validate registration, then broaden to your full target group.
Note: Required will force the Origin agent to install on any targeted system. If you’d like to make Origin available via Company Portal, assign your group instead under Available for enrolled devices and add users (not computers). This will make the Origin app available in Company Portal after targeted users authenticate in Company Portal.

​
4. Review + create

Review all settings, then click Create. Intune will process the MSI and make the app available for device assignment. Processing typically takes a few minutes.

​
Monitoring and Troubleshooting

​
Post-deployment checks

  1. Intune admin center → the app → Device install status. Review successes, failures, and pending counts.
  2. On an endpoint, tail the IME log: %ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
  3. Review the Origin install log on the endpoint: C:\ProgramData\Origin\Agent\Logs\install.log
  4. Confirm the Origin service is running:
  5. Verify backend registration in the Origin console — the endpoint should appear with a recent heartbeat.

​
Common install failures