Discussion Locked

PDC BDC Sizing

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Does anyone know a rough estimate of the number of simultaneous logons a pdc or bdc can handle? Lets assume both the pdc and BDC are PIII 500 with 256 MB RAM.
Also, what is the determining factor of which will do the authenticating?

7 replies

by baadil

As far as I am aware of there should be a PDC and one BDC for up to 10,000 users for authentication. Add another BDC for each 10,000 users. Practical limits might be as low as 5-6 thousand.

HTH

by mckaytech

The answer to the first part of your question depends on how you define simultaneous logons. If, for example, you have a large or complicated logon script, the limiting factor could easily become the network connection. The 10,000 user limit that has been suggested is related more to the size of the SAM database than to any measure of simultaneous logons. I would hazard a guess that if 1,000 users hit the box within a few seconds, there would be some delays but nothing unmanageable.

Your second question makes me chuckle because for a year now we've been trying to figure out that very thing. Theoretically, it should be the "closest" BDC but in practice, we've had workstations on our fully-switched, fiber-backbone central campus authenticate against slow (P75/64meg)BDCs hundreds of miles away across relatively slow WAN links. Even the prefdc utility from Microsoft doesn't seem to guarantee that a particular BDC will authenticate a particular workstation. So the answer to your question is "I dunno but I don't feel bad about it because no one else seems to know either...".

paul

by nsa13

Microsoft's recommendation is 2000 users per BDC. 10000 is about the MS limit for the number of users/machines/groups (40mb SAM) that MS will say can be safely supported. Of course you can go beyond those recommendations but then you go into uncharted territory. =)

With a P3/500 you should have no problem servicing that many people. Make sure that your BDCs and PDC are configured logically and physically so people don't have to go over WAN links (typically slower). If you have a larger concentration of personnel at one facility than another maybe make sure that they have there own dedicated BDC. But, rule of thumb is that every sat. office (WAN link) has a BDC and that your main office have a BDC and PDC. That should allow you tohave fast authentications and redundency in case of failure.

Authentication is based upon the browser. When a machine boots up it announces itself to the master browser of its segment. Now, the segment is a cluster of 32 machines, not neccessarily physically close to one another. So, if 1 machine from LAN2 announces itself as a BDC and 31 machines announce themselves on LAN1 than the 31 machines of LAN1 will authenticate on LAN2.

Use WINS and use it correctly. Also, adjust your workstation/DCs browser settings to compensate.

GL

This discussion is closed to new replies.