<div>
This settings will ensure that logon is not possible until startup policies are applied. &nbsp;Usually this is not enabled and thus policies run asynchronously,
</div>


This settings will ensure that logon is not possible until startup policies are applied.  Usually this is not enabled and thus policies run asynchronously,

<div>
What OS is the server and what functionality is the domain? It could also be waiting for DNS to get loaded from Active Directory if it is integrated.
</div>


What OS is the server and what functionality is the domain? It could also be waiting for DNS to get loaded from Active Directory if it is integrated.

<div>
The OS w2k8 R2 SP1. &nbsp;The functionality is Windows 2008 R2 at Forest and domain, with ADDNS. &nbsp;I think that is exactly what is happening, waiting for DNS. Sounds like I need to disable that GPO
</div>


The OS w2k8 R2 SP1.  The functionality is Windows 2008 R2 at Forest and domain, with ADDNS.  I think that is exactly what is happening, waiting for DNS. Sounds like I need to disable that GPO

<div>
Disabling the GPO resolved the problem
</div>


<div>
<div class="content wysiwyg-content">
I am cleaning up an Active Directory Domain for someone. &nbsp;One of their complaints centers around the fact that when the domain controllers on the Forest\Domain (it is a flat design) are rebooted they take an extremely long period of time to boot up and replicate with each other. &nbsp;GPO processing is especially acute.<br />
<br />
I noticed they applied the GPO setting 'Always wait for the Network at computer startup and logon' in the Domain Controllers Policy. &nbsp;I have never applied this at the DC level. &nbsp;It seems this would be the cause of the issue but I would like to get a second opinion before I disable it?<br />
<br />
Thanks
</div>
</div>


I am cleaning up an Active Directory Domain for someone.  One of their complaints centers around the fact that when the domain controllers on the Forest\Domain (it is a flat design) are rebooted they take an extremely long period of time to boot up and replicate with each other.  GPO processing is especially acute.

I noticed they applied the GPO setting 'Always wait for the Network at computer startup and logon' in the Domain Controllers Policy.  I have never applied this at the DC level.  It seems this would be the cause of the issue but I would like to get a second opinion before I disable it?

Thanks

Can this GPO setting applied to DC's cause very slow startup

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.