0

This is a new single-server-farm install of SharePoint 2016 on Win 2012 R2. All seems OK except that People Picker is not finding any users. This should be a vanilla single-domain AD scenario.

I've configured AD profile synchronisation in the User Profile Service Application, and this appears to be working OK (if I go into 'Manage User Profiles' I can pull up details of the users) and I can see a count of the User Profiles.

The domain administrator account (which was used to carry out all install/config steps) can log into and browse the site collection I created, but is unable to add any other users into the site groups, because people picker isn't finding anyone else.

I have not used stsadm to modify any People Picker properties.

The site is configured to use Claims Based NTLM auth.

I'm new to SharePoint, so I suspect I'm missed a step somewhere along the way, but a day of reading has not uncovered the culprit. Do I have to somehow convert the imported profiles into actual users? Do I have to do further config to People Picker to allow it see the users? Might it be something to do with the permissions of the account the site collection is running under?

Improve this question
1
  • UPSA is not involved in the People Picker. Can you monitor the ULS logs when you search for a user via the People Picker? This should give you some idea if there is a query failing/DC inaccessible, and so forth.
    – user6024
    Commented Jun 30, 2016 at 17:08

1 Answer 1

Reset to default
1

Discovered the problem. It was because the site collection was running under an IIS app pool that was using a local user as its identity. I changed the identity to a domain user & people picker is now working.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.