DynamicPacks ONE-ACTION

Solution # DynamicPacks
ONE-ACTION

Collect Desired Information and Maintain Systems Health

Notable
Features

Collect Desired Information from Targets

Using DynamicPacks ONE-ACTION, you can collect the desired information from the targets managed by the Run Points. A Run Point contains a Dynamic Pack that you would like to execute against selected Targets. For example, you can create a Run Point that includes "Get GPO Info" Dynamic Pack to collect GPO information from Windows Client Computers. Similarly, you can create a Run Point that collects Active Directory GPO, Forest, Domain Controller Information from Active Directory Forests.

Report on "Any" Configuration Changes

DynamicPacks ONE-ACTION provides the ability to report on configuration changes for targets. For example, you can have DynamicPacks ONE-ACTION send you an email if Active Directory configuration changes (for example, when Domain Controller configuration changes occur). Similarly, you can configure DynamicPacks ONE-ACTION to report on Hyper-V configuration changes. Depending on the availability of Dynamic Packs, you can have DynamicPacks ONE-ACTION report on Configuration changes. Currently, DynamicPacks ONE-ACTION ships with Active Directory Dynamic Packs. You can design your own Dynamic Pack and include in the DynamicPacks ONE-ACTION.

Run Point is Backbone of
DynamicPacks ONE-ACTION

What is a Run Point?

A Run Point is an execution point which contains a Dynamic Pack and Target Instances. For example, a Run Point can contain "Get FSMO Roles" Dynamic Pack and ABC.Com and XYZ.Com AD Domains as Target Instances. Similarly, a Run Point created to collect GPO information from Windows Client computers can contain list of computers as Target Instances. One Run Point can include only one Dynamic Pack, but you can create multiple Run Points for a Dynamic Pack. For example, you can create RunPointA to contain same Dynamic Pack (Get Client GPO Dynamic Pack), but different Target Instances (list of computers).

Creating a Run Point

Creating a Run Point

Execute Run Points from Execution Window

Once you have created a Run Point, you can execute Run Point by navigating to Execution Window. All you need to do is provide a list of Required Target Instances depending on the Dynamic Pack configured in the Run Point. For example, if Run Point includes a Dynamic Pack that requires list of Domain Controllers, you will need to provide required Target Instances in the Step 2 as shown in the screenshot below. You can collect required Target Instances automatically by clicking "Get Instances for Target" button.

Executing a Run Point from Execution Window

Executing a Run Point from Execution Window

Run Point Supports Health Sets

Once you have created a Run Point, you can then create a Health Set for the Run Point. A Health Set contains the data that you would like to compare with Run Point data. For example, you create a Run Point to collect Domain Controller Configuration, next you create a Health Set. Once you execute the Run Point via DynamicPacks ONE-ACTION Execution Window or Run Point Scheduler, DynamicPacks ONE-ACTION will compare Run Point Data with Health Set Data. If data doesn't match (in other words Domain Controller configuration does not match), you will be notified via email. You can also see the differences in Data Window.

Scheduling

Get Notified of Configuration Changes

DynamicPacks ONE-ACTION ships with a powerful Run Point Scheduler that you can use to schedule Run Points and get notified via email. When scheduling a Run Point, you can set desired criteria. For example, you can schedule a Run Point and receive email notification with Run Point report only if configuration changes occur. DynamicPacks ONE-ACTION supports defining following attributes for criteria:

-Notify via Email if Run Point Data does not match with Health Set Data
-Notify via Email upon completion of Run Point
-Do Nothing

Reporting

Data View, TreeView, and HTML View

DynamicPacks ONE-ACTION can show you run point data in three different formats; CSV, Treeview and HTML. In Data View, you can easily find any configuration changes that might have occurred. HTML View provides you the overall status of Run Point and also show the differences. HTML View is sent you via email if any configuration changes occur in the Target managed by the Run Point.

Run Points

Create Multiple Run Points

A Run Point is an execution point. A Run Point contains a Dynamic Pack and Target Instances. An example of a Run Point: You can create a Run Point which contains Get Active Directory Domain FSMO Dynamic Pack to check FSMO role holders in each domain. Similarly, you can create a Run Point to check Group Policy Status on client computers by including Get GPO Status Dynamic Pack. Once Run Point has been created, you can create a Health Set for Run Point. A Health Set will contain the data that you would like to compare with Run Point data.

Creating Run Point

Creating Run Point

It's only fair to share...Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInShare on Reddit