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)
Update 4/15/20: I tested this with AD Import and SharePoint 2019. It’s still the same story with SharePoint 2019. This problem manifests itself in a few different ways: You create an Audience based on “Member Of” the “Domain Users” group. You notice there are only a couple (or maybe even zero) members shown, whereas you
This is part 4 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 3 – 2013 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 have SharePoint 2016 configured to import user profiles using Microsoft Identity Manager (MIM) 2016 as the External Identity Manager. You have configured MIM to import profile pictures from Active Directory (AD). After the pictures have been created in SharePoint, you decide to reverse the flow to export profile pictures from
Consider the following scenario: You have SharePoint 2016 set up to import user profiles from an External Identity Manager. We’ll say you’re using Microsoft Identity Manager (MIM) 2016 to import profiles from some 3rd party LDAP directory. The profiles should be imported as Trusted Provider type users (SAML-claims). You run a Sync, and everything goes
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.