Chat now with support
Chat mit Support

GPOADmin 5.18 - 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 the change window for specific actions 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

Working with report folders

Reports in GPOADmin mirror the contents of My GPOADmin Reports folder in the Documents folder.

* 
NOTE: Report Folders are only available in the GPOADmin console.
•
Managing report folders

Managing report folders

To create a folder
•
Right-click Reports or any subfolder, and select New | Folder.
To rename a folder
•
Right-click any subfolder under Reports, select Rename and enter the new name.
* 
NOTE: The name must be a valid Windows® folder and must not conflict with any other folder names of the same parent.
To delete a folder
•
Right-click any subfolder under Reports and select Delete.
To manage reports using Windows Explorer
1
Right-click Reports and select Open Folder in Explorer.
From here, you can manage your files in the typical manner.
2
Once you return to GPOADmin, right-click Reports, and select Refresh to ensure that your view is updated.

Appendix: Windows PowerShell Commands

•
Introduction
•
GPOADmin scripts
•
Available commands
•
Using the GPOADmin PowerShell commands (Examples)

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).

Registering the GPOADmin PowerShell commands

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

To register the GPOADmin commands
1
Open a PowerShell window and type the following in the command prompt:
import-module ‘C:\Program Files\Quest\GPOADmin\GPOADmin.psd1’
2
Type the following in the PowerShell command prompt to verify that the snap-in was added:
get-command -module GPOADmin
All registered PowerShell commands display.
Loading the PowerShell provider
To load the GPOADmin PowerShell provider
1
Open PowerShell and run the following command:
Import-Module -Name <GPOADmin Install Directory>\GPOADmin.psd1.
Once the GPOADmin provider is loaded, it creates two default drives called "VCRoot" and "PSRoot".
PSRoot is the virtual directory created when Protected Settings policies are enabled for the specified server. All Protected Settings policy management and workflow actions are performed from here.
2
To access the drive, enter the following command: CD VCRoot: or CD PSRoot:
* 
NOTE: You must include the colon.
If you are running only the GPOADmin client, you must create a PSDrive mapped to the version control root to use the available PowerShell capabilities.
We recommend that all commands be run from the created PSDrive.
* 
NOTE: The account used in the credentials parameter must have permission to connect to the specified GPOADmin server. Permission is granted by adding the user as either a GPOADmin user or administrator on the Access tab of the targeted GPOADmin Server Properties dialog.
 
 
Table 18. Connection options
Connection requirement
Command

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
New-PSDrive -Name "PSRoot" -PSProvider PSGPOADmin -Root "Protected Settings Root" –DriveType PSROOT

Connect to the Version Control Root of GPOADmin on this computer as a different user (a dialog appears prompting for the user password)
New-PSDrive -Name "VCRoot" -PSProvider PSGPOADmin -Root "Version Control Root" -Credential “domain\user”

Connect to the Protected Settings Root of GPOADmin on this computer as a different user (a dialog appears prompting for the user password)
New-PSDrive -Name "PSRoot" -PSProvider PSGPOADmin -Root "Protected Settings Root" –DriveType PSROOT -Credential “domain\user”

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)
New-PSDrive -Name "PSRoot" -PSProvider PSGPOADmin - Root "Protected Settings Root" –DriveType PSROOT -Server“server.domain.com” -Credential “domain\user”

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”

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen