Category: People Picker

Consider the following scenario: You have your SharePoint servers in the “Contoso.com” domain. You have the peoplepickersettings.searchactivedirectorydomains (SearchADForests) People Picker property configured properly to search trusted forest “fabrikam.net”. You search for a user that exists in the trusted forest and get “No results found” in the People Picker control. If you set your SharePoint logging

Poor people picker performance is usually caused by one of two things: 1. People Picker (hereafter abbreviated as PP) is connecting to a Domain Controller across a slow network link. 2. People Picker is trying to query domains that are not available on the network (usually due to firewall settings). Note: If PP performance is

We’ve seen a few of different problems occur in SharePoint (2013, 2016, 2019) when users are being migrated from one domain to another. They usually come up in one of the following areas: People Picker People Picker may show either or both accounts depending on which domain SharePoint is in, and how PP is configured

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