Custom Apps

Deploy your own Windows installers. Upload an MSI, EXE or ZIP, tell Pckgr how to install, uninstall and detect it, and it deploys like any catalog app.

WindowsOwners and Admins upload installers and set commands; MSP Technicians assign and deploy them; Read Only and MSP Read Only can view

In short

  • Works for line-of-business apps, licensed software and anything else the catalog does not carry.
  • The upload goes straight from your browser to Pckgr's storage, up to 1.9 GB, while you fill in the rest of the form.
  • Pckgr wraps your installer so it gets the same deferral, close-apps, progress and restart options as catalog apps. No change on devices is needed.
  • Detection rules decide whether the app is installed: an MSI product code, a file, a registry value, or your own PowerShell script.
  • A new version is a new upload. Devices with the old version update when your detection rule says they do not have the new one.

Add a custom app

  1. Go to Apps and click Upload Installer.

    The button is shown to Owners and Admins. Technicians can assign and deploy the app once it exists.
  2. Drop the installer on the page, or click to choose it.

    An .msi or .exe, or a .zip when the installer needs other files beside it (a setup with its data files, or a script that drives it). The upload starts at once and keeps going while you continue.
  3. Program: name the app and give its commands.

    For an MSI, Pckgr fills the name, publisher, version and product code from the file; you only add extra properties if the installer needs them. For an EXE, enter its silent switches and an uninstall command; for a ZIP, the install and uninstall commands (see below).
  4. Detection: say how the agent can tell the app is installed.

    An MSI starts with a product code rule. Other installers start with a file rule; change it to whatever the installer leaves behind. See Detection rules.
  5. Review and click Create App.

    Pckgr wraps the installer into a deployment package. The app page shows Preparing for a moment, then Ready. Then assign it to a group as you would any app.

Deployment options come afterwards

Deferrals, closing apps before install, the progress dialog, restart prompts and pre/post scripts are set on the app page under Advanced Deployment Settings, exactly as for catalog apps.

Install and uninstall commands

Commands run on the device as SYSTEM (or as the signed-in user when you choose the User context) from the folder Pckgr unpacks the package into, with no window anyone can see. They must therefore be silent.

In the User context the commands have only the user's rights. An installer or uninstaller that asks for elevation shows a UAC prompt on the user's screen; the deployment waits for the answer and fails if it is declined, or after an hour if nobody answers. Pick the User context only for apps that install and remove themselves without administrator rights.

MSI
Pckgr runs msiexec with its silent switches and REBOOT=ReallySuppress. Enter only extra properties or switches, such as ALLUSERS=1 or a licence key property. Uninstall uses the product code, so it works even after the installer file is gone from the device.
EXE
Enter the installer's silent switches, such as /S or /VERYSILENT /NORESTART; Pckgr starts the uploaded file with them. The uninstall command is a full command line: the app's own uninstaller by path, for example "%ProgramFiles%\App\unins000.exe" /VERYSILENT, or the uploaded installer with its uninstall switch, for example setup.exe /uninstall /quiet. Pckgr waits for the uninstaller and for anything it starts before it checks that the app is gone, so an uninstaller that hands the work to a copy of itself (NSIS ones do) still counts as finished only when the app is.
ZIP
Both commands name a file inside the ZIP (bin\setup.exe /S) or a full path on the device, with its arguments. The file can be an .exe, .msi, .ps1, .cmd or .bat; scripts run in 64-bit Windows PowerShell with the execution policy bypassed.

Common silent switches

Installer typeInstall switchesUninstall command
Inno Setup/VERYSILENT /NORESTART /SUPPRESSMSGBOXES"%ProgramFiles%\App\unins000.exe" /VERYSILENT
NSIS (Nullsoft)/S"%ProgramFiles%\App\uninstall.exe" /S
InstallShield/s /v"/qn"setup.exe /s /x /v"/qn" (the uploaded installer)
Wrapped MSI / Burn bundle/quiet /norestartsetup.exe /uninstall /quiet (the uploaded installer)

