none
What is Contact object type assosiated with this forest setting in GALMA ? RRS feed

  • Question

  • We use MIIS for galsync.

    We see Contact object type assosiated with this forest(contact_MAName metaverse object) setting in GALMA.

    If we delete attribute flow which include this contact_MAName metaverse object , or delete this object from metaverse,

    Is there any negative impact in galsync ?

    Wednesday, June 26, 2013 9:32 AM

All replies

  • Let's start with an explanation of the contact_MAName metaverse object:

    1. If a user exists in Forest A we create a contact for him in Forest B 
    2. If a user exists in Forest B we create a contact for him in Forest A
    3. If a contact exists in Forest A we create a contact for him in Forest B
    4. If a contact exists in Forest B we create a contact for him in Forest A

    The sync engine needs a way to flow different attributes from a contact originating in Forest A (scenario 3) than the contact in Forest A that was created by the sync engine to represent an object originating from a different forest (scenarios 2 and 4). So it creates a new metaverse object type for Contacts originating from each Gal sync MA. If you delete inbound attribute flows from this object type then those attributes will no longer be imported from the contacts originating in that forest. So YES that is a negative impact unless you don't want to import those attributes from those contact objects that originate in that forest. Deleting the metaverse object type would mean that your galsync code would fail unless you modify it. NEGATIVE impact. If you don't want to import contacts from that forest you can modify your connector filter on that MA.

    You should also upgrade to FIM so that you can get support for Exchange 2007 and later -- MIIS won't run the UpdateRecpient PowerShell commandlet.


    David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

    Wednesday, June 26, 2013 3:58 PM