Space banner

   

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Managing object assignment preferences

In the Object Assignment tab, you can set defaults for the assignment and unassignment of the BMC Client Management objects and a the default operational rule schedule. You can manage the following object assignment preferences:

Device Assignments and Unassignments

Actions such as assigning or unassigning require activation to make them valid. This frame defines the setting for the type of activation.

Parameter

Description

Activation Type

Enables setting the activation for assigning, for example, a device group. The options include:

  • Prompt: Activations will be accompanied by a message box requesting that the user confirms activation should go ahead using the default schedule.
  • Automatic: This type enables full automation. No user interaction is required. You cannot advertise packages with this type of assignment activated.
  • Manual: The user fully controls the activation.

The default activation type is Prompt

Operational Rules

The elements in this box allow the administrator to manage the schedule for operational rules.

Parameter

Description

Default Schedule

Defines the default schedule for the execution of the Operational Rules . If you do not define your own default schedule, the following schedule is set as the default: Immediate execution, stop after one execution.

Assignment Date

The option boxes in this panel allow you to change the default assignment from immediate to a specific time.

Warning Threshold

This parameter defines the maximum number of targets, devices or users, that can be assigned without warning. If the threshold is reached or passed a confirmation window appears on the screen and you need to confirm the assignment or you can cancel it. This value is applicable in the same way when reassigning or activating an operatinal rule or publishing it to the targets. The default threshold is set to 1000 targets. To deactivate this function enter 0 (zero). This value is also applicable to device and user groups. If the member count of all assigned groups is higher than the defined threshold, the message window also appears. This warning is used to make you aware, that you are executing a large number of assignments which might impact the performance of your systems. It allows you to cancel the assignment and possibly defer it to a less critical time.

  

Modifying the default schedule

  1. Click Modify next to Default Schedule in the Operational Rules panel.
    The Scheduler window appears.
  2. Make the desired changes to the schedule.
  3. Select one of the following options for the question When do you want this rule to be run on devices? to define when the actual execution is to be launched:

    • Right now Select this option to start the execution immediately.
    • At Startup Select this option if the operational rule is to be executed every time the device is started.
    • At Session Startup Select this option if the operational rule is to be executed every time the agent is started
    • At Session Close Select this option if the operational rule is to be executed every time a session is closed.
    • Run repeatedly on a schedule Check this option if if the execution is to be scheduled repeatedly.
    • Use Cronspec to Schedule Select this option if the execution schedule is to be created via a cronspec.

    Depending on the choice you make in this list box, additional options become available.

  4. (Optional) If you selected the Run repeatedly on a schedule option fill in the boxes that appear to create the execution schedule:
    1. Select if the schedule is to run every day, week or month.

      Notes

      • Be aware, that the weekly option is not available for agents of version 11.5.0 or earlier. If in your target groups there are agents of these versions, the final status is always Sending impossible .
      • If you already used previous versions of CM , be aware that it is not possible any longer to define a schedule that executes on the nth day of the month.
    2. If you select the weekly schedule you also need to select on which days of the week the schedule is to run by clicking the respective days represented by their initials in the table that appears. You can select more than one weekday.
    3. If you selected a monthly schedule you also need to select in which week of the month by selecting the respective number and on which days of the week the schedule is to run by clicking the respective days represented by their initials in the table that appears. You can select more than one week and one weekday.
    4. Select the Once daily radio button to only execute the object once per day. Then, in the list box next to it specify the time at which it is to be run.
    5. Select the Multiple times radio button to execute the object more than once per day. Then, in the boxes that appear below, specify the frequency and the unit for the frequency. Check the between box if in addition these multiple times are to occur within a specific timeframe and define the start and end time of this interval in the list boxes that appear.
  5. (Optional) If you selected the Use Cronspec to Schedule option fill in the values that appeared for the cronspec definition:

    • Minute Enter the minute value, it can vary from 0-59.
    • Hour Enter the hour value, it can vary from 0-23
    • Day Enter the day value, it can vary from 1-31.
    • Month Enter the month value, it can vary from 1-12 (1 is January)
    • Week Day Enter the week day value, it can vary from 0-6 (0 is Sunday).
    • Weeks of the Month Enter the weeks of the month value, it can vary from 1-5.

      Note

      Each set of ranges can be preceded by a % sign which changes the meaning from an absolute to a relative number. For instance if minutes equals 29 the timer fires each time the absolute time ends with a number of minutes equal to 29 (for example, 11:29) whereas %20 means every 20 minutes every hour, that is, at 13:00, 13:20, 13:40, 14:00, and so on.

      • Ranges are comma-separated lists. A range is made of a number eventually followed by a '-' sign and another number
      • The wildcard character asterisks (*) can be used to indicate any value.
  6. (Optional) If the schedule is not to start immediately you need to select its starting time from the Do you want to configure a window in which this rule can run? box.
    • Prevent this object from running on a schedule Select this option if you want to disable a schedule.
    • Start the schedule immediately Select this option if you want to start the schedule immediately.
    • Start the schedule at next startup Select this option if you want to activate the schedule only after the next startup of the device.
    • Start the schedule window on Select this option if you want to start the schedule at a specific date and time.
  7. (Optional) If you selected the Start the schedule window on option you now need to select the date and time at which the schedule is to start in the boxes that appear.
  8. (Optional) Select after how many executions the schedule is to stop. To have it run without any limits select the option Unlimited from the list box.
  9. (Optional) If the execution is to stop at a specific date and time check the End on box and select the desired values from the list boxes next to it.
  10. Click OK to confirm the modifications.
    The default schedule is modified.

User Assignments

This section defines the default settings for assignments with users and user groups as targets.

Parameter

Description

Assign to Primary and Secondary Users (only primary if not selected)

Check this box if the assignments are applicable to the secondary users and the primary user. If not selected the assignments will only be carried out for the primary user. This option is only applicable if the Deploy to devices linked to users option is selected during assingment.

Operational Rule Assignment Policy

Select from this list the type of policy to use for the user assignments:

  • Assign at User Login : the assignment of the operational rules is carried out when the user logs on to a device.
  • Assign at User Logout : the assignment is carried out when the user logs off.
  • Assign Immediately : the assignment is carried out immediately after defining the assignment.
  • Assign with Default Assignment Date : the assignment is carried out according to the defined default schedule. This option is only applicable if the Deploy to devices linked to users option is selected during assignment.
Was this page helpful? Yes No Submitting... Thank you

Comments