You should configure the agent update settings before attempting to use it. Following are the settings that you can configure:
Deployment stages are optional; however, stages allow you to deploy an update one step at a time, such as to a test group first, then to your managed devices.
The global default timeout setting is 3 days. This provides the same timeout length for each stage. For information about setting the timeout for individual stages, see Modifying the Stage Timeout.
Set this value to be long enough to accommodate updating all of the devices you plan to update.
When the timeout value is reached, the stage’s deployment stops. You can cancel the deployment, or you can clear the error to restart the stage and reset the timeout, or, you can ignore all pending devices to trigger a stage progression (either automatic, or wait for administrator action based on the setting).
To configure global stage timeout settings:
In Endpoint Management Console, click Configuration in the left pane.
On the Configuration tab, expand the Management Zone Settings panel (if necessary), click Infrastructure Management, then click Agent Update Settings to display the Stage Timeout Settings panel.
Select the Stage Timeout check box, then specify the days, hours, and minutes desired.
Click Apply to make the changes effective.
Either click OK to close the page, or continue with another configuration task.
If you did not click Apply to make your changes effective, clicking OK does so. Clicking Cancel also closes the page, but loses your unapplied changes.
Some updates do not require a device to be rebooted after they have been deployed to a device. However, if a reboot is required to complete the update process, the deployment is not completed until the device is rebooted.
To configure the reboot behavior:
In Endpoint Management Console, click Configuration in the left pane.
On the Configuration tab, expand the Management Zone Settings panel (if necessary), click Infrastructure Management, then click Agent Update Settings to display the Reboot Behavior panel:
Select one of the following options:
Prompt User to Reboot When Update Finishes Applying: After the update has been applied, a request to reboot is immediately displayed. If the user initially rejects rebooting, the user is periodically requested to reboot the device, until the device is rebooted.
Reboot the device when no user is logged in: Select this option to reboot the device even if no user has logged into the system.
Reboot the device when it is locked: Select this option to reboot the device if the device is locked. Prompt will not be displayed before rebooting the device.
Do Not Reboot Device: The device does not reboot; however, the user is periodically requested to reboot the device, until the device is rebooted.
Start Endpoint Agent with limited functionality: Select this option to start Endpoint Management services incase reboot is supressed while deploying the update to the device. It is not applicable for Primary Servers.
Force Device to Reboot: After the update has been applied, the device is automatically rebooted without user intervention if a reboot is required by the update.
Click Apply to make the changes effective.
Either click OK to close the page, or continue with another configuration task.
If you did not click Apply to make some of your changes effective, clicking OK does so. Clicking Cancel also closes the page, but loses your unapplied changes.