No - presumably you are concerned that the deltas might be lost to FIM if ILM imports them, or vice versa? It is the ILM and FIM CS respectively which keep track of the watermark for comparison of changes ... not the ADLDS service itself. I would recommend that you use an event driven service to detect changes in ADLDS to drive DI/DS run profiles for at least the downstream FIM AD MA, but also run the pending exports from ILM on demand.Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

Hi all, We are migrating from FIM to ILM. For a period of time, we'll have both FIM and ILM in production. We have an LDS server that we use an ILM input/output MA to both populate and read data from. The plan is to bring up up an import-only FIM MA while the bi-directional ILM MA continues to run. In such a setup, is there any issue with deltas generated by LDS? Thanks, Greg

No - presumably you are concerned that the deltas might be lost to FIM if ILM imports them, or vice versa? It is the ILM and FIM CS respectively which keep track of the watermark for comparison of changes ... not the ADLDS service itself. I would recommend that you use an event driven service to detect changes in ADLDS to drive DI/DS run profiles for at least the downstream FIM AD MA, but also run the pending exports from ILM on demand.Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

Thanks, Bob.