You may be able to find the culprit by running a gpresult and viewing the time 
taken for each of the components.  Also, the event log at 
Microsoft-Windows-GroupPolicy will reveal some of this information too.

Personally, I prefer to have multiple GPOs, each for a specific type of thing I 
am targeting.  So for instance, I will have a separate GP for setting up 
Printer, and a separate GP for setting up Folder Redirection, etc.

I don't believe there is a significant difference in speed between the two, but 
I would think that having all settings in a single GPO would be faster, 
although would be much harder to troubleshoot (which is one of the reasons I 
separate them).

-Aakash Shah

From: [email protected] [mailto:[email protected]] On 
Behalf Of Kelsey, John
Sent: Thursday, August 13, 2015 10:29 AM
To: [email protected]
Subject: [NTSysADM] Streamlining GPOs

We're seeing significant logon delays due to the high number of GPOs that have 
to get processed when a user logs in.  We're trying to clean up and reduce the 
number of things that have to happen in order to get the user logged on faster. 
 If we block all GPOs in our testing, we've been able to cut the logon time in 
half.  So either we just have too many GPOs or a couple of them for whatever 
reason is crushing the logon.


Is it more efficient to have 200 GPOs that set 1 item in each one?
OR
Is it more efficient to have 1 GPO that sets 200 items?
OR
Does it not make any difference in how long it takes to process?

Thanks all.

***************************************
John C. Kelsey
Penn Highlands DuBois
*:  814.375.3073
*  :   814.375.4005
*:   [email protected]<mailto:[email protected]>
***************************************
[PHH ESig Logo 150dpi]


This email and any attached files are sensitive in nature and intended solely 
for the intended recipient(s). If you are not the named recipient you should 
not read, distribute, copy or alter this email. Any views or opinions expressed 
in this email are those of the author and do not represent those of Penn 
Highlands Healthcare or its affiliates.. Warning: Although precautions have 
been taken to make sure no viruses are present in this email, the company 
cannot accept responsibility for any loss or damage that arise from the use of 
this email or attachments.

Reply via email to