commit 93a77dfa7fcb842476639b0aa5dc3cee13c8538a
Author: Abraham Elmahrek <abraham@elmahrek.com>
Date:   Fri May 16 09:36:22 2014 -0400

    [useradmin] Remove server selection from ldap functionality when using legacy configuration

:100644 100644 698a3b8... c3ca8de... M	apps/useradmin/src/useradmin/forms.py
:100644 100644 ff41d31... 353ff8c... M	apps/useradmin/src/useradmin/views.py

Tested with both configurations: legacy and new.
[[ldap]]
ldap_url=ldap://<AD server>
create_users_on_login=true
base_dn=<base dn>
bind_dn=<bind dn>
bind_password=<bind pass>
[[[users]]]
user_filter="(objectClass=user)"
user_name_attr="sAMAccountName"
[[[groups]]]
group_filter="(objectClass=group)"
group_name_attr="cn"
group_member_attr="member"

and

[[ldap]]
[[[ldap_servers]]]
[[[[server1]]]]
ldap_url=ldap://<AD server>
create_users_on_login=true
base_dn=<base dn>
bind_dn=<bind dn>
bind_password=<bind pass>
[[[[[users]]]]]
user_filter="(objectClass=user)"
user_name_attr="sAMAccountName"
[[[[[groups]]]]]
group_filter="(objectClass=group)"
group_name_attr="cn"
group_member_attr="member"

Can import users and groups with both configs from AD. The problem was unrelated to AD. It was a "server selection" problem.