Reboot And Chained State; State Description - Novell ZENWORKS PATCH MANAGEMENT 6.4 SP2 User Manual

W W D
ORKING ITH EPLOYMENTS

Reboot and Chained State

The reboot and chained states are the result of a device not performing the required reboot
following a deployment.
Table 4-1: Reboot and Chained State
Reboot State
Chained State
There are two deployments which will always perform a reboot:
Table 4-2: Reboot Deployments
Reboot System Package
Task - System Reboot
Standard packages reboot for one of three reasons.
• The deployed package required and forced the reboot (unless suppressed), during the
installation.
• The package installer determined that it required a reboot.
• The reboot flag was sent to the agent. It is not necessary that the agent receive the Reboot
System Package or Task, the agent will perform the reboot on its own.
State
Deployment
Indicates that the device received a standard deployment
requiring a reboot, yet the reboot was suppressed. While in
this state, the agent will only accept a deployment. A reboot
deployment or a manual reboot will clear this state.
Indicates that the agent received a chained deployment in
which the reboot was suppressed. While in the chained state,
the agent will only accept another chained deployment or a
reboot deployment.
A system task that is automatically added to the end of
chained deployments where the final reboot is not
suppressed. Also sent to agents when you click the Reboot
Now button on the Endpoints page.
A task which permits the user to schedule a reboot using the
scheduling features of the Schedule Deployment Wizard.
- 74 -
Description
Description