Category: People Picker

Keeping SharePoint happy during your domain migration

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

SharePoint – People Picker: PeoplePickerSearchInMultipleForests

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

SharePoint: People Picker error: “user does not exist or is not unique” – similar account names

Consider the following scenario: SharePoint 2013 or 2016 servers are in the domain has a trust relationship with the domain. The peoplepicker-searchadforests property is configured like this: “;,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.

SharePoint – People Picker times out – Hybrid App Launcher issue

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

SharePoint: Certain users not resolved in People Picker – invalid character

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. 

SharePoint: The problem with changing UserQueryMaxTimeout

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