Skip to main content

Cloud

Bizarre Behavior in the SharePoint Portal Profile Import

I’ve run into a rather interesting issue concerning SharePoint Profile imports and deleted users. You probably know that SharePoint marks users as "missing from import" when they are not found in Active Directory after three consecutive Full Imports. The issue I’ve seen is that if you run an Incremental Import in between the three Full Imports the deleted users will NOT be put in the "missing from import" list. The three Full Imports must be consecutive and not interspersed with Incremental Imports in order to catch the deleted users. Once the users get to the missing list, you’re fine. They won’t be put back in the active list.

Example: Run three Full Imports after deleted a user from Active Directory. After the third import the user is shown in "Missing from import". Run a two Full Imports after deleting another user from Active Directory. Then run an Incremental Import. Then run another Full Import. The user is not shown in the missing from Import.

If you are familiar with backup or index scheduling you might assume you should schedule a Full job once a day and an Incremental job several times a day. This won’t work correctly for SharePoint if you want to remove deleted users from the profile database.

This behavior is not documented in the Resource Kit or the SharePoint Portal Server admin guide. As a workaround, I’ve been manually running three consecutive Full Imports to clean up the deleted profiles. I’ve tested this on several servers both SPS SP1 and SPS SP2.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

PointBridge Blogs

More from this Author

Follow Us