We are currently trying to use a custom profile import app that was written in house.

The app works fine and updates the user profile property as expected, however the FULL imports and it seems the incrementals blank out these fields.

How can I prevent this and make the fields ignored in the OOB import?

At one time the fields were mapped to a BDC connection in the import but that has been deleted

thanks

themush

Which properties are you looking to prevent their import? Not all properties can be prevented from being imported, without just outright disabling AD Import/UPSS.

Right now it shows the fields as having no mapping but the import seems to blank them out not revert to original AD field and import it

These are a few of them, if possible I want to make sure certain fields are left alone and my custom sync will take care of it

Display Name or Preferred Name

Email 

Manager

Is there a list of what must be imported from AD.

Those would be among the fields that are 'mandatory' due to the way UPSS/AD Import is set up.

You can look in the miisclient.exe connection's mapping configuration to Active Directory. To achieve what you're after, you need to not import from Active Directory.

If this is a business requirement, I would consider purchasing Forefront Identity Manager 2010 R2 and combine your data within FIM's metaverse prior to exporting to SharePoint.

I still want to use AD to import new accounts and pull in other data its just certain fields need to come form another source

If a field has no mapping will it revert to the OOB mapping and import that

I am trying to understand the behavior of the imports incremental and FULL

themush