Novell ZENWORKS PATCH MANAGEMENT 6.4 SP2 - SERVER, User Manual

Page: 101 / 390

W
ORKING
W
ITH
D
EPLOYMENTS
- 85 -
Explaining Deployment Distribution Order
When deploying more than one package to an individual device or group of devices, the
deployments can be scheduled to process at different times.
NOTE
: Each device managed by ZENworks Patch Management Server requires an agent. A
deployment is associated to the agent installed on a particular device.
Order is also influenced by deployment type, status, and reboot requirements. Deployments
proceed in the following order prior to regularly schedule system tasks and agent processes:
1) Chained deployments
2) Standard deployments
3) System Task: Reboot
4) Task – Reboot System
5) Discover Applicable Updates (DAU)
Although no deployment occurs before its scheduled time, a chained deployment whose
time has elapsed will always precede a standard deployment whose time has also elapsed.
If multiple chained deployments are scheduled and some devices have the final reboot
suppressed, while others do not, the determination of a reboot override is based on the last
scheduled deployment.
Next Run Date Displays the date when the device is to perform the
deployment again, if the deployment is recurring.
Last Run Date Displays the status of the last time the device performed the
deployment.
Last Run Start Date Displays the date when the device last started the
deployment.
Last Run Completed Date Displays the date when the device last finished the
deployment.
Field Description