Creating a Shop Policy

Creating a shop policy allows the end user - to whom a shop policy is assigned via user or computer - to select the relevant package to install via Software Shop.
Only after installation, a policy instance is derived from the shop policy.

The procedure for assigning a shop policy to a computer/user, an OU or a group is as follows:

1. Select an OU, group or computer/user in the Organization Tree.
2. Choose the Create Shop Policy task and then follow the wizard.
   If you assign the package to a group or a container, you must specify whether the assignment also applies to the user or the computer objects contained in the package (you cannot select both).
   

   As a result, a new shop policy will be created. This is visible in the context of the package, the OU or the group.
   Note the following:

   • The wizard asks for installation parameters that may exist for the assigned package and that may be changed when the package is assigned!
   • Certain properties of the shop policy can be changed as long as the shop policy is deactivated.
   • In order to create the policy instance,the user has to start the installation in the Software Shop first.
   • Changing the installation parameters for Software Sets later:
     In the context of shop policies for Software Sets you cannot display any component policies and therefore also no installation parameters.
     Instead, component shop policies can be displayed in the context of the component package in the Software Library.
     You can only change installation parameters there if the associated shop policy of the Software Set is deactivated. For this, the rollout of the Shop Policy has to be stopped for the Software Set! This is not possible for individual components.

   A Shop policy is equivalent to a standard policy with the instance creation mode On Demand.
   For further details on the required specifications, open the Assigning Software section.