none
joining AD user to existing metaverse peson object is impossible ? RRS feed

  • Question

  • There is one person ojbect in metaverse which is imported from GAL MA1(say AD1).

    Same user's mailbox exists in other Forest and I tried to import by GAL MA2(say AD2),

    but join-resolution error happened.

    If in attribute flow , join rule from datasource(user)  to person object is defined,

    is it impossible to join data source( user) object to existing metaverse object ? 

    GAL_MA2 with  DN CS GAL_MA2 user someuser  attempts to join when it should be projected.  There is another authoritative object representing the same entity in the metaverse: CS GAL_MA1 user someuser. This object will not be propagated to any other forests until this conflict is resolved by removing or modifying one of the objects so that they no longer collide.

    <input id="b3735990-d1ac-4011-9076-b420c6e37701_attachments" type="hidden" />
    Wednesday, November 14, 2012 2:39 AM

Answers

  • In the knowledge base article below it is stated that GAL Sync has trouble with accounts with the same email addresses in different forests.

    KB article

    The solution according this article would be to eliminate the duplicate email addresses.

    Monday, November 19, 2012 12:50 PM

All replies

  • I'm sure that I get your question completely. But for proper joins to take place you need to make sure that enough data exists on the metaverse objects projected. So make sure that the MA that Projects also have enough inbound attribute flows for the attribute values that is use for joining from the other MA's

    You may want to be a little more clear on the question.


    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

    Friday, November 16, 2012 3:25 PM
  • In the knowledge base article below it is stated that GAL Sync has trouble with accounts with the same email addresses in different forests.

    KB article

    The solution according this article would be to eliminate the duplicate email addresses.

    Monday, November 19, 2012 12:50 PM