Pckgr warns when an install command has no switch it recognises as silent. Without one the installer opens a window in a session nobody can see, and the deployment fails after an hour.

Exit codes

0 and 1707 mean success; 3010 and 1641 mean success with a restart pending (the device is not restarted; Windows Update or the user does that). Anything else fails the deployment with the installer's own code, which you will find in the deployment's logs.

Detection rules

The agent runs the detection rules before every install (an app that is already there is left alone and the job succeeds without downloading anything) and after it (an install that leaves no trace fails). Every rule must pass for the app to count as installed.

MSI product code
Windows Installer lists the product code, in either the 64-bit or 32-bit view, or for the signed-in user. Optionally require the version to compare with a value, for example greater than or equal to 2.5.
File or folder
The path exists, does not exist, or the file's version compares with a value. Paths may start with a variable such as %ProgramFiles% or %ProgramFiles(x86)%.
Registry
A key exists, a value exists, or a value compares as a string, a version or a whole number. Choose the 32-bit view for 32-bit apps on 64-bit Windows (Pckgr reads WOW6432Node for you). HKCU is the signed-in user's hive only for apps in the User context.
PowerShell script
Your own script, which must be the only rule. Exit code 0 means installed. It runs in Constrained Language Mode on devices that enforce AppLocker or WDAC, so keep to cmdlets and operators.

Make detection version-aware if you want updates to roll out

When you upload a new version, Pckgr creates update jobs for the devices your Install and Update Only assignments reach. On each device the agent runs the new detection rules first, and only installs when they fail. A rule such as "file version greater than or equal to 2.0" or an MSI rule with a version does that; "file exists" sees the old version as installed and leaves it.

The app page

A custom app's page has everything a catalog app's has, plus a Package card:

Ready
The package exists and the app can be assigned.
Preparing / Wrapping
Pckgr is building the package. For a first upload the app cannot be assigned yet; for a new version or changed commands, devices keep the current package until the new one is ready.
Failed
The card says why (an empty ZIP, a ZIP that unpacks past 1.9 GB or holds more than 50,000 files, an installer that was never uploaded, a command that names a file the package does not have). Fix the cause and click Try again, or upload the installer again.
Upload new version
A new installer of the same kind. Give it a version so the Self-Service Portal and update history show it.
Edit commands / Edit arguments
Changing a command rebuilds the package; what is already installed on devices is not touched.
Edit detection
Takes effect at each device’s next check-in, within about five minutes. No rebuild.
Versions
Every installer uploaded for this app, with who uploaded it and whether it is the current one. Older and failed versions still count towards the tenant’s storage; delete them here with the trash icon when they are no longer needed.

To change the app's name or publisher, click Edit details at the top of its page. Names are unique in a tenant whatever their capitalisation, so a name another app has is refused as already in use; the publisher is optional. A new name needs no rebuild: devices show it in notifications from their next deployment of the app. A new publisher rebuilds the package, because it is part of the deploy script; devices keep the current package until the new one is ready, and nothing already installed is touched. Assignments stay as they are.

Good to know

  • Windows only. macOS apps come from the catalog.
  • An installer can be up to 1.9 GB, the most an agent downloads. A ZIP must also unpack to no more than 1.9 GB and hold at most 50,000 files. A tenant can hold 20 GB of uploads by default; ask support to raise that.
  • Custom apps are not carried by templates yet; add them in each tenant.
  • A custom app has no auto-update: only you publish new versions of it.
  • Deleting the app removes its uploads from storage within about an hour.
  • Pckgr verifies the package's SHA-256 on every device before it runs, and checks that an upload is used only by the tenant that made it.
  • Catalog packages carry Pckgr-signed scripts; the deploy script Pckgr generates for your installer is not signed. Devices that allow PowerShell scripts by publisher signature only cannot run custom apps; the path rules for the agent's folders in Hardened Environments are enough.