My current issue is not so much with why am I getting an ambiguous-import-flow-from-multiple-connectors error message, but why I am not.
I am using the Active Directory Domain Services MA for FIM 2010 R2 (Version 4.1.3441.0).
I have a join rule using the employeeID metaverse attribute--String (Indexable); Multi-valued: No; Indexed: Yes.
In one ADDS MA used to manage regular users, I am using the AD employeeID attribute to join to the employeeID metaverse attribute. I will get the following error if an AD object is already connected to the metaverse object, which is what I expect:
"Import flow was rejected because the destination metaverse object had multiple connectors from the source management agent."
In another ADDS MA used to manage administrative accounts, I am using the AD extensionAttribute1 attribute to join to the employeeID metaverse attribute. With this MA I am able to connect multiple connector space objects from this admin MA to a single metaverse object, which is what I don't want.
Note that these ADDS MAs are connected to the same metaverse object. There should be not more than one regular user ADDS (ADDS MA 1) CS object and one admin ADDS (ADDS MA 2) CS object connected to a single person metaverse object.
Has anyone else encountered this issue? For importantly, has anyone resolved this?