Custom Packaging
Upload your own installers — EXE, MSI, or scripts — and let Robopack automatically detect install commands, uninstall commands, and detection methods. Packages are tested on a virtual machine before deployment.
How it works
- Click Convert Package and upload your installer
- Robopack detects the input type (executable, MSI, script) and the installer platform (WixBurn, InnoSetup, Nullsoft, etc.)
- Based on the platform, Robopack suggests a silent install command
- With Analyze and Test enabled, a virtual machine is provisioned to verify everything works
VM testing workflow
When you upload a custom app with Analyze and Test enabled, Robopack:
- Uploads to secure storage
- Scans for viruses
- Provisions a virtual machine
- Installs the app and verifies the install command works
- Discovers the uninstall command
- Uninstalls the app and verifies cleanup
- Generates a detection method for Intune
- Reports any leftover files after uninstall
Supported installer types
| Type | Examples |
|---|---|
| .exe | Any installer framework — WixBurn, InnoSetup, Nullsoft, InstallShield, etc. |
| .msi | Windows Installer packages |
| Scripts | PowerShell, batch files |
Custom App Settings
Custom App Settings let you define configuration that is applied to some or all versions of an app. This means you configure your app once and have it take effect for every future version.
- Per-app — all settings are defined per app
- Global or per-tenant — each setting can apply to all tenants in your organisation, or be scoped to specific tenants to override the global configuration
Custom App Settings are managed in App Settings in the left menu.
What you can configure
| Setting | Description |
|---|---|
| Target version | Pin to a specific version |
| Target architecture | Restrict to a specific architecture or allow any |
| Target scope | Machine or User scope |
| Script template | Override the script template for this app (or inherit from the organisation default) |
| Signing certificate | Override the signing certificate |
| Apps to close | List of processes that should be closed before installation. Used by the "Only if there are apps to close" option in Script Templates. |
| Installer customization | Override install and uninstall commands — either modify the parameters or replace the entire PowerShell command |
| Registry values | Set registry values during installation (HKLM, HKCU, HKCR, HKU) |
| Files | Include files to be deployed to the device (user profile or machine locations) |
| Script accessory files | Include auxiliary files (e.g. licence keys, configuration files) that are available during installation but not copied to the device |
| PowerShell script commands | Add custom PowerShell commands that run during installation. Robopack provides custom variables and supports both PSADT v3 and v4 commands. |
| Dependency control | Optionally disable dependencies being included for an app |
Detection methods
Robopack supports multiple detection methods for Intune:
- File-based — detect by file path and version
- Registry-based — detect by registry key and value
- MSI product code — detect by MSI product code
- PowerShell script — use a custom PowerShell script for detection. Scripts are automatically signed when uploaded to Intune using the same certificate as the installation script.
App documentation
After testing, Robopack generates documentation including:
- Tested install command
- Tested uninstall command
- Detection method (file, registry, or MSI)
- Install and uninstall logs from the VM
- Leftover files report
Related
- Tutorial: Deploying Custom Apps
- Script Templates — customise the PSADT templates used for packaging