1

I'm in the process of setting up a new SharePoint farm. We only really need one way import for Active Directory so I've been thinking we'll go with simplified Active Directory Import... however... of the 'limitations' on TechNet at least one needs a bit of clarification

The AD import option does not support Business Connectivity Services Import. SOURCE

So... does this mean I can't use BCS... or that I can't use it to import user profiles... or that I can't combine my user profile data with data form another system...?

Or is there some other scenario that isn't supported?

0

Consider the following situations and note what the AD import option does not support when you determine whether to use this option:

  • Import operations that use this option are significantly faster than the same operations that use SharePoint profile synchronization.
  • The AD import option does not perform bidirectional synchronization. That means changes made to SharePoint user profiles will not be synchronized back to the domain controller.
  • Referential integrity among users and groups is only maintained within a single Active Directory forest.
  • The AD import option lets you configure and use only a single, farm-wide property mapping.
  • The AD import option does not automatically synchronize photos from Active Directory to SharePoint Server 2013. If you need to import photos you must use profile synchronization. For more information, see Synchronize user and group profiles in SharePoint Server 2013.
  • The AD import option does not support generic (non-AD) LDAP sources.
  • The AD import option does not support Source Schema Discovery.
  • The AD import option does not support multi-Forest scenarios such as:

    • If you have a trust between two forests, the trusted forest objects will not be imported.
    • If you need to import users from multiple domain, you must create multiple synchronization connections. If you have multiple domains to manage, using Profile Synchronization or FIM may be a better option.
  • The AD import option does not support Contact objects (also known as cross-object pointers).

  • The AD import option does not support custom object classes besides User and Group.

  • The AD import option does not filter user interface to create complex Boolean expressions.

  • The AD import option does not provide object filtering based on object property values (you must use simple LDAP filters).

  • The AD import option does not provide Logon and Resource Forest support. That is, custom joins of data from multiple sources.

  • The AD import option does not support Business Connectivity Services Import.

  • The AD import option does not support property mappings for complex types like pictures and special AD types.

  • The AD import option does not support exporting data from SharePoint to Directory Sources.

  • The AD import option does not support Upgrading/Translating FIM based connections or synchronizing configuration to AD import (or in reverse order).

  • The AD import option does not ensure single-master of each object property (currently, the last writer wins).

  • The AD import option does not perform per-tenant property mapping.

https://technet.microsoft.com/en-us/library/jj219646.aspx

  • You've just pasted the list from the same TechNet article I have already referenced. I need clarification as to what the impact will be based on the specific limitation I have highlighted. – mtwelve Feb 16 '16 at 10:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.