Centralized Gpo Design

By Author: fiona
Total Articles: 191
Comment this article

With a centralized GPO approach mcitp 2008, the goal is to use very few GPOs (ideally only one) for any given user or computer. All of the policy settings required for a given site, domain, or OU should be implemented within a single GPO.
If the site, domain, or OU has groups of users or computers with different policy requirements, consider subdividing the container into OUs and applying separate GPOs to each OU rather than to the parent. A change to the centralized GPO design involves more administration than the decentralized approach because the settings might need to be changed in multiple GPOs, but logon time is shorter. This model is best suited for environments in which users and computers can be classified into a small number of OUs for policy assignment.
Group Policy Processing
As mentioned in earlier chapters, planning your OU structure is key to the efficient application of Group Policy, Every additional policy that you apply increases the number of settings that the individual computers must evaluate MCITP: Enterprise Administrator. ...
... Planning your organizational structure so that you can apply as few group policies as possible to only those containers that require them is a key to improving startup and logon performance, You might even decide to create OUs for the purpose of applying a specific Group Policy. For example, if you have several computer accounts that require a specific configuration that is unique to only those systems, you may find it more efficient to create a separate OU in order to handle that special configuration.

There are three parts to planning Group Policy: plan the Group Policy settings,plan GPOs, and plan administrative control of GPOs.Plan Group Policy settings sparingly—justify the selection of each setting as you would the creation of a domain or OU. Choose settings based on their ability to help you to simplify the administration of computers and users.
You can build GPOs by using a decentralized or a centralized design. A decentralized design uses a base GPO applied to the domain, which contains policy settings for as many users and computers in the domain as possible. Then this design uses additional GPOs tailored to the common requirements of each OU and
applied to the appropriate OUs. A centralized design uses a single certification exam papers containing all policy settings for the associated site, domain, or OU.