Once you have configured a Scope Action object, it is ready to be executed. You must run a scope action at least once for data to be generated or actions to be taken. You can also schedule a scope action to execute periodically. Scope Actions use a push technology that gives you results immediately.
Select the Scope Action object to be executed.
Right-click on the mouse and select Run from the menu.
If you have previously executed a scope action and need to run it again, use the down arrow below the Run button in the Ribbon Bar to access additional options:
| Run - Erase previously generated report data and re-run the scope action on the full scope. |
Run As - Erase previously generated report data and re-run the scope action on the full scope using a different set of credentials (see Executing a Scope Action using Alternate Credentials below). | |
Re-Run Failed Objects Only - Preserve already generated report data and re-run the scope action only on the objects which failed during the last execution. If new report data is generated, it is merged with the existing data set. This mode is useful if you configure a scope action to execute tasks (like installing an MSI package) and not all machines were successfully processed during the last execution. | |
Re-Run Merge Data - Re-run the scope action on the full scope and merge the resulting report data with the existing one.
This mode is useful to generate an asset management data set. Create a scope action which reports on the required information, schedule it to execute periodically using this mode of operation.
|
Select an action from the Scope Action view.
Right click on the mouse and select Run As.
When prompted, enter the desired credentials to run the scope action and click on OK.
Specifying Domain Account Credentials | Specifying Local Account Credentials |
To specify domain account credentials, enter the UNC user account name and password. |
If the scope action targets computer objects and you need to use a local account as alternate credentials, set the Authority field to '.' (single period, no quotes), and enter the local account name and password in the respective fields: |
The Scope Action execution window initially opens in Ready Mode as shown in the figure below.
Scope Action Information:
Displays the scope action's name, description, the scope and the report output file path.
Execution Speed
This slider controls the speed at which the scope action will execute. It represents the actual number of simultaneous active nodes. An active node is a target object currently being processed by the scope action.
HIGHER execution speed will result in a HIGHER consumption of available network bandwidth.
LOWER execution speed will result in a LOWER consumption of available network bandwidth.
For more information, see Understanding Execution Speed and Resources Used.
Note: You can modify the execution speed at any time during the execution of the scope action.
Click on the Start button to begin executing the scope action. This triggers the Execution window to expand and display execution information. While the scope action is running, you can Pause / Resume or Abort the execution at any time. Aborting the execution simply completes the scope action with the already processed nodes and abandons all remaining nodes.
Execution Status - The execution of a scope action contains multiple phases. The current phase is reported above the progress bar. For example, the figure above shows the phrase "Processing nodes...". The animated icon in the upper left corner also changes depending on the phase being executed.
The Progress Bar displays the global status of the execution. The percent completed is displayed at the bottom right corner of the progress bar.
Active, Processed and Remaining Nodes which are displayed under the progress bar, are the number of active, processed and remaining nodes.
Active Nodes - The active nodes are the nodes currently being processed by the scope action. The actual names of these nodes are displayed. The number of active nodes is dependent on the execution speed.
A higher execution speed means a larger number of simultaneous active nodes, as well as higher network bandwidth usage. You can modify the execution speed at any time during the execution of the scope action.
Console Window - The console window displays real time information, warnings and errors during the execution of the scope action. Observe this window to detect potential problems with specific nodes. This is particularly useful during a pilot test.
Note: The contents of the Console window is automatically saved once the execution of the scope action has been completely executed. The contents of the Console window are saved under the configured log output directory.
During the execution of a scope action, an execution icon is displayed in the tray area of Windows. You can use the tray icon to view the progress and status of the execution or to minimize / maximize the execution window to and from the tray.
Place the mouse cursor over the execution icon to view the current status of the execution.
Right click on the mouse over the execution icon to show or hide the execution window. You can also double click on the icon to toggle the show/hide functions. Making the execution window visible will allow you to control its execution (pause, abort, etc.).
Once the execution is completed or aborted, the execution window displays a new set of controls which allow you to view the output report and the output log. Click on the View Report button to see the output report or click on the View Log button to see the problems encountered during the execution. If the scope action was configured to automatically generate output report and close after execution, it will be done in this completion phase.
Note: The data generated by this execution can be viewed from the main Scope Action view. You do not need to keep the execution window opened. See: Viewing the results of a scope action.
