SharePoint: Troubleshooting guide for importing groups and managers with MIM
Update 5/21/20: Added some PowerShell and SQL queries to help determine the state of managers and group memberships. 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
SharePoint: Profile Sync with MIM – Managers and Group memberships are not updated
Update 9/16/19: It has come to my attention that at the time of this update (9/16/19), we have a similar problem with SharePoint 2019 as we did in early SP 2016 builds. To get the timer job to process the staged manager and group membership entries, you will likely need to set the “NoILMUsed” flag
SharePoint: Profile Sync and the “Domain Users” group – the Primary Group problem
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
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: Importing Manager property with AD Import: A Troubleshooter
Overview: This is a fairly visible problem within SharePoint. It can cause the organization chart to show old manager info, or not work at all.So what to do if your user profiles show no manager value, or maybe a user has changed managers, and it’s not being updated? This is a complicated topic for a
SharePoint: Profile Synchronization – some users are missing their manager
Important: This little quirk only occurs with the “SharePoint Profile Synchronization” (aka: FIM Sync) option in SharePoint 2010 and 2013. It does not occur with the “Active Directory Import” (aka: AD Import) option available in SharePoint 2013 and 2016. If possible, I recommend switching to AD Import. You can read through switch considerations in my