I am having an issue with exporting from FIM 2010 into Exchange 2010. Whenever I run an export, the miisservice process (miisserver.exe) will run up to +/- 98% CPU usage and hang there until I kill the process. This happens every time an export is run even when there are no actions performed. If I remove the option for provisioning to exchange 2010 in the MA and then run an export the issue goes away.This was occuring in my canned test environment and now in my production testing as well. I have seen a couple of references to the issue and am wondering if it is being investigated or if a solution is available. My environment is as follows: FIM installed on a VM (hyper-v) running latest eval FIM (4.0.3531.2) on SQl 2008 and Server 2008 R2 exporting into Exchange 2010 (2 different exchange environs, same issue). Also of note is the error message when setting the provisioning to exchange 2010 in the MA - "the synchronization server has detected a microsoft exchange version different from the one you have selected...." Not sure if the 2 are connected. Any help would be greatly appreciated.

We are aware of this issue. The problem is in the Exchange powershell, so we can't fix this in FIM. What we will do in the next FIM update is to run AD MA's PowerShell in a separate process. When a process is idle it will be automatically terminated by the Sync Engine. This will work around this problem. As far as we know there are no issues caused by this behavior in the Sync Engine (except wasting a lot of CPU cycles). The other issue is unrelated and should be fixed with Update 1. /AndreasThis posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/copyright.htm

Hi Andreas, I am experiencing the same issue with the same configuration as TJMM. I've applied Update 1. The discovery of the Exchange 2010 schema by the MA is OK, there isn't any warning now. But the high CPU usage is always happening, each AD/Ex2010 MA export. Does the update 1 fix it? How can I run AD MA's powershell into a separate process like you ! Thank you for you answer Olivier DETILLEUX - vNext

This was fixed after Update 1. You can call PSS and ask for hotfix KB2028634. This hotfix will have the behavior I describe above. /AndreasThis posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/copyright.htm

Andreas, I am facing the same issue. Hence, called up PSS and the customer support personnel told me there was no article with the number KB2028634. He also mentioned that the KB article numbers have only 6 digits. Can you please verify the article number? Thanks!!!

Kevin, if you haven't found out by now, I can confirm that is a valid KB. I have applied it to fix a problem with FIM Sync crashing.

The fix exists but there is no KB available publically with that number. I believe it will be forthcoming.

For those interessed. One of the latest builds (4.0.3561.2) has this fix in it. It has been made available through the following KB http://support.microsoft.com/KB/2443871 which references it as a requirement.http://setspn.blogspot.com