Intune deployment for TwinPane (Win32 app step-by-step)

Deploy TwinPane Client and Server through Microsoft Intune as Win32 apps, including install commands, detection rules, assignment strategy, and rollout tips.

This guide walks through deploying TwinPane in Microsoft Intune using Win32 apps. It covers packaging, install/uninstall commands, detection rules, and safe rollout.

Prerequisites

  • Intune admin access.
  • TwinPane installers and license key.
  • Test device group for pilot rollout.

If you need the command-line switches first, see Silent install (Client and Server).

1. Package the installer as a Win32 app

Intune Win32 apps require .intunewin packaging.

  1. Place TwinPane - Client.exe in a source folder.
  2. Use the Microsoft Win32 Content Prep Tool to create a .intunewin package.
  3. Repeat for TwinPane - Server.exe if you also deploy server components via Intune.

Use separate app objects for Client and Server.

2. Create the TwinPane Client app in Intune

In Apps > Windows > Add > Windows app (Win32):

  • Upload your Client .intunewin.
  • Name: TwinPane Client.
  • Publisher: TwinPane (or your internal standard).

Install command

"TwinPane - Client.exe" /LICENSE=YOUR-LICENSE-KEY /VERYSILENT

Uninstall command

"C:\Program Files\TwinPane\TwinPane - Client\unins000.exe" /VERYSILENT

Adjust the path if you use a custom install directory.

3. Configure detection rules

Use reliable detection to avoid repeated installs.

Recommended options:

  • Registry detection:
    • Hive: HKLM
    • Key path: SOFTWARE\FileSyncBridge\Client
    • Value: InstallPath
    • Detection method: value exists
  • Or File detection on the installed executable path.

For registry references, see Registry keys (Client and Server).

4. Configure requirements and return codes

  • Architecture: match your fleet standard.
  • Minimum OS: Windows 10/11 as applicable.
  • Leave default success code handling unless your packaging changes exit behavior.

5. Assignments and rollout strategy

Roll out in phases:

  1. Pilot IT/admin test group.
  2. Small production group.
  3. Broad production group.

Use Required assignment for managed rollout.

6. Deploying TwinPane Server via Intune (optional)

If your server hosts are Intune-managed:

  • Create a second Win32 app for TwinPane - Server.exe.
  • Use:
"TwinPane - Server.exe" /LICENSE=YOUR-LICENSE-KEY /VERYSILENT

For AVD/Citrix/RDS shared hosts, many teams prefer server deployment through image pipeline or host management tools instead of end-user Intune flow.

7. Validation checklist

On a pilot device:

  • TwinPane Client is installed.
  • License key applied.
  • App starts at user logon (if configured).
  • File opening from remote session works end-to-end.

Common pitfalls

  • Detection rule too weak, causing reinstall loops.
  • Wrong uninstall path in Intune app config.
  • Same package used for Client and Server accidentally.
  • Rolling out to all devices before pilot validation.

Related guides

Related guides

Group Policy rollout for registry defaults

Configure TwinPane default settings at scale using Group Policy registry preferences for HKLM and HKCU paths, including license and server behavior flags.

Registry keys (Client and Server)

Reference for the Windows registry keys and values used by TwinPane Client and Server for settings, license, and deployment.

SCCM deployment with detection rules

Deploy TwinPane through Microsoft Configuration Manager (SCCM/MECM) with silent install commands, robust detection rules, and phased collection rollout.