none
Why so many disconnectors? RRS feed

  • Question

  • Hi,

    In the FIM terminology, a connector space object, if it is linked to a metaverse object is known as connector and disconnector if it is not linked.

    So, under which circumstances would a FIM system develop disconnectors?

    One I can think of is if the deprovisioning rule is set to "Explicit disconnector".

    Also, all the OUs from the AD MA scope are represented as disconnectors - doesn't this impact performance when doing a Sync operation?

    What else would create a disconnector?

    thank you.


    • Edited by Shim Kwan Wednesday, April 9, 2014 11:45 PM
    Wednesday, April 9, 2014 11:14 PM

Answers

  • Hi Shim,

    The best way with the AD MA to reduce the number of disconnectors is to limit what OUs are being imported from AD.  For instance if FIM is only managing users and groups - and they each live in an OU only import those OUs.  This obviously becomes tricky depending on the structure of the AD and how many user OUs etc there are, but basically import as few containers as you can possibly get away with.

    As an example I've seen an environment where FIM was managing a limited number of groups in a FIM specific OU but the AD MA was also importing 1000s of groups that FIM wasn't managing from a different OU. All those extra groups were being imported on every import run and leading to additional processing on every sync run also.

    Cheers,

    Andrew.

    • Marked as answer by Shim Kwan Thursday, April 10, 2014 9:46 AM
    Thursday, April 10, 2014 4:40 AM

All replies

  • Hi Shim,

    The best way with the AD MA to reduce the number of disconnectors is to limit what OUs are being imported from AD.  For instance if FIM is only managing users and groups - and they each live in an OU only import those OUs.  This obviously becomes tricky depending on the structure of the AD and how many user OUs etc there are, but basically import as few containers as you can possibly get away with.

    As an example I've seen an environment where FIM was managing a limited number of groups in a FIM specific OU but the AD MA was also importing 1000s of groups that FIM wasn't managing from a different OU. All those extra groups were being imported on every import run and leading to additional processing on every sync run also.

    Cheers,

    Andrew.

    • Marked as answer by Shim Kwan Thursday, April 10, 2014 9:46 AM
    Thursday, April 10, 2014 4:40 AM
  • excellent, thanks Andrew
    Thursday, April 10, 2014 9:46 AM