Category: SharePoint 2016

SharePoint: Active Directory Import with Trusted Provider authentication: Map only Claim User Identifier

  Summary: You do this a bit differently than when using FIM Sync. When using Active Directory Import (AD Import) with SharePoint 2013, 2016, 2019, etc, only the “Claim User Identifier” (SPS-ClaimID) profile property needs to be mapped manually.  “Claim Provider Identifier” (SPS-ClaimProviderID) and “Claim Provider Type” (SPS-ClaimProviderType) are mapped automatically when you create the

SharePoint: Troubleshooting guide for importing groups and managers with MIM

Update 9/16/19: Updated some PowerShell and wording to also apply to SharePoint 2019. I’ve had a few posts in the past explaining various problems with importing Active Directory (AD) groups and managers. However, this post is designed to be more of a troubleshooting guide that is applicable when using Microsoft Identity Manager (MIM) to Sync

SharePoint: A Troubleshooting Guide for UserProfileApplicationNotAvailableException

Why a whole troubleshooter? In SharePoint, the User Profile Service can be one of the more finicky web services. Problems with the User Profile Service Application (UPA) may manifest themselves in several ways like: Trying to access the User Profile Service Application within Central Administration fails with “An unexpected error has occurred” Missing “Target Audiences”

SharePoint: All about one-time timer jobs

Update 9/15/19: Added some clarifying info, and some PowerShell that can be used to delete any “stuck” one-time timer jobs. One-time timer jobs are created on the fly, should run immediately, and then disappear when they are done doing whatever they were supposed to do.  If you have one-time timer jobs hanging around, you have

SharePoint: Cross-forest group memberships not reflected by Profile Import

Consider the following scenario: You have an Active Directory Forest trust between your local forest and a remote forest. You create a “domain local” type security group in Active Directory and add users from both the local forest and the remote trusted forest as members. You configure SharePoint Profile Synchronization to use Active Directory Import

SharePoint: FIM / MIM fails on Import with stopped-extension-dll-exception or read-error

  Consider the following scenario: You have one of the following User Profile Synchronization configurations for SharePoint: SharePoint 2010, which utilizes Forefront Identity Manager (FIM) for User Profile Synchronization. SharePoint 2013, using the “Use SharePoint Profile Synchronization” option, which also uses FIM. SharePoint 2016 or 2019, using the “Enable External Identity Manager” option, which (typically)