AD question here: For our computers on our network, especially our XP machines,
the "Applying Computer Settings" portion of the boot process takes a very long
time (4 minutes?) which makes the initial login for our users a little painful.
I am curious if I have something setup in a way that is n
I have about 120 GPOs applying at logon, and it doesn't take anywhere near
that long. Keeping them separate and distinct is better when it comes to
working out which one is screwing things up, believe me.
Are all your DCs local to the problem PCs? Are you getting any other network
issues?
On 9 Ju
Be sure to disable computer/use settings on GPOs that have no settings in those
sections, so the won't be scanned and time will be saved.
As for merging I wouldn't recommend it. I'd just spend the time to recreate so
you'll have a fresh GPO. Then delete the older GPOs and allow the system t
The few times I've had to deal with this the problem turned out to be
connectivity-related instead of the number of GPOs.
Can you ping all of your DCs from the workstations? Has it always been this
way, or did something change? Is it all of the workstations all of the
time, some of them all of t
On Wed, Jun 9, 2010 at 1:53 AM, Matthew W. Ross
wrote:
> AD question here: For our computers on our network, especially our XP
> machines, the
> "Applying Computer Settings" portion of the boot process takes a very long
> time
> (4 minutes?) which makes the initial login for our users a little p
Is the load time slow on all of them? I had this happening on one
machine in our office. Ended up being a bad DNS setting. Went from
minutes to seconds to logon.
On Jun 9, 2010, at 1:53 AM, Matthew W. Ross wrote:
AD question here: For our computers on our network, especially our
XP mach
