Corporate / Intune

Corporate deployment with Intune

日本語

Use the Intune distribution when IT controls installation and updates. It installs XKey machine-wide and contains no Standalone self-updater.

Files to download

Get matching files from GitHub Releases (opens in a new tab):

FileUse
Intune-x64.intunewinUpload as a Windows app (Win32) in Intune
Intune ZIPMSI, signed install/uninstall/detection/migration scripts and supporting files
Intune-x64.msiDirect installation or MSI inspection
DEPLOYMENT.mdExact package-specific requirements and commands

The .intunewin is a transport container. Intune downloads its contents to managed devices and runs the commands IT configures. Users do not run this file directly.

Prepare devices

  • Install desktop PowerPoint, .NET Framework 4.8+, VSTO Runtime and the required machine-wide WebView2 Evergreen Runtime. Check the package guide for its minimum runtime version.
  • Deploy prerequisites as separate Intune dependencies.
  • Identify existing MSI, Standalone and per-user ClickOnce installations before assignment. Standalone and Intune cannot coexist.
  • Run Migrate-XKeyClickOnce.ps1 as each affected Windows user. It reports by default; use -Remove only after reviewing the confirmed XKey installation. Do not run user migration as SYSTEM. One user's successful migration does not cover other accounts.

Configure the Win32 app

Upload the supplied .intunewin, select System installation behavior and Windows x64 requirements, and use the supplied commands:

Install:

powershell.exe -NoProfile -NonInteractive -ExecutionPolicy AllSigned -File .\Install-XKey.ps1

Uninstall:

powershell.exe -NoProfile -NonInteractive -ExecutionPolicy AllSigned -File .\Uninstall-XKey.ps1

Use the generated Detect-XKey.ps1 as a custom detection script in 64-bit PowerShell, with signature checking enabled. Use the script from the package, not a source template. Detection checks the Intune distribution, version, files and registration and accepts equal or newer versions.

Map 0 to success, 3010 to soft reboot and 1618 to retry. If PowerPoint is running, installation defers without closing presentations. IT may need to reschedule after the user closes PowerPoint; retries are finite.

See Microsoft's Win32 app setup instructions (opens in a new tab) for the Intune configuration screens.

Deploy updates

Pilot a newly versioned Intune package before wider assignment. Configure supersedence with Uninstall previous version = No: the new XKey MSI performs the upgrade. IT controls targeting and timing; a GitHub publication does not change an existing assignment.

See Microsoft's supersedence guide (opens in a new tab) for that setting. Do not change to Standalone while an Intune assignment still manages the device.

Logs and removal

Management script logs are under %ProgramData%\Infiniti\XKey\Logs. Uninstall preserves user settings and application data. The wrapper succeeds when the managed app is already absent. Never use Win32_Product for detection.

Test before broad rollout

Test silent SYSTEM installation, standard-user PowerPoint startup, detection, upgrade, repair, uninstall and settings preservation on disposable devices. Test both Office bitness configurations you intend to support. A direct administrator MSI installation does not validate Intune behavior.

Review the package's validation-report.json for automated results and acceptance limits. Complete a real Intune pilot before a broad deployment. IT may need to approve the signing publisher under company policy; do not import the signing certificate into Trusted Root.