Chat now with support
Chat mit Support

GPOADmin 5.19 - Quick Start Guide

Best practices

Best practices

The following best practices exist within GPOADmin:

•
Deploying Cloaked GPOs
Before you deploy a GPO, ensure that it is not cloaked. If you deploy a cloaked GPO, and then later deploy it uncloaked, it will be flagged as non-compliant.
•
Forest Configuration
It is recommended that users who are members of the Enterprise Administrators group configure the forest for version control.
•
Client Installation
Users should be a local administrator on the computer where the client is installed.
•
Remote Forest Management
Although remote forest version control management options are available, it is recommended to manage a forest logged in as a user from the same forest to eliminate any additional trust and security-related considerations.
•
Storage Repository Placement
If using AD LDS or SQL as storage options it is recommended that they are located in the same forest that is being managed to eliminate any additional trust and security-related considerations. It is recommended that AD LDS is used as the configuration store, and a network share as the backup store.
•
Register/Unregister Actions
It is recommended that users who are members of the Enterprise Administrators group perform the register and unregister actions on GPOs within the Version Control system.
•
Naming Conventions
When creating GPOs within the Version Control system, it is possible to enter names that have already been used. However, it is highly recommended to use unique names. You enable the option to use unique names in the Server Properties Options tab.
•
Action Comments
Use descriptive comments to help others easily identify the reasons for performing actions within the Version Control system.
•
Deploying Changes
Ensure each object has the desired settings before approving and deploying any pending modification actions. Once the modification has been approved and deployed, the changes will be applied to the live object. 
•
GPO  Settings - Versions
When running in a mixed mode environment, newer GPO settings are not backwards compatible with older versions of GPMC. For example:
Preferences introduced in Windows Server 2008 are not backwards compatible.
•
Watcher Service
It is recommended that only one GPOADmin Watcher Service be installed per configuration store.
It is recommended that you not install the Watcher Service on a domain controller.
•
Migration Utility
A configuration utility is available that allows you to migrate the configuration store to SQL from an AD/ AD LDS. Before migrating the configuration store, Quest suggests that you test the migration to ensure that all objects migrate according to your specifications. To validate the migration, run the command with the /t option. This gathers all the information that will be committed to the SQL database but does not commit any changes.
•
Configuration Store Selection
The best practice is to use AD LDS as the configuration store. However, in large environments, SQL server is the recommended option. Quest uses the following criteria to define large environments:
•
Domains with more than 500 registered objects that run searches on a regular basis.
•
More than 500 registered containers.
•
Containers with objects nested more than 3 levels deep.
These are guidelines and should not be considered as an exhaustive list.
 
 
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen