SharePoint: Unexpected values in user profile SIP Address property

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

SharePoint: Quick Troubleshooting Tip: Add the Account column to User Information List

Often while troubleshooting authentication or permission problems, you need to see the actual account name for the user or group added to permissions. This is particularly important in SAML / Trusted Provider authentication because the way the claim is being passed in the SAML assertion must match exactly with the way claim has been added

SharePoint – Users from trusted forest are not found with People Picker

Update 8/13/20 – Added info about RPC Endpoint Mapper Client Authentication, which can break people picker in forest trust scenarios. 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

SharePoint – Slow People Picker – Troubleshooting Performance

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

SharePoint – AD Import – Some users are not imported

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

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 2016: Configure the SSRS Report Viewer web part

Starting with SQL Server 2017, there’s only one installation mode for Reporting Services: Native mode. As such, the SharePoint integration with SQL Server Reporting Services (SSRS) is pretty much limited to getting the Report Viewer web part to work. Installing SharePoint, SQL and SSRS are beyond the scope of this post, so let’s pretend you