Category: AD Import

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

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: All about non-imported user profiles

I find there is much confusion around this topic, so I’ll try to clear it up here. First off, non-imported profiles are well… not imported. They were not created by Profile Sync / AD Import / Sync with External Identity Manager. We also refer to these as “unmanaged”, or “stub” profiles because they typically only

SharePoint: This Profile Import error is (usually) normal

  Here’s an example of an error that often occurs during Active Directory Import (aka: ADI, AD Import):   ScanDirSyncChanges: Batch-abort Exception in processing response for page ‘7’, exception ‘System.DirectoryServices.Protocols.DirectoryOperationException: An operation error occurred.   Under what conditions might this occur? You have an Active Directory group that has over 5,000 members. You may see