Chat now with support
Chat with Support

GPOADmin 5.13.5 - User Guide

Introducing Quest GPOADmin Configuring GPOADmin Using GPOADmin
Connecting to the Version Control system Navigating the GPOADmin console Search folders Accessing the GPMC extension Configuring user preferences Working with the live environment Working with controlled objects (version control root) Checking compliance Editing objects Synchronizing GPOs Exporting and importing
Creating Reports Working with the GPOADmin Dashboard Appendix: Windows PowerShell Commands Appendix: GPOADmin Event Log Appendix: GPOADmin Backup and Recovery Procedures Appendix: Customizing your workflow Appendix: GPOADmin Silent Installation Commands About Us

What is a custom workflow action?

You can extend GPOADmin’s version control system to incorporate customized actions based on your organizations existing workflow. This allows you to customize and control the deployment of controlled objects (such as GPOS, SOMs, and WMI filters) to meet your individual needs. For example, you can configure a pre-action to send the help desk distribution list an email each time a GPO change is requested.

Also, if you have a workflow tool in place that encompasses many different organizational tools you no longer need to use the workflow in both applications. With pre and post actions, a GPO check out, modification, and request for approval can be configured to create a ticket in an existing workflow system. Subsequent approval in the external workflow system can be configured to approve and deploy that same policy in GPOADmin. A post action can be configured to add additional ticket information about the deployment of the GPO into the customers external workflow application.

Custom actions are available on the following Version Control actions:

Approve

A change to a version controlled object is approved.

CancelScheduledApproval

A version controlled object’s scheduled deployment has been canceled.

CheckIn

A version controlled object is checked in.

CheckOut

A version controlled object is checked out.

Cloak

A version controlled object has been cloaked.

ComplianceAction

Either a “Rollback” or “IncoporateLive“ compliance action is performed.

Create

A version controlled object has been created.

Delete

A version controlled object has been deleted.

Deploy

A version controlled object has been deployed into the live environment.

DisableWorkflow

A version controlled object has been workflow disabled.

Edit

A version controlled object has been modified.

EnableWorkflow

A version controlled object has been workflow enabled.

Label

A label has been applied to one or more version controlled objects.

Lock

A version controlled object has been locked.

ModifySecurity

The security has been modified on a version controlled object.

Move

A version controlled object is moved.

Register

An object is registered with the version control system.

Reject

A change to a version controlled object is rejected.

Rename

A version controlled object is renamed.

RequestApproval

An approval for a version controlled object is requested.

Restore

A version controlled object has been restored.

SubmitScheduledApproval

A version controlled object has been scheduled for deployment.

Synchronization

A version controlled Group Policy Object has been synchronized with another Group Policy Object.

ToggleApprovalWorkflow

Toggles a version controlled object between workflow enabled and disabled.

Uncloak

A version controlled object has been uncloaked.

UndoCheckOut

A version controlled object’s checkout is undone.

Unlock

A version controlled object has been unlocked.

Unregister

A version controlled object is unregistered.

WithdrawApproval

An approval on a version controlled object is withdrawn.

WithdrawApprovalRequest

A request for approval has been withdrawn.

Working with custom workflow actions in the Version Control system

GPOADmin provides an easy to use editor to help you set up and configure your custom actions.

Each custom workflow action has two phases; pre-actions (processed prior to the version control action being executed), and post-actions (processed after the version control action has been executed).

Whether or not an action is processed can be controlled by the use of conditions. This must be set through the editing the xml file directly. For details see, Conditions .

GPOADmin includes a sample custom workflow to get you started that shows how to incorporate the creation of Help desk ticket with each approval request generated from the Version Control system.

2
Select Options | General | Enable the processing of custom workflow actions, and select Launch Editor.
4
Select the Request approval | Pre-Action to view the sample.
2
Select Options | General | Enable the processing of custom workflow actions, and select Launch Editor.
5
If desired, select the Stop on error option. This will instruct the service to stop all processing for the current object when an error occurs.
7
8
If required, select the Post-Actions tab and configure its options.
9
Click Add.
11
When you are ready to deploy the workflow, select Enable the processing of custom workflow actions.
2
Select Options | General | Enable the processing of custom workflow actions, and select Launch Editor.
2
Select Options | General | Enable the processing of custom workflow actions, and select Launch Editor.

Working with the custom workflow actions xml file

Custom workflow actions are defined in an XML file (CustomWorkflowActions.xml) which must be located in the same directory as the GPOADmin Service executable.

Actions

For a list of available actions, see What is a custom workflow action? . Custom workflow actions are defined in the CustomWorkflowActions.xml file as follows:

The PreActions and PostActions are defined as follows:

Each phase may contain one or more actions with the following properties:

Table 19. Properties

Name

Identifies the action.

Comment

Describes the action.

StopOnErrors

Instructs the service to stop all processing for the current object when an error occurs.

The properties are defined as follows:

Each action also contains the following nodes:

Table 20. Nodes

Executable

The full path to the executable.

Parameters

The list of parameters to pass to the executable.

Conditions

A list of conditions which determine whether or not to process the action.

The nodes are defined as follows:

Related Documents