NOTE:You must have the appropriate user rights to perform these operations. Refer to Configure policies for user roles for more information.
Whenever you deploy a package, a policy or policy group to (or delete a policy from) a managed node, a deployment job is created. You can view all pending jobs by clicking on the job icon in the console tree. When a job has completed, it is deleted from the details pane.
NOTE:The deployment jobs help you to monitor the actions you have
requested. If a job remains in the details pane longer than you
expect, you should investigate the cause of the delay. If some
problem has prevented the execution of the deployment job, it will
be displayed in the details pane with an error status. Jobs
that are waiting show the status suspended. After correcting
the cause of the problem, you can restart the job by right-clicking
on the node and
selecting All Tasks
Restart all deployment jobs.
You can also restart a failed job without performing a prerequisite check on the target node. This feature allows you to force the deployment of components to managed nodes, even if one or more of the target nodes does not meet the standard requirements for a managed node.
If you create a job that deploys agent packages, you must provide the credentials of a user who has access to the node. Also, if you restart a failed or suspended job that deploys agent packages, you must provide the credentials again. You may also need to provide credentials to deploy other packages to nodes that have the DCE agent.
Related Topics: