Are there any issues with people picker in SharePoint?
There are a handful of People Picker issues, where a particular user, group, or all objects cannot be resolved. Here are some common scenarios with easy resolutions.
Why does people picker not resolve users from other domains?
On a SharePoint site, users from other domains don’t get resolved from People Picker. Additionally, You receive the error message “No match found.” With the installation of Service Pack 2 (SP2), suddenly the People Picker would not resolve users from other domains even if one-way trust was enabled.
How to set people picker in SharePoint local domain?
You need to set the peoplepicker-searchadforests property for each one-way trusted domain from a SharePoint perspective. The following command was delivered to have the people picker look up users in all domains that are in trust relationship with the SharePoint local domain.
Do you need to set people picker in SP2?
SP2 enforces the security features with respect to People Picker and the peoplepicker-searchadforests property. You need to set the peoplepicker-searchadforests property for each one-way trusted domain from a SharePoint perspective.
Are there filters on the people picker queries?
Verify that there are no filters on the People Picker queries for the Web Application. This can be validated with PowerShell. Quick and easy ways to troubleshoot are if you do not see the troublesome behavior on another Web Application, it is going to be the People Picker Settings or Application Pool account.
How can I troubleshoot my people picker account?
Quick and easy ways to troubleshoot are if you do not see the troublesome behavior on another Web Application, it is going to be the People Picker Settings or Application Pool account. If you see the issue farm-wide (that is, Central Administration and all Web Applications), it is likely a firewall or name resolution issue.
Do you need Sid to use people picker?
When using Windows authentication, only objects with Security Identifiers (SID) can be searched with the standard permissions-based People Picker (Audience Targeting is a different story). This means the object must be a User account or an Active Directory Security account.