Default operational rule settings

Automatic general operational rule reassignment after device reinstall

This column defines if the general operational rules are to be automatically reassigned after a client was reinstalled. By default this value is No, indicating the rules will not be automatically reassigned.

Limit Operational Rule Dependencies

This parameter defines if dependencies are taken into account when assigning an operational rule to a group. Possible values are Yes and No, the default value is No. Yes indicates that if an operational rule has a dependency on another rule that is NOT assigned to the this group, the dependency is ignored and the operational rules will be executed in the order defined but without the missing rule. If you select No for the same case as the preceding one, you either must also assign the missing rule to the respective group or remove the dependency from the current rule.

Wake Up Switched Off Devices

This parameter defines if by default devices that are switched off when an operational rule is assigned to a device or device group are to be woken up via the WOL option when the assignment is sent. By default this option is deactivated.

Upload intermediary status values for operational rules

This option activates the choice to upload all status values, that an operational rule execution (general as well as software distribution) runs through or only to upload the final status values. By default this option is activated, that is, all status values are uploaded. Contrary to all other packages, the ConfigFiles.cst package does not use this parameter.

Automatic software distribution rule reassignment after device reinstall

This value specifies if the software distribution rules are to be automatically reassigned after a client was reinstalled. By default this value is No, indicating the rules will not be automatically reassigned.

Status Modification Window

This parameter defines if the modification of an operational rule, that is, when a step was added or removed, etc., is to impact the operational rule status of all assigned devices. By default this option is deactivated, that is, no status will be modified.

Modify the operational rule schedule when importing a CSV file

This parameter specifies if for devices that are imported to a device group to which operational rules are assigned a specific schedule for these operational rules can be defined. By default this value is deactivated. If set to Yes, a pop-up menu will provide the possibility to modify the existing operational rule schedule.

Automatic dependency activation of published operational rules

This parameter enables/disables the automatic execution of dependencies of advertised rules (for both user and device). If the parameter is enabled, no pop-up displays and dependencies are automatically assigned (if necessary) to the device when a rule is selected via MyApps. Else, a pop-up displays that the dependency check has failed and the operation rule thus could not be executed.However a reduced dependency management is still done even with this option disabled. It is possible only if all dependencies are present on the device, else the Verification Failed status will appear.

Take chronological dependencies into account after device reinstall

Defines if the chronological dependencies of operational rules are taken into account and followed during resynchronization after a device reinstall. By default this option is activated. Deactivating this option makes the rule synchronization faster, however, this might lead to inconveniences or even problems on the devices if some rules which are dependent on each need to be executed in the specified order for proper functioning.

Remove relations with devices created by MyApps

After an optional rule is unassigned from a user assignment, the user can no longer activate it via MyApps . If this option is activated, all devices are automatically unassigned if the link between the user the rule is removed. By default this option is not activated.

Automatic creation of the operational rule when a package is published

For a package to be distributable and installable a corresponding operational rule must exist that defines the operations to execute during the package installation. This parameter defines if this rule is automatically created when a package is published. The value is applicable to all types of packages. By default this option is not activated, that is, the rule is not created.

Automatic reassignment of all general operational rules if the local database is corrupted

This parameter defines if all general operational rules are to be automatically reassigned after the recreation of a corrupted local database. By default this value is No, indicating the rules will not be automatically reassigned.

Automatic reassignment of all software distribution rules if the local database is corrupted

This parameter defines if all general software distribution rules are to be automatically reassigned after the recreation of a corrupted local database. By default this value is No, indicating the rules will not be automatically reassigned.

Take chronological dependencies into account at the first device installation

Defines if the chronological dependencies of operational rules are taken into account after the first installation of a device. This option is useful if your environment relies heavily on device provisioning. After the new devices have uploaded their identity for the first time, all their assignments are already in place and will be activated directly.