If the client is indeed processing paged results, I would think this issue does lay within the DC’s Page Size being limited to 1000. It sounds like the client is capable of processing 5000 results, but the DC isn’t capable of returning them due to being limited at 1000.
*Erik* *From:* Miguel Goya [mailto:[email protected]] *Sent:* Friday, March 31, 2017 12:05 PM *To:* [email protected] *Subject:* Re: Guacamole and Active Directory Paged Results They are. *Miguel Goya * | Senior Infrastructure Engineer [image: Image removed by sender. ClearEdge Named a Top Workplace for a 3rd Straight Year] <http://www.clearedgeit.com/news/2016/baltimore-sun-top-workplace/> a: 10620 Guilford Road | Suite 200 | Jessup, MD 20794 p: 443-212-4700 | w: www.clearedgeit.com On Fri, Mar 31, 2017 at 12:05 PM, Erik Berndt <[email protected]> wrote: Are all the users within the AD sub-tree you defined in ldap-user-base-dn? Erik *From:* Miguel Goya [mailto:[email protected]] *Sent:* Friday, March 31, 2017 11:09 AM *To:* [email protected] *Subject:* Guacamole and Active Directory Paged Results Hello, I am having problems with Guacamole displaying all of my user accounts in Active Directory. I am running 0.9.11. Authentication is working fine but I am unable to access all users account in the Guacamole UI. I added the ldap-max-search-results property to my guacamole.properties and set it 5000. The UI still only display 1000 accounts. My organization does not want to modify the server side AD setting of 1000 for MaxPageSize. In theory this should not matter if the client application can process paged results. It was my understanding that Guacamole should support paged results Anybody come across this problem and find a solution? Thanks
