Title: Message

If you log into the machine (as an Administrator) and type the following (in bold)
 
C:\> ntdsutil
ntdsutil: ldap policies
ldap policy: connections
server connections: connect to server SERVERNAME
Connected to SERVERNAME using credentials of locally logged on user
server connections: q
ldap policy: show values
 
Policy                          Current(New)
 
MaxPoolThreads                  4
MaxDatagramRecv                 1024
MaxReceiveBuffer                10485760
InitRecvTimeout                 120
MaxConnections                  5000
MaxConnIdleTime                 900
MaxActiveQueries                20
MaxPageSize                     1000
MaxQueryDuration                120
MaxTempTableSize                10000
MaxResultSetSize                262144
MaxNotificationPerConn          5
 
ldap policy: set maxpagesize to ##### (for example, 50000)
ldap policy: commit changes
ldap policy: q
ntdsutil: q
Disconnecting from SERVERNAME ...
 
Now, that is only a workaround since you can always exceed that hard defined limit.  It is also a performance hit if you are doing large queries with results that aren't paged (i.e. returning 50000 results is a big task).
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Rudolph
Sent: Friday, November 22, 2002 10:30 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] LDAP Policies

Does anyone have any experience with changing the default LDAP policy for MaxPageSize?  We currently use the default (1,000) but have been asked by another group to significantly increase the limit (5,000 or 10,000). Apparently, the intent of the 1,000 default limit is a prevent performance hit on the Domain Controllers. I'm interested in knowing whether anyone has made a similar change and the results they experienced.  Thanks in advance.
 
 
David Rudolph
CISSP, MCSE NT & 2000, CCNP
ADS Team - Schema Administrator
Anadarko Petroleum Corporation 
 
 
 


Anadarko Confidentiality Notice:
This electronic transmission and any attached documents or other writings
are intended only for the person or entity to which it is addressed and may
contain information that is privileged, confidential or otherwise protected
from disclosure. If you have received this communication in error, please
immediately notify sender by return e-mail and destroy the communication.
Any disclosure, copying, distribution or the taking of any action concerning
the contents of this communication or any attachments by anyone other
than the named recipient is strictly prohibited.

Reply via email to