Category: FIM Sync

SharePoint: The complete guide to user profile cleanup – Part 2 – 2010

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   Sync Options: Profile Synchronization (AKA:

SharePoint: The complete guide to user profile cleanup – Part 1

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

SharePoint 2013: User Profile Incremental Synchronization timer job fails with Access Denied

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

SharePoint: Users randomly lose permission – are deleted from site

This is a good one, it appears to be random, and intermittent, and is extremely hard to track down. 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 our more friendly version: “Sorry, this site hasn’t

SharePoint 2013 & 2016 – Manager and Assistant values swapped in User Profiles

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

SharePoint: Considerations when switching from FIM Sync to AD Import

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