Go Premium for a chance to win a PS4. Enter to Win


One large group policy vs many small group polices

Posted on 2010-09-15
Medium Priority
Last Modified: 2013-12-04
This is a question on best practices.  I want to know which works better for system speed, one or two large group policies or many, like over 10 smaller group polices that would be targeted to specific ou's and groups?

I am looking for overall login speed.  We are revising what we have and trying to decide which is better.  From an administration point of view it seems that the many smaller polices will make it clearer which policy we need to go into to adjust settings.  We are concerned that all the extra policies will increase login time.  We are looking to go from 2 large group polices to about 10 to 15 smaller ones.

Breaking out settings for particular systems like an SCCM policy, a network policy, a security policy.  Where all of these settings we in a default policy before.

I am looking for an explanation of why one way is better than the other.  Preferably with some industry documentation to back up the statement.

Question by:tdisalvo
LVL 22

Assisted Solution

by:Joseph Moody
Joseph Moody earned 300 total points
ID: 33685441
Smaller specific GPOs.
When you have a large GPO, it will contain many settings that every computer doesn't need. When you narrow down your policies to which machines specifically need which policies, the machines have less settings to process the first time (or anytime the policy changes).
So let us say that your large policy has 100 settings. Anytime you change just one setting in the policy, the version number increases by one. This means that your computers have to download the entire policy.
Now let us say that you have 10 policies with 10 different settings. If you change one setting in policy 1 but do not make changes in 2-10, only policy one has to be replied. This means that 90 settings are not checked again.
LVL 11

Assisted Solution

TheGorby earned 300 total points
ID: 33685468
While I don't have any documentation, I have experience doing the same thing. The company I'm with had 3 large policies (default domain, extra-restricted, un-restricted) when I started with them, which over time I have branched out into 19 separate policies. The benefit of this is that as you mentioned, you can target specific OU's and groups for specific settings. We haven't noticed (or had any complaints about) longer login times, my guess is that despite the number of GPOs, when a user doesn't have the Apply Group Policy permission to a GPO it skips right over it seemingly without any performance reduction. We did in fact test this ahead of time as we were worried about login times as well. Although there are 19 GPO's typically no more than 5 or 6 will apply to any one user, which should be easily handled at login
Overall I wouldn't say that one method is inherently better or more preferred than the other, it really depends on the type of settings or restrictions you need to apply to your users and computers. If you have a mostly equally standardized workstation environment, then a few GPOs may be all you need. If you have several departments with varying programs and needs (as I do) then a dozen or more GPO's can give you that flexibility you need.
LVL 11

Expert Comment

ID: 33685489
I like Jmoody10's point as well, you may actually impove login times
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

LVL 53

Accepted Solution

Will Szymkowski earned 1200 total points
ID: 33685510
There really is no "best practices" when it comes to defining and creating gpo's. This is all based on your own needs in your environment.

I personally find that breaking out the policy's are the best way to manage policy's as you can quickly link, or remove a link to a speific OU etc. This is also better for managing machines that need different policies applied to them. The only best practice you should be following is what you are putting in your default domain policy.

The default domain policy should only include authenticate policys, password policy and certificate policies. Other than that you basically create your structure based on your business needs.

When it comes to managing the performance it is very hard to measure. Take a look at this link as it will give very detailed information on Group Policy performance. This is a little bit of a read but has good information...

Hope this helps~!
LVL 57

Assisted Solution

by:Mike Kline
Mike Kline earned 200 total points
ID: 33685560
It really depends on what is set - no definite answer here
+1 to that link that Spec01 sent, that is from one of the top gurus in the GP world.
I personally like breaking them out a bit but more because they are self documenting that way (just easier for me...not because of perf)
LVL 22

Expert Comment

by:Joseph Moody
ID: 33685702
mkline71: "I personally like breaking them out a bit but more because they are self documenting that way (just easier for me...not because of perf)"
Completely Agree! So much easier to know exactly what a GPO name IE Settings does than a GPO named General Computer Settings.

Author Closing Comment

ID: 33687179
Thanks to all that replied.  Spec01 that article was exactly what I was looking for.  

Featured Post

WatchGuard Case Study: NCR

With business operations for thousands of customers largely depending on the internal systems they support, NCR can’t afford to waste time or money on security products that are anything less than exceptional. That’s why they chose WatchGuard.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Office 365 is a subscriptions based service which includes services like Exchange Online and Skype for business Online. These services integrate with Microsoft's online version of Active Directory called Azure Active Directory.
Transferring FSMO roles is done when an admin wants to split roles between certain Domain Controllers or the Domain Controller holding the Roles has been forcefully demoted using dcpromo / forceremoval
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

886 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question