In most environments Run MA is the most heavily used schedule step.
Run MA invokes a run profile on MIM waits for the MA to complete and (typically) records data for objects modified by the steps in that run.
Run MA saves MA Run History objects in Identity Panel for each step in the profile. It is generally recommended to use exclusively single-step run profiles as this gives better flexibility and clarity when filtering and charting run-history results.
There are two global settings that impact the functionality of Run MA Steps.
- Skip Exports checkbox in MS Sync Connection: If this is selected the Run MA will automatically be skipped if one of the steps in the profile is an export step.
- If Disable History is checked in the schedule settings MA runs will happen, but object data collection will be completely omitted. Instead a Run history record will be saved with the normal statistics counters, but the run profile name with have " – No Scan" appended and there will be no data updates for Time Traveler.
The major settings for the step are in the strip header. Before these items can be selected an initial load scan must have been performed to populate the MA settings dropdown lists. After new MAs or run profiles are added, the changes will be picked up by either a catchup full-scan or by any MA run scan.
Environment – Which sync environment to connect to
MA – MA name to run
Run Profile – Run profile name to run
Detailed settings include things like preferred server, condition rules, etc. Because it is typical to have many MA run steps with the same detailed settings it is fastest configure the details on one strip, then use the duplicate button to make multiple copies.
IMPORTANT: When you change to a different MA from the dropdown after duplicating a step you must also select the run-profile. Even if the run profile names are the same it is necessary to re-select the run profile name from the dropdown.
Skip CS/MV Scan – The skip scan checkbox allows you to disable data collection for a single run-step. This feature is only intended for use in environments that are pushing the boundaries of SLA performance requirements as it significantly degrades resolution of Identity Panel change history. Objects skipped in this manner will not be captured until a subsequent run scan or a catchup full scan.
Reference Count Threshold – When synchronizing group membership using MIM or Azure ADConnect, if you find that a disproportionate portion of the data collection time following the completion of a run profile is consumed by a few large groups that change on every run (e.g. All Employees), you will benefit from setting a Reference Count Threshold. You set the Reference Count Threshold with a Scheduler run step. Setting a non-zero Reference Count Threshold will cause Identity Panel to skip data collection on any object (like a group) with more multi-attribute references (i.e. members) than the number specified in the threshold. The benefit of setting this value is obvious: shorter scan times. Collection of these large groups memberships should be set aside, and performed once periodically, like once a day, using a schedule step that doesn't have the threshold, or by a daily full scan.
Condition and Skip Rule – Use the Sync Step Condition functions section of the rule helper to see functions for probing threshold values for MA runs.
Please sign in to leave a comment.