<div>
You can also enable field engineering logging <a href="http://support.microsoft.com/kb/314980" rel="ugc">http://support.microsoft.com/kb/314980</a>&nbsp; to log expensive and inefficient searches<br />
<br />
I'm with thia, you probably don't need another. &nbsp;The main reason for two DCs in any size domain (even 10 users). &nbsp;Is for fault tolerance/uptime.<br />
<br />
You only have one DC and that goes down hard and you have downtime/problems for users. &nbsp;You have at least two and one goes down and the users shouldn't even notice.<br />
<br />
Thanks<br />
<br />
Mike<br />

</div>


You can also enable field engineering logging http://support.microsoft.com/kb/314980 [http://support.microsoft.com/kb/314980]  to log expensive and inefficient searches

I'm with thia, you probably don't need another.  The main reason for two DCs in any size domain (even 10 users).  Is for fault tolerance/uptime.

You only have one DC and that goes down hard and you have downtime/problems for users.  You have at least two and one goes down and the users shouldn't even notice.

Thanks

Mike


<div>
<div class="content wysiwyg-content">
We currently have around 160 users with 2 domain controllers at a site. We have some monitoring software running and it is showing over 60 LDAP connections to the each server. I am going to add another domain controller to the site but I was wondering what the correct ratio of domain controllers to users is. We are going to implement some network intensive applications so I'm assuming the LDAP connections will only get higher after that.
</div>
</div>


We currently have around 160 users with 2 domain controllers at a site. We have some monitoring software running and it is showing over 60 LDAP connections to the each server. I am going to add another domain controller to the site but I was wondering what the correct ratio of domain controllers to users is. We are going to implement some network intensive applications so I'm assuming the LDAP connections will only get higher after that.

What is the optimal domain controller to users ratio for a site using Windows Server 2008 R2?

Project management is the discipline of carefully projecting or planning, organizing, motivating and controlling resources to achieve specific goals and meet specific success criteria. A project is a temporary endeavor designed to produce a unique product, service or result with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables) undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value.

Project Management

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.