Updating a Policy

Once a new revision of a software package has been released, existing policies will not be updated to the new revision.

How to update policies to a new package revision:

1. Select the desired package in the Software Library.

   All the policies for this package are now displayed in the Software Policies tab of the Detail window.

2. In the Detail window, select a policy and in the Tasks window, select Update Policy.

   All the available, higher revisions of the package are now displayed.

3. Select the desired revision.

   If there are packages with the same Replacement ID, the system also provides the revisions of these packages (see also Dependencies between Software Packages).

4. On the next page of the wizard, specify whether or not to update the installation parameters you set individually per policy instance... 
   • Keep installation parameters of policy instances
     The installation parameters you changed per policy instance are kept. This can mean the following:

     • If the previous revision has a changed installation parameter value (i.e., one that's different than the default value), the new revision will use that changed value.

     • If the previous revision has an unchanged installation parameter value (i.e., the default value), the new revision will use the default value of the revision to which you update the policy.

   • Reset installation parameters of policy instances
     The installation parameters you changed per policy instance are overwritten with the value from the policy. The value of the installation parameter will be the default value of the revision to which you update the policy (no matter what the value of the current revision installation parameter is).

   • Important: There is one limitation (no matter which option is selected above)—the new revision installation parameter can't take the default value of the revision from which the update is performed. If you want to use the default value of the installation parameter from one revision to the next, create the next revision with the same default value.

   • Before the end of the update policy process, the Change Installation Parameters window will display, where you can check the value that will be obtained for the installation parameter after the update. If needed, you can change the value in this step.

5. Depending on which changes the revision contains, choose...
   • Update is uncritical
     Policy instances already executed will not be updated. The package will not be reinstalled.
     Policy instances not yet executed will be updated. These instances use the new configuration for installation.
   • Update is critical
     Policy instances already executed must be updated in order for the package to be reinstalled.
     These instances use the new configuration for installation.
6. If you now wish to edit the new policy instances, choose the option Deactivate all Policy instances after updating.
7. On the next page of the wizard, specify the date and time from which the package is to be installed, and whether and how long the automatic installation may still be postponed by the end user.
   See also: Postponable Installations
8. On the next page of the wizard, decide whether for immediate installation the tasks Execute changes (FastInstall) and / or Wake up computer (WoL) are to be executed.
9. Close the dialog by clicking OK.

   DSM provides different options for updating instances to the current policy revision later on, if you haven't updated all of the revisions including the policy to the new revision yet.

   • The following tasks are available in the policy context:
     Update all policy instances
     Update all policy instances (only active policy instances)
     Update all policy instances (only inactive policy instances)
   • In the policy instance group context (e.g. compliant, the following task is available:
     Update all policy instances (only compliance status '<name>')
   • In the policy instance context, the following task is available:
     Update policy instance