Overview
A software package is the foundation of any deployment in Zecurit. It contains the application installer along with all the configuration needed to install it correctly on target endpoints, silently and automatically.
Packages are stored in the Software Repository, which acts as a central library of all applications available for deployment. Once created, a package can be reused across multiple deployment policies.
Navigation: Go to Manage → Deployment → Software Repository → Software Packages tab, then click Add Package.
Section 1: Package Details
This section captures the basic identity and source of your installer.
Package Name (Required) Enter a clear, descriptive name to identify this package in the repository. This name appears in the Software Packages list and is referenced when selecting a package in a Deployment Policy. Example: Microsoft Office 365, Google Chrome 120, Zoom Client
Installer Type Select the format of your installer file.
- MSI : Windows Installer format. Recommended for enterprise deployments. Supports Transform files and standard MSI arguments.
- EXE : Executable installer format. Use this for applications distributed as .exe files.
Source Type Choose where Zecurit should retrieve the installer file from:
- Upload : Upload the installer directly from your local device. Supported archive formats (.zip, .tar, .gz, .bz2, .z) are automatically extracted after upload. This is the simplest option for smaller packages.
- Network Share : Point to an installer file stored on a shared network location. The Zecurit agent accesses the file using the credentials you provide. Recommended for large enterprise deployments to avoid repeated uploads.
- Hosted URL : Provide a direct download URL where the installer is hosted. The agent downloads the file at the time of deployment.
Section 2: Installer Info
This section defines exactly how Zecurit runs the installer on target devices.
Installer File Path (Required) The relative path to the main installer file within your uploaded package or network share. Example: app.msi, setup/install.msi
Transform File Path (.mst) (Optional) For MSI installers, specify a custom Transform (.mst) file to modify the installation behavior, such as setting default language, features, or configuration options. Example: app-transform.mst
Install Arguments (Optional) Pass additional command-line properties to the installer to control its behavior during installation. Example: REBOOT=ReallySuppress, /quiet /norestart
Uninstall Command (Optional) Specify the command to silently remove the application when a deployment policy set to “Uninstall” is triggered. Example: msiexec /x {GUID} /quiet
Working Directory (Optional) Set the directory from which the installer process should be executed. Use this when the installer requires a specific working path to locate supporting files. Example: C:\Temp
Timeout (secs) Set the maximum time (in seconds) Zecurit should wait for the installation to complete. If the installer does not finish within this window, the deployment is marked as failed.
💡 Tip: For large applications, set a generous timeout to avoid false failures caused by slow installations.
Section 3: Pre Install Check
Pre-install checks allow Zecurit to verify that target devices meet specific conditions before attempting installation. This helps prevent failed deployments and avoids duplicate installs.
You can configure one or more of the following checks:
| Check Type | What It Does |
|---|---|
| File / Folder Check | Verifies that a specific file or folder exists (or does not exist) on the device before installing |
| Registry Key Check | Validates the presence or absence of a registry key or value |
| Service Running Check | Confirms that a required service is running before installation begins |
| Disk Space Check | Ensures the device has sufficient free disk space to complete the installation |
| Software Already Installed | Detects if the application is already installed and skips deployment to avoid duplicates |
If a pre-install check fails, the deployment is skipped for that device and the result is recorded in the deployment report.
Section 4: Pre/Post Configuration
This section allows you to run additional automation steps before and after the main installation.
Pre-Install Configuration Actions that run before the installer executes:
- Run Script — Execute a script from the Scripts Repository to prepare the device (e.g., stop a conflicting service, create a directory, set a registry value).
- Terminate Process — Automatically close a running application that could interfere with installation (e.g., close Chrome before installing an update).
- Uninstall Existing Software — Remove a previous or conflicting version of the software before installing the new one.
Post-Install Configuration Actions that run after the installer completes successfully:
- Run Script — Execute a cleanup or configuration script after installation (e.g., apply license keys, configure default settings).
- Terminate Process — Stop any processes launched by the installer that are no longer needed.
- Uninstall Software — Remove a companion or temporary application that was only required during installation.
Section 5: Advanced Settings
Advanced Settings allow you to store metadata about the software for asset tracking, license management, and reporting purposes.
| Field | Description |
|---|---|
| Name of the Software | The display name shown to users and in reports (e.g., Microsoft Office 365) |
| Version Number | The version of the software being deployed (e.g., 16.0.1) |
| Software Vendor Name | The name of the software publisher (e.g., Microsoft Corporation) |
| License Type | Select whether the software is Commercial or Free |
| Software Category | Categorize the software (e.g., Productivity, Security, Developer Tools) |
💡 Tip: Completing these fields improves the accuracy of your software inventory, license compliance reports, and audit records.
Saving the Package
Once all required fields are completed, click Save to add the package to your Software Repository. It will immediately appear in the Software Packages list and can be selected when creating a Deployment Policy.
Click Cancel to discard your changes and return to the Software Packages list without saving.