Deployment Schedules
Key features
- The Deployment Schedule will deploy a new version of a given application based on the Deployment Schedule configuration assigned to a given application when updated. This allows users to deploy a new version utilizing a phased roll-out.
- Each Deployment Schedule has a name, a number of phases and a trigger.
- A phase has a name, an Assignment Profile that will be assigned to the application when the phase becomes active, an offset in days and a requirement script. The requirement script allows to only install/patch the new version on devices that have the application installed already.
- The defined offset for the initial phase is derived from the trigger, the offset for the remaining phases is based off of the initial phase.
- If the requirement script radio button is toggled on, then the phase will affect only the users/devices where the requirement.ps1 script returns 1.
- The trigger for a deployment schedule will decide when and how a deployment schedule is initiated, there are 3 options:
- When a new version is uploaded: the Deployment Schedule will start whenever a newer version of that application is uploaded.
- Weekly: the Deployment Schedule will start every week on the day specified. This allows you to deploy all new application versions starting on a given day of the week.
- Monthly: the deployment schedule will start every month in a specified week day of one of the first 4 weeks at 00:00. E.g. (first Monday of the month or third Wednesday of the month).
- When creating a new deployment schedule, the name and the Assignment Profile for each existing phase is required.
- An application can have only 1 deployment schedule at any given time.
- An application has to be deployed or else you can not assign a deployment schedule to it.
- You can not have a deployment schedule with less than 1 phase.
- You can not have a deployment schedule with more than 28 phases.
- The number of phases depends on the offset and on the trigger option, those 2 above are the minimum and maximum limits.
- If the trigger is set on Weekly, the maximum number of phases can not exceed 7. This is to ensure patch capability when new updates are made more than once a week.
