I’ve put off writing this post for a long time, hoping that the User Profile Synchronization service (aka: FIM Sync) would go away. And it is going away with the eventual retirement of SharePoint 2010 and 2013, but that’s not happening soon enough, and meanwhile we’re still seeing a lot of support cases on it.
As lame as this sounds, there have been a few (rare) situations where trying to do something with a Windows-Claims web application within Central Administration fails with an Access Denied (sorry, this site has not been shared with you) error due to lack of permissions for your Windows Classic authentication account. If you find a
Consider the following scenario: You configure Active Directory Import (ADI) within SharePoint 2013, 2016, or 2019. You make some custom user profile property mappings. You run a Full import. You notice that users have odd values with their SIP Address user profile property. For example: Or maybe it has an “SMTP:” prefix like
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
The most common reasons for some users not getting user profiles imported when using SharePoint Active Directory Import (AD Import; ADI) have been the same for a long time now. They are (in order): Container / OU selection (you didn’t select the containers that the missing users live in) LDAP Filter (your filter excludes those
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