サポートと今すぐチャット
サポートとのチャット

GPOADmin 5.17 - 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)
Creating a custom container hierarchy Selecting security, levels of approval, and notification options Viewing the differences between objects Copying/pasting objects Proposing the creation of controlled objects Merging GPOs Restoring an object to a previous version Restoring links to a previous version Managing your links with search and replace Linking GPOs to multiple Scopes of Management Managing compliance issues automatically with remediation rules Validating GPOs Managing GPO revisions with lineage Setting when users can modify objects Working with registered objects Working with available objects Working with checked out objects Working with objects pending approval and deployment
Checking compliance Editing objects Synchronizing GPOs Exporting and importing
Creating Reports Appendix: Windows PowerShell Commands Appendix: GPOADmin Event Log Appendix: GPOADmin Backup and Recovery Procedures Appendix: Customizing your workflow Appendix: GPOADmin Silent Installation Commands Appendix: Configuring Gmail for Notifications Appendix: Registering GPOADmin for Office 365 Exchange Online Appendix: GPOADmin with SQL Replication About Us

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:

The properties are defined as follows:

Each action also contains the following nodes:

The nodes are defined as follows:

Predefined Tags

Tags are typically replaced with their corresponding values by the service. However, there are cases where the tags will not be converted. For example, if a comment is not specified during the version control action then the [COMMENT] tag will be empty; or if the object is not checked out then the [TRUSTEENAME] and [TRUSTEESID] will be empty.

Keep in mind that in some cases the tags will always be empty as is the case of a pre-action for the Register version control action. At the time the pre-action is processed, the corresponding version control information would not exist.

Parameters and conditions support the following predefined tags:

The possible values of a registered object's sub status include the following:

None

Default.

Register

Registers objects with the version control system.

Unregister

Unregisters objects from the version control system.

CheckIn

Save edits made to an object in the version control system.

CheckOut

Prepares an object in the version control system for editing.

UndoCheckOut

Discards change made to an object in the version control system.

RollBack

Restores an object in the version control system to a previous known state.

Restore

Restores an object in the version control system to a previous known state.

Get

 

Overwrites the current settings of an object in the version control system with settings from a previous known sate.

Import

 

Overwrites the current settings of an object in the version control system with settings from a previous backup.

IncorporateLive

 

Overwrites the current settings of an object in the version control system with those from the live environment.

Create

Creates a new object in the version control system.

Branch

Branch on object.

Edit

Edits an object in the version control system.

Delete

Marks an object in the version control system as deleted.

Approve

Approves changes made to an object in the version control system.

Reject

Rejects changes made to an object in the version control system.

RequestApproval

Request approval for changes made to an object in the version control system.

ApplyPolicyTemplate

Applies a template to a policy in the version control system.

Label

Labels objects in the version control system.

Lock

Locks an object in the version control system.

Unlock

Unlocks an object in the version control system.

Cloak

Cloaks an object in the version control system.

Uncloak

Uncloaks an object in the version control system.

EnableWorkflow

Forces the object to follow version control workflow.

DisableWorkflow

Allows the object to not follow version control workflow.

Move

Moves an object from one container to another in the version control system.

WithdrawApproval

Withdraws approval of changes for an object in the version control system.

WithdrawApprovalRequest

Withdraws an approval request for changes to an object in the version control system.

Rename

Renames an object in the version control system.

SubmitScheduledApproval

Submits approval for scheduled deployment of an object in the version control system.

CancelScheduledApproval

Cancels a scheduled deployment of an object in the version control system.

Deploy

Deploys an object in the version control system to the live environment.

Link

Links a policy object to a scope of management in the version control system.

LinkUpdate

Updates the links on a scope of management.

ComplianceAction

An action which affects the compliance of an object in the version control system.

ModifySecurity

Modifies the security of an object in the version control system.

UnauthorizedModifications

A backup of a noncompliant object. This is intended to be done by the Watcher Service.

MigrationAction

Indicates an import from NetPro GPOADmin. This is intended to be done by the Migration Wizard.

Synchronization

Synchronizes a source object to one or more targets of the same type.

ToggleApprovalWorkflow

Toggles the order of approval workflow processing.

FailedDeployment

A deployment has failed.

The possible values of a version controlled object’s status include the following:

Conditions

Whether or not an action is processed can be controlled by the use of conditions. A condition must evaluate to true in order for the action to be processed. If the condition evaluates to false then a log entry stating such is created and the current custom workflow action is not processed.

Each condition node has the following properties:

The type of operations available depends on the DataType property.

The following DataTypes are available:

The following operations are available for a String DataType:

The following operations are available for a Guid DataType:

The following operations are available for a Version DataType:

The available logical operators include:

The logical operators ‘And’ and ‘Or’ function sequentially and grouping is not supported. For example:

would be processed as:

not as:

To use a logical “And” or “Or” operator, specify a new Condition with only the Operator property.

For example:

Example of a complete pre-action

The following example demonstrates a pre-action that creates a CheckIn directory below the GPOSettingsReports directory provided that the name of the version controlled object contains an underscore and the version is less than 4.5 or the comment ends with “_AMER”.

関連ドキュメント
Showing 1 to 4 of 4 rows

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択