Group Policy Best Practice
I always thought you consolidate GPOs to improve logon performance.
I was watching a CBTNuggets video where the instructor recommends creating a separate GPO for each purpose.
Which is best?
I was watching a CBTNuggets video where the instructor recommends creating a separate GPO for each purpose.
Which is best?
Comments
-
Hyper-Me
Banned Posts: 2,059
Some consolidation is not a bad thing. You can improve performance in other ways as well, like turning off the "other side" of a GPO. If its a computer GPO, turn off the user side, and vice versa.
I think the main point in seperating your GPOs is so that if you need to make a configuration change later, you can easily identify the GPO that contains the setting instead of editing one fat GPO.
An example i can give you is that at work I use a GPO called "studentworkstationdefault" that contains all the generic settings we use on ALL student computers. But i also add standalone GPOs like "softupdates" which installs adobe reader, flash, and java. I edit the softupdates frequently, and might need to repeal it all together at some point, so i dont want it tied into the other one.