User1095185381 posted
I forgot to ask: what directory are you using? Certainly for Active Directory, 5000 users isn't a lot. Maybe my big dinner's gone to my brain but I can't figure what you mean by DL.
Only getting 1000 records usually means you haven't set the PageSize parameter. This code (C#) will get all users in your domain and display their sAMAccountName:
static void Main(string[] args)
{
string defaultNamingContext = GetDefaultNamingContext();
using (DirectorySearcher ds = new DirectorySearcher())
{
ds.Filter = "(&(objectClass=user)(objectCategory=person))";
ds.SearchScope = SearchScope.Subtree;
ds.PageSize = 1000;
using (SearchResultCollection src = ds.FindAll())
{
foreach (SearchResult sr in src)
{
Console.WriteLine("Found user: {0}", sr.Properties["sAMAccountName"][0].ToString());
}
}
}
Console.WriteLine("\r\nPress a key to continue...");
Console.ReadKey(true);
}
private static string GetDefaultNamingContext()
{
using (DirectoryEntry rootDSE = new DirectoryEntry("LDAP://RootDSE"))
{
return rootDSE.Properties["defaultNamingContext"].Value.ToString();
}
}
If you run the code and watch the display, you'll notice it pause every so often - if you add a counter to the display, you'll see that it pauses every 1000 users. This is the way ActiveDirectory works if you activate paging (by setting PageSize to
1000). You can set paging to less than 1000 and get a more responsive application, if you want.
I seem to have confused you with my original reply. When I was talking about the server setting, I was trying to say that you can make the server return more than 1000 objects at a time but all this does is increase the size of the page - you still
need paging to make it work and since your admin guys probably won't want to do it I wouldn't worry about it.
I suggest you start by getting your query working in a basic console app, then transfer the working class(es) into your app proper.
