Table of Contents
Advertisement
About the execution of Managed Software Delivery
policies
When a Managed Software Delivery policy runs on a managed computer, it
performs a series of tasks that are grouped into the following phases:
Compliance
See
Table
6-2.
Remediation
See
Table
6-3.
When you schedule a Managed Software Delivery policy, you can assign different
schedules for compliance and remediation. For example, you can schedule the
compliance status to be reported during the day and the remediation to occur
only during a maintenance window.
See
"About policy applicability, compliance, and remediation"
The ability to separate compliance and remediation also allows for the offline
execution of Managed Software Delivery policies. When the compliance check
determines that a remediation is required, the policy downloads the appropriate
package. Remediation can occur even if the client computer is not connected to
the server because the client computer already has the package that it needs.
See
"About deferring the execution of software remediation"
Process for the compliance phase of Managed Software Delivery
Table 6-2
Step
Action
Step 1
Policy execution
Step 2
Applicability check
Performing advanced software deliveries
About the execution of Managed Software Delivery policies
Description
Starts the policy s compliance process at the
scheduled time on the client computer.
(Windows only) Determines whether the client
computer has the correct environment for an
installation of the software. If the computer does
not have the correct environment, the policy
execution stops.
The applicability check runs for each software
resource in the Managed Software Delivery policy
that is associated with an applicability rule.
99
on page 102.
on page 124.
Advertisement
Table of Contents
