Hi All, We do not run the FIM Portal component, just the Synchronisation service with custom extensions. I'm revisiting an error I got when I first enabled Exchange 2010 provisioning but ignored, as since having enabled this agent on the AD MA I've had two reocurring issues. Firstly, here's the error: And here's the two problems I've been having since: Occasionally, an update slated for the AD "mail" attribute will not flow through to the AD account, throwing a "exported-change-not-reimported" error on the DI side of the EDIDS pass; After every EDIDS pass, I have to restart the FIM Synchronisation Service, which while that doesn't bother me, it's hardly the way I can leave things standing. Removing the Exchange 2010 provisioning option removes the above two issues. All records provision and update successfully as they did prior to enabling the Exchange 2010 provisioning option. Here's the thing: this is a new AD environment where there has been no version of Exchange other than what we have right now installed. There were no issues with the forest or domain prep stages of Exchange, and the Exchange BPA does not report any issues whatsoever with respect to the environmental configuration. So, why is FIM telling me I'm not running Exchange 2010? That's my question. For the sake of completeness I've done as the error suggested and re-entered credentials appropriate for re-checking the forest configuration, but unsuprisingly it comes back with the same error. Are there any log files that I can review that might illustrate: How this option within the AD MA is trying to establish what Exchange version is in place; What the progressive results are from doing the above. Right now I'm in a position where I know the Exchange provisioning extension is at fault, but I have no starting point for trying to address whatever it's unhappy with. I should add as a belated note that mailboxes are provisioning just fine. There's just anomalies as illustrated two bullet-point lists back. Cheers, Lain

Do you have the update 1 bits installed for FIM 2010? I think these solved the Exchange version discovery error for me. http://setspn.blogspot.com/2010/05/fim-2010-update-1-details-available.html Regards Thomas http://setspn.blogspot.com

Hi Thomas, Thanks for the tip. I'm pulling those components down now, and if they resolve this issue I'll come back and mark the above as the answer. I'm really, really, really hoping this proves to be the solution. Cheers, Lain

Make sure you test the updates in a lab environment, or at least have a rollback plan. Good luck!http://setspn.blogspot.com

Hi Thomas, The update has resolved the identification issue for Exchange 2010, but it has not addressed the CPU issue I mentioned, so I'm going to have to keep looking at this. I can't say for sure what the status of updating the "mail" attribute is just yet, because there were only six provisions and four updates waiting, none of which seemed to spawn the "exported-change-not-reimported" error. The only thing I can say right now for sure is that the update resolved the cosmetic issue of detecting Exchange 2010 without issue. Your suggestion was helpful nonetheless. I verified again that when running the EDIDS cycle on the AD MA: Without Exchange 2010 provisioning enabled, there is no post-execution CPU issues; With Exchange 2010 provisioning enabled, the CPU-bound issue returns. Cheers, Lain

I'm not sure wheter you have an alert set on this topic, but the following topic provides an answer: you can call PSS and reference KB2028634 With thanks to Andreas and Glenn for the intel. Reference: http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/0456bce2-7f5f-45eb-aa0a-c1945d2b7065 http://setspn.blogspot.com

That appears to have done the trick. Thanks for the pointer. Cheers, Lain