November 2007
Intermediate to advanced
688 pages
15h 40m
English
Perhaps the most daunting task when working with GPOs is determining what GPOs should be used and which ones are best left alone. Generally speaking, GPOs should be created only when there is a specific need that can be addressed by a GPO. This is to say, the GPO should be driven by a company decision rather than being implemented because it looks useful.
Some companies fall into the trap of flipping through every possible GPO setting and deciding yes or no on each setting. This is a bad idea and will generally cause more issues than it will fix. The better approach is to ask yourself, “What have I always wished I could ...
Read now
Unlock full access