What will happen if connected CS object is disconnecte from Metaverse Object ? RRS feed

  • Question

  • We use MIIS for galsync.

    If some MA had connected to metavase person object ,

    and that MA's  had import flow and was imported some values to person object and that CS object were  disconnected from  person object, what will happne to person object ?

    Those person attribute values which are imported from that MA will disappear when disconnected ?

    Monday, August 5, 2013 3:42 AM

All replies

  • Bj08,

    if this is the actual OOB galsync solution shipped with MIIS 2003 and the connector you disconnect is for an AD user object as opposed to a contact object, then, assuming the default rules have not been modified, the person object from the MV will be deleted and this will cause any contact objects connected to this same MV object via other MAs will be set to be a pending delete from the target.

    You typically not should manually disconnect authoritative objects(users, groups) from the MV object in GALSYNC solution as the default rules specify to remove object from MV and target MAs in that case.

    Monday, August 5, 2013 4:29 AM
  • Thank you.

    In my understanding,

    In default galysnc scenario,  authoritative object deletion cause MV object deletion and other CS objects deletion.

    But what I would like to know is CS object(not authoritative object) which is joined to Metaverse object and and that CS object update MV object by import flow and that CS object is disconnected , what will happen to MV object attribute ?

    It depend on extension DLL of that MA or MV DLL ?

    Thursday, August 8, 2013 2:02 AM
  • If you mean by CS object a non-authoritative object, in the case of GALSYNC this would be a contact object, then you if disconnect a connector, the only effect on the MV object is that the multi-valued legacyExchangeDN attribute might lose the value contributed by the disconnected object. It should not delete the MV object or trigger deletions in the other MAs assuming that the default GALSYNC configuration is intact.
    Saturday, August 10, 2013 3:01 PM