Packages
A package describes a piece of software the agents can install or uninstall. Tenant admins create packages; technicians and viewers can see them and technicians can deploy them.
Global packages from Entrosity (marked Shared by the global admins) appear read-only next to your own and can be deployed like them.
Create a package
Under Packages → New package, pick a kind:
| Kind | What you provide | Notes |
|---|---|---|
| MSI | The .msi file | Product code and version are read from the file and used for detection and uninstall. Installed with msiexec /i … /qn /norestart. |
| EXE | The setup program and its install arguments (the silent switch, e.g. /S) | Add uninstall arguments if the vendor has them. The command line is passed as you type it. |
| Winget | A winget ID, found by searching the catalog (e.g. "7-Zip") | Nothing is uploaded; devices install from winget. Optional version and source (winget or msstore). |
| PowerShell | A .ps1 file or a pasted script | Runs with -ExecutionPolicy Bypass as SYSTEM (or the user). |
Uploaded files go straight from your browser to object storage. The
server then checks the size and SHA-256 you declared, reads the MSI
metadata, and marks the package ready. Until then it is a draft
and cannot be deployed (package_not_ready). A ready package's file
cannot be replaced: create a new package for a new version.
Common settings
| Setting | Meaning |
|---|---|
| Name, publisher, version, description | Shown in the library and in deployments. |
| Architecture | The CPU architecture the package is for. |
| Success exit codes | Default 0, 3010, 1641. 3010 and 1641 mean "succeeded, reboot required". |
| Timeout | 1 minute to 24 hours. |
| Run as | System (default), or the logged-on user for per-user software. With nobody signed in, the job fails with no_logged_on_user. |
| Requires reboot | The package always needs a restart afterwards. |
Detection rules
A detection rule tells the agent whether the software is present:
- before installing: if it passes, the device is marked Already installed (skipped) and nothing runs;
- after installing: if it fails, the install is reported as failed
(
detection_failed); - after uninstalling: it must fail.
| Rule | Checks |
|---|---|
| MSI product code | The product code is installed. |
| Registry | A key exists, or a value compares (==, !=, >=, >, <=, <) with an expected value. HKLM or HKCU, in both registry views. |
| File | A file exists, optionally with at least a minimum file version. Environment variables are expanded. |
| Winget | The winget package is installed. |
Winget on devices without winget
Devices without winget install App Installer from files the server hosts
(ops upload them once; see Configuration → winget).
Without them, winget packages fail on such devices with winget_missing.
Deleting a package
Packages are soft-deleted: finished deployments keep showing them. A
package used by a deployment that has not finished cannot be deleted
(package_in_use). The file is removed after 7 days by default.