Sorry to resurrect my old post, but I'm trying to use LDAP in ProGet and am running into the same issue. Users and groups that are in the domain of the server running ProGet are found, but users in a different domain are not.

You're right, at the moment the LDAP provider uses whatever domain it happens to be a part of. We'll put it in the roadmap, but we also offer the ability to "speed up the process" so-to-speak for our enterprise customers via our professional services. If you would be interested in this option for your organization, just send us a message using the contact form (http://inedo.com/contact).

The 1000 is a limit imposed by Active Directory presumably for performance reasons. Typically, you shouldn't ever need to be on the users page when using Integrated Security because once a user is assigned privileges via the "Assign Security Privileges" page, they automatically become a named user if there are licenses available when they visit the BuildMaster URL. We are planning an enhancement that will determine based on the assigned privileges whether the user should be approval-only or full, but for now it will default to full (if available) and downgrade to approval-only if no full user licenses are available. Once the user has become a named user, you can manually edit the type of user on the "License Key and Activation" page which allows you to select "[change]" to toggle the user between full or approval-only as needed.

That error message says "DirectoryProvider 1" which is the built-in provider. If you open up the Admin Tool located in the BuildMaster installation directory you can switch the directory provider to the LDAP one.

This can sometimes happen when the cookies are not cleared properly after an upgrade. Try flushing your browser cache and clearing your browser's cookies, then visit the BuildMaster site root, e.g. http://buildmasterinstall.corp/