Chat now with support
Chat with Support

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

Introduction

The GPOADmin PowerShell commands are installed during a complete or custom installation. (Asssuming that you have Windows PowerShell currently installed.)

The GPOADmin provider and commands allow you to perform virtually all available functionality through a command line.

For detailed examples on using the commands, see Using the GPOADmin PowerShell commands (Examples).

Before you can use the commands, you must register them on the system where GPOADmin is installed.

Import-Module -Name <GPOADmin Install Directory>\GPOADmin.psd1.
Once the GPOADmin provider is loaded, it creates two default drives called "VCRoot" and "PSRoot".

Connect to the Version Control Root of GPOADmin on this computer as the current user

New-PSDrive -Name "VCRoot" -PSProvider PSGPOADmin -Root "Version Control Root"

Connect to the Protected Settings Root of GPOADmin on this computer as the current user

Connect to the Version Control Root of GPOADmin on this computer as a different user (a dialog appears prompting for the user password)

Connect to the Protected Settings Root of GPOADmin on this computer as a different user (a dialog appears prompting for the user password)

Connect to the Version Control Root of GPOADmin on a different computer using the default port number as the current user

New-PSDrive -Name "VCRoot" -PSProvider PSGPOADmin -Root "Version Control Root" -Server“server.domain.com”

Connect to the Protected Settings Root of GPOADmin on a different computer using the default port number as the current user

New-PSDrive -Name "PSRoot" -PSProvider PSGPOADmin -Root "Protected Settings Root" –DriveType PSROOT -Server“server.domain.com”

Connect to the Version Control Root of GPOADmin on a different computer using the default port number as a different user (a dialog appears prompting for the user password)

New-PSDrive -Name "VCRoot" -PSProvider PSGPOADmin -Root "Version Control Root" -Server “server.domain.com” -Credential “domain\user”

Connect to the Protected Settings Root of GPOADmin on a different computer using the default port number as a different user (a dialog appears prompting for the user password)

Connect to the Version Control Root of a GPOADmin server on a different computer using a custom port number of 40201 as the current user

New-PSDrive -Name "VCRoot" -PSProvider PSGPOADmin -Root "Version Control Root" -Server “server.domain.com” -Port 40201

Connect to the Protected Settings l Root of a GPOADmin server on a different computer using a custom port number of 40201 as the current user

New-PSDrive -Name "VCRoot" -PSProvider PSGPOADmin -Root "Protected Settings Root" -Server “server.domain.com” -Port 40201

Connect to the Version Control Root of a GPOADmin server on a different computer using a custom port number of 40201 as a different user (a dialog appears prompting for the user password)

New-PSDrive -Name "VCRoot" -PSProvider PSGPOADmin -Root "Version Control Root" -Server “server.domain.com” -Port 40201 -Credential “domain\user”

Connect to the Protected Settings Root of a GPOADmin server on a different computer using a custom port number of 40201 as a different user (a dialog appears prompting for the user password)

New-PSDrive -Name "VCRoot" -PSProvider PSGPOADmin -Root "Protected Settings Root" -Server “server.domain.com” -Port 40201 -Credential “domain\user”

GPOADmin scripts

GPOADmin installs the following PowerShell scripts to c:\Program Files\Quest\GPOADmin\Scripts:

Grants the specified service account Edit settings, Delete, and Modify Security privileges and assigns ownership to all the GPOs in the specified domain.

Runs a specified GPOADmin dynamic report and emails the results to a list of recipients.

Available commands

The following section lists all available GPOADmin commands. To see examples on how to use some of these commands, see Using the GPOADmin PowerShell commands (Examples) .

NOTE:  

 

Add

Clear

Copy

Get

 

 

Get

New

Push

Remove

Reset

Select

Set

Set

Switch

GPOADmin PowerShell provider extensions

GPOADmin has extended the following standard PowerShell commands:

GPOADmin has extended Microsoft’s New-Item and Remove-Item PowerShell commands to add the ability to create and delete items from the GPOADmin version control.

Example: Create a container name HR

new-item -Path VCRoot:\ -Name HR -ItemType Container

Example: Create a GPO name HR_GPO in the HR container

new-item -Path VCRoot:\HR -Name HR_GPO -ItemType GPO -Comment "Set the minimum password length to 8 characters"

Example: Remove the GPO name HR_GPO in the HR container

remove-item -Path vcroot:\HR\HR_GPO

Example: Remove a container name HR

remove-item -Path VCRoot:\HR

The GPOADmin PowerShell provider has extended the Get-ChildItem and the New-PSDrive command to include the following parameters:

Table 20. Commands

Get-ChildItem extensions

New-PSDrive extensions

New-Item

Remove-Item

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating