|
Changing MaxPageSize as the solution to “the max # of objects you can retrieve” is almost always a bad idea. You should use paged searches. Here’s a bit I wrote in a mail to an alias internally just yesterday on this very topic:
<snip> For MaxPageSize……tweaking this might be ok today, or even tomorrow, but consider this….one day, you’ll exceed your new MaxPageSize. It’s not a matter of if, only when. And probably only by one or two values. Then the question is, how long will you silently be dropping a few results w/o noticing? A day? A week? Longer? Live in fear because you’ll not notice it for a while I’m sure. I hope it isn’t a query for recently fired people to remove from payroll, because after a layoff, you’ll be paying out needlessly. The reality is that relying on MaxPageSize always imposes a glass ceiling on the # of results your directory will return to you. Paged searches _is_ the right answer. </snip>
~Eric
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kern, Tom
I thought by default the max # of records that can be retrieved from a query is 1000.
I think you can fun ntdsutil to change this or better yet, if running against win2k, you can use paging. you set it with ldp.exe and an ldap control( i forget the number). also with win2k3 you can use VLV
|
- [ActiveDir] Softerra's LDAP Browser Creamer, Mark
- RE: [ActiveDir] Softerra's LDAP Browser Kern, Tom
- Re: [ActiveDir] Softerra's LDAP Browser Eric Fleischman
- Re: [ActiveDir] Softerra's LDAP Browser Kern, Tom
- RE: [ActiveDir] Softerra's LDAP Browser Marcus.Oh
- RE: [ActiveDir] Softerra's LDAP Browser Creamer, Mark
- RE: [ActiveDir] Softerra's LDAP Browser joseph.e.kaplan
- RE: [ActiveDir] Softerra's LDAP Browser Jerry Welch
- RE: [ActiveDir] Softerra's LDAP Browser Creamer, Mark
