This is an interesting “gotcha” that came up recently: Problem: The Active Directory Import (UserProfileADImportJob) timer job does not run. It’s enabled and scheduled to run (default every 5 minutes), but never runs.The result is that the user profiles never get imported. Cause: All the servers in the farm that are running the User Profile
Problem: Consider the following scenario: You have SharePoint 2016 set up to import user profiles from Microsoft Identity Manager (MIM) 2016. You have configured User Profile Pictures (PictureURL property) to import from Active Directory Attribute ThumbnailPhoto. See my related blog post here. You run the Sync, and everything is successful including the Export sync step.
Problem: Consider the following scenario:The User Profile Service (the web service, not the Sync service) is running on two servers in the farm: App1, App2.In that case, the <UPA name>- User Profile Incremental Synchronization timer job (internal name: ProfileImportJob) can run on either server. The User Profile Synchronization Service is running on App2.When the User
This is a good one, it appears to be both random and intermittent, and is extremely hard to track down. It’s known as the “SID mismatch” problem. Consider the following scenario: Intermittently, when a user browses to a resource (site, list, etc) that they are supposed to have access to, they receive “Access Denied“, or
Here’s one that was a problem in SharePoint 2013, was fixed, but never ported to SharePoint 2016, so we had to fix it again. Consider the following scenario: You are importing user profiles from Active Directory (AD). This can happen using any of the profile import methods for either SharePoint 2013 or 2016. 2013: SharePoint
In this post, I’ll walk through importing user profile pictures to SharePoint 2016 using Microsoft Identity Manager (MIM) 2016 using a ton of screenshots. The idea is to show how the process works so you know how to configure it and where to go looking when something goes wrong. After completing the basic SharePoint 2016/
Many times we end up battling “SharePoint Profile Synchronization” (aka: “FIM Sync”) for a while before we realize that “SharePoint Active Directory Import” (aka: “AD Import”, aka: “ADI”) was a better fit all along. Why switch? Or for new farms, why go with AD Import? “SharePoint Active Directory Import” (“AD Import” from here on) is