• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 622
  • Last Modified:

Sharepoint users unable to search AD

So I've been asked to setup SharePoint, which went just fine (as far as I can tell).  
I have a simple task application I've added to a site collection,  When trying to "Assign To" it populates the users to select and link with active directory.  The problem is that this only works for the Owner (sharepoint-owner.png),  The Group Members cannot populate this information (sharepoint-user.png)

users in the group  have "edit" permission to the entire site,  what piece am I missing!


SharePoint 2013 on Server 2012R2  connecting to SQL 2012 on Server 2012R2
  • 2
1 Solution
You can configure the 2013 people picker control to limit selection to a particular OU in a domain, or limit to site users only, however I'm not sure that would give the behaviour you have reported (see reference here to check for yourself: https://technet.microsoft.com/en-us/library/gg602075.aspx)

Your problem may be something with the User Profile Service not being properly configured.   This syncs with AD to provide a copy of AD within Sharepoint.  When not available, SharePoint checks AD directly (which often means people don't even realise this service is not configured until something odd happens).  This process relies on many permissions being configured correctly, and can be quite a weak spot. Have a look at this: https://technet.microsoft.com/en-us/library/ee662538.aspx.  

I still can't see why this would work for owners and not members, so:
First step: ensure EVERYTHING is patched to current patch level, including domain controllers.

Then check Central Admin to see this service is configure, working, and has imported AD from your domain.
Check the ULS logs and look for problems with the User Profile Service, or any other "permission denied" errors.
DeltaMNAuthor Commented:
Thank You Colly,

That link got me on the right path, in all my searching prior to on this forum, "people picker" wasn't anywhere in sight.   I ended up getting it to work with this command from powershell

stsadm -o setproperty -pn peoplepicker-searchadcustomfilter -pv "(&(objectCategory=person)(objectClass=user)(!userAccountControl:1.2.840.113556.1.4.803:=2))"  -url http://servername   

(servername was my working server url)


Now all of my users across all sites can search by typing in the first 3 characters.
Thanks for posting the answer you found that is new to me - that is a very interesting command you had to run!  SharePoint is great,  but it can drive you absolutely crazy!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now