Today I’m writing about a little-known SharePoint People Picker property that can influence your People Picker results. First some background: In SharePoint 2010, People Picker searched all two-way trusted Active Directory (AD) forests by default. In SharePoint 2013 and above, only the local forest is queried, but similar to Exchange, we also leverage the mxExchMasterAccountSid
Consider the following scenario: You have a SharePoint 2013 or 2016 web application that has both Windows and Trusted Provider / SAML authentication (ADFS, etc) enabled. You have a list with a “Person or Group”-type (aka: “people picker”) column in it. You edit the list using the “Quick Edit” / “edit this list” functionality to
Consider the following scenario: SharePoint 2013 or 2016 servers are in the contoso.com domain contoso.com has a trust relationship with the corp.fabrikam.com domain. The peoplepicker-searchadforests property is configured like this: “forest:contoso.com;forest:corp.fabrikam.com,corp\SPadmin,*****“ You use People Picker to find a user. If the users account name (samAccountName) is unique, you have no issues adding it to SharePoint.
This was a really unique situation where a network problem for the Hybrid App Launcher caused People Picker to intermittently time out and display no results. Note: The two features are not directly related as you’ll see below. Let me explain: When you configure Hybrid OneDrive and Sites in SharePoint 2016, it adds an
Here I cover how to use Fiddler and IE Developer Tools (F12) to troubleshoot People Picker problems in SharePoint 2013 and 2016 within the context of a problem I recently came across. Problem: Certain users are not resolved in People Picker. The client-side people picker control shows no results, but doesn’t throw an error either.
Consider the following scenario: You have a fairly large and / or complex Active Directory (AD) infrastructure.When using People Picker in a SharePoint 2013 or 2016 site, you are unable to find users from certain domains, and eventually the People Picker control displays an error: “Sorry, we’re having trouble reaching the server”. You do some
SharePoint: Person or Group column does not display expected results when limited to a SharePoint group
Consider the following scenario: You have a SharePoint list with a Person or Group column.This column is limited to choose from a SharePoint group called (for example) Approvers. Within this SharePoint group, you have three users with (for example) first name Jeff, and one user with last name Jefferson. Within the person or