Hi,
Is it possible to have multiple GALsync MA pair in single FIM server? For example, DomainA/OU1 <=> DomainB/OU1, DomainA/OU2 <=> DomainB/OU2, DomainC/OU3 <=> DomainD/OU3 and so on.
Technology Tips and News
Hi,
Is it possible to have multiple GALsync MA pair in single FIM server? For example, DomainA/OU1 <=> DomainB/OU1, DomainA/OU2 <=> DomainB/OU2, DomainC/OU3 <=> DomainD/OU3 and so on.
The GAL Sync MA which comes out of the box has the source code with it. So you are free to modify it as you like. A I recall from an earlier poject the GAL MA out of the box works like this. On your MA you select one or more OU's which holds e-mail enabled objects for that MA's domain. You also select a container which will store the contacts created by GAL Sync which represent mail enabled objects of other domains.
And this story goes for each MA/Domain.
Is there any particular reason you want to separate them in OU's? The contacts in the "target" OU are completely FIM managed and I can't see much operational reasons to touch them out of band. Perhaps you want some distribution list logic on the OU position?
Tomek, if you are talking about using FIM to build your own GAL Sync, I would seriously consider using the one provided by the FIM product team. If it doesn't fits your needs then you can go your own solution. In my opinion using the out of the box MA increases supportability and reduces complexity. Besides that, after working with the out of the box GAL Sync MA, and going through it's code often, I've come to the conclusion that there's quit some "special" situations covered