- 04 Jan 2023
- 1 Minute to read
- Updated on 04 Jan 2023
- 1 Minute to read
Deployments are used to sequence a set of application installations during the imaging process of both virtual and physical devices. For more information about starting or enabling deployments, click here.
The details screen provides a few basic options to configure the Deployment.
|Name||The friendly name for the Deployment|
|Enabled||Determines if the Deployment is active|
|Description||A description for the Deployment|
The “Assignments” tab allows you to add Contexts, Devices, and Device Collections to the Deployment. You can do so by using the search bar, you can also remove or change the type of assignment in this tab. When you assign a Context, Device or Device Collection you can choose which stage of a package needs to be Assigned to the selected identity.
Filters allow you to define when a deployment is available for a device based on certain requirements. For example: only enable the deployment if a certain file is available on the device that the deployment is assigned to.
Filters are contained by Filter Sets, it is possible to use these sets in a OR or a AND clause, as can be seen below:
The “Packages” tab shows a list of Packages associated with the Deployment. In the List you can add, edit and remove Packages associated with the Deployment. The following columns are available.
|Name||The technical name for the Package|
|Action||The type of Action Sets that should be executed by the Deployment|
|Enabled||Whether or not the Package will be executed by the Deployment|
|Ignore errors||If this enabled the Deployment will not be aborted when encountering an error|
When creating or editing a package you are able to assign filters which determine whether or not a Package should be executed by the Deployment.
Please review the corresponding documentation for a full list of all the package filters.