|
Ok, he created one user-defined ou , and added an object in that
container. If he adds more than this values, the
limit exceeded message appears:
Thanks for your help! Steve From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Eric Fleischman I could probably tell you which admin
limit you’re exceeding if you tell me the OS version & service pack
level. Most admin limits are there to protect
perf of the box & prevent against DoS attacks. Better than changing the limits
would be to change the query to use LDAP RFC compliant ways to performing the
action w/o changing lmits. For example, if the limit is # of objects returned
per page, rather than using a huge page you’d do a paged search. So the questions that would be of
interest: 1) OS and service pack level 2) What is the action being performed (as an example, if this is a
search, baseDN + scope + filter) Thanks! ~Eric From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Brashear I have a customer who has created an OU and
populated it with objects that have many attributes. He is now encountering
this error: Is there a maximum size limitation for
user defined objects in AD? Can that value be modified? Where would one modify it? Would it
be in the LDAP policies/protocols configuration? TIA! |
- [ActiveDir] Exceeding the LDAP Look Through Limit Steve Brashear
- RE: [ActiveDir] Exceeding the LDAP Look Through Limit Cotter, Paul M.
- RE: [ActiveDir] Exceeding the LDAP Look Through Limit Eric Fleischman
- RE: [ActiveDir] Exceeding the LDAP Look Through Limit Steve Brashear
- RE: [ActiveDir] Exceeding the LDAP Look Through Limit Eric Fleischman
- RE: [ActiveDir] Exceeding the LDAP Look Through Limit Eric Fleischman
- RE: [ActiveDir] Exceeding the LDAP Look Through Limit Eric Fleischman
- RE: [ActiveDir] Exceeding the LDAP Look Through Limit joe
