Configure Custom App Settings
Custom App Settings let you define configuration for an app that is automatically applied to every version Robopack deploys. Instead of reconfiguring settings each time an update is released, you set them once and they carry forward.
This is useful for things like custom install arguments, registry values, licence files, closing conflicting applications, and running custom PowerShell commands during installation.
What you'll need
- Package Writer or Organisation Administrator permissions in Robopack
Step-by-Step Guide
1. Navigate to App Settings
In the left menu, click App Settings. You'll see a list of existing settings, or an empty page if you haven't created any yet.
2. Create a new app setting
Click Create App Setting and choose the app you want to configure. You can create settings for both Instant Apps and custom uploaded apps.
Give the setting a descriptive name (e.g. "Adobe Acrobat Reader DC").
3. Configure the basic options
| Setting | Description |
|---|---|
| Target version | Pin to a specific version, or leave blank to apply to all versions |
| Target architecture | Restrict to x64, x86, or allow any architecture |
| Target scope | Machine or User scope |
| Script template | Override the script template for this app, or select Inherit from organization default to use whichever template is set as the default |
| Signing certificate | Override the signing certificate used for this app's installation scripts |
Changing the script template for a deployment that is already in progress will not affect currently deployed packages — only future packages uploaded to tenants.
4. Set apps to close
The Apps to close setting defines which processes should be closed before installation begins. This works together with the "Only if there are apps to close" option in Script Templates — when that option is enabled, the welcome dialog only appears if the user has one of these processes running.
For example, for Adobe Acrobat Reader you might add AcroRd32 and Acrobat so that the installer can update files that would otherwise be locked.
5. Customise install commands
Under Installer customization, you can override the install and uninstall commands in two ways:
- Modify the parameters — add or replace the arguments passed to the installer
- Replace the entire command — write your own PowerShell command that runs the installer
For example, the default install command for Adobe Acrobat Reader might be:
Execute-Process -Path "$installerPath" -Parameters "-sfx_nu /sAll /rs /msi"
You could modify the parameters to add custom logging:
Execute-Process -Path "$installerPath" -Parameters "-sfx_nu /sAll /rs /msi /log `"$configToolkitLogDir\AdobeReader_Install.log`""
6. Add registry values
Click Registry values to add registry keys that are set during installation. You can target any of the standard hives:
HKEY_LOCAL_MACHINEHKEY_CURRENT_USERHKEY_CLASSES_ROOTHKEY_USERS
This is useful for things like disabling auto-update, setting licence keys, or configuring app defaults.
7. Add files
You can include files that are deployed to the device during installation:
| Location | Use case |
|---|---|
| User profile | Files that belong in the user's profile directory |
| Machine | Files that go to a system-wide location |
8. Add script accessory files
Script accessory files are included in the installation package but are not copied to the device. They're available to the installation script during execution — useful for licence files, configuration templates, or other files referenced by your install commands.
9. Add PowerShell script commands (optional)
For advanced scenarios, you can add custom PowerShell commands that run during installation. Robopack provides a range of custom variables you can use in your scripts.
Make sure your PowerShell commands match the PSADT version used by the script template. PSADT v3 and v4 use different commands.
10. Save and apply
Click Save. The settings will be applied to all future deployments of this app. If you have existing Robopatch flows for this app, you can sync the changes by clicking Sync app settings in the deployment.
Scope options
All Custom App Settings are per-app. Each setting can be applied to one or more tenants, overriding the global (organisation-wide) settings for those tenants.
| Scope | Effect |
|---|---|
| Global | Applies to all tenants in your organisation |
| Per-tenant | Applies to specific tenants, overriding the global setting for that app |
What's next?
- Custom Packaging feature overview
- Customise Script Templates — configure how dialogs and notifications work during installation
- Automating App Updates — Custom App Settings are applied automatically to every new version