• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 453
  • Last Modified:

Chaning the LDAP Policies on Domain Controller

Hi guys,
So here is my case;

I have added a linked server in MS SQL to ADSI (OLEDB LDAP), and created multiple views for other business applications to use for query to AD. But I quickly found out the 1000 row limit (in the LDAP Policy, MaxPageSize). I know that we can use ntdsutil to change the policy, but I also found a lot of people warning / not advising to change the policy..

So what do you guys think ? We have a large enterprise AD with multiple child domains, sites and around 60 domain controller wordwide. (So I don't what to f*ck shit up..)
(We run Windows 2003 R2 Domain Controllers and MS SQL 2005)

Thanks for all feedback ;-)  
0
dds_felles
Asked:
dds_felles
2 Solutions
 
KenMcFCommented:
It is highly NOT recomended to change this setting. You will put extra overhead on all your domain controllers. The best thing to do here is fix your code. You should be using paged searches when doing queries against AD.
0
 
TasmantCommented:
I think you cannot do it, it's described here: http://msdn.microsoft.com/en-us/library/ms190803.aspx
Only 1000 results can be returned by the OLE DB provider.
0
 
dds_fellesAuthor Commented:
Hi guys,

Thanks for the feedback, I did some changes in my SQL view (used the "union all" clause), worked like a charm ;-)

0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now