Category: FIM Sync

This is part 3 in a series. You can find other parts here: SharePoint: The complete guide to user profile cleanup – Part1 SharePoint: The complete guide to user profile cleanup – Part 2 – 2010 SharePoint: The complete guide to user profile cleanup – Part 4 – 2016 SharePoint: The complete guide to user

This is part 2 in a series. You can find other parts here: SharePoint: The complete guide to user profile cleanup – Part1 SharePoint: The complete guide to user profile cleanup – Part 3 – 2013 SharePoint: The complete guide to user profile cleanup – Part 4 – 2016 SharePoint: The complete guide to user

Part 1: High-level Concepts If you have certain users that still show in the organization chart web part or “people search” results after being deleted or disabled in Active Directory, then it’s likely that the process to automatically clean up those user profiles is not working. Throughout the lifetime of SharePoint, there have been several

Consider the Following Scenario: You’re using SharePoint Profile Synchronization (FIM Sync) to import user profiles from Active Directory (AD) into a SharePoint 2010 or 2013 farm. Users that have been deleted in Active Directory still show active user profiles in the User Profile Service Application (UPA). They also show up in People Search results and

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

Update 11/16/22: I’ve just tested this in the latest (November 2022) builds of both SharePoint 2019 (16.0.10392.20000) and SharePoint Server Subscription Edition (16.0.15601.20226). The problem still occurs in those builds. This is a good one. It appears to be both random and intermittent (it’s actually neither), and is extremely hard to track down. It’s known

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