AD User Import Feature Request
It would be very nice if the AD user import allowed for filtering. Example: I only want to import users who are members of a certain AD Group.
This would be a nice addition and should not be difficult to implement. Allow the admin to specify a filtering attribute string after they select an OU to import from.
In my example above I would select my OU with users. And then enter my filter "memberof=CN=MyGroup, OU=Groups, DC=test, DC=stuff, DC=com"
AD allows for some very specific queries, it's a shame they aren't allowed to be implemented more often.
I have been testing several help desk solutions for possible implementation. Most of which do not allow for this filtering, and the others that do are not good enough in other areas to use for our purposes.
I really enjoy SD+ in the short time I've been able to use it, however this is a sticking point for me because we are a small part of a huge organization. Having to import 51000+ users when we only support ~400 is very time consuming and a waste of resources.
If there is a way around this problem, or if this will be addressed in future revisions, please let me know.
Ryan
This would be a nice addition and should not be difficult to implement. Allow the admin to specify a filtering attribute string after they select an OU to import from.
In my example above I would select my OU with users. And then enter my filter "memberof=CN=MyGroup, OU=Groups, DC=test, DC=stuff, DC=com"
AD allows for some very specific queries, it's a shame they aren't allowed to be implemented more often.
I have been testing several help desk solutions for possible implementation. Most of which do not allow for this filtering, and the others that do are not good enough in other areas to use for our purposes.
I really enjoy SD+ in the short time I've been able to use it, however this is a sticking point for me because we are a small part of a huge organization. Having to import 51000+ users when we only support ~400 is very time consuming and a waste of resources.
If there is a way around this problem, or if this will be addressed in future revisions, please let me know.
Ryan