Hello all, I hope someone has come across this with a simple fix. I wanted to test a few things, but I just did not have the time. Thus my problem. Following a ILM 2007 to FIM 2010 upgrade - driven by a database move (I assume, was not part of the upgrade). The ADMA from the ILM 2007 environment only has the ability to provision to Exchange 2003/2007. When you create a new ADMA on the upgraded FIM instance it does support Exchange 2010 provisioning. just to clarify - on the old ADMA the only option available under provisioning is "Exchange 2007 RUS (optional)". Has anyone seen this behaviour, and do you know hat fixes this? (A config export/import fixes maybe or is a MA rebuild required)Almero Steyn (http://www.puttyq.com) [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or "Helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

I apparently have a similar problem. In my test environment I have an ILM 2007 FP1 (no hotfixes or SP1) installation configured to provision Exchange 2003 mailboxes. I was unable to upgrade my database after copying it to a SQL Server 2008 R2 instance, so instead installed FIM 2010 R2 with a brand new metaverse and then imported the Server Configuration I had exported from the ILM server. Not only do I not have the Exchange 2010 provisioning option on the "Configure Extensions" pane of the ADMA properties, the Exchange 2007 checkbox I see on the ILM server is also missing! That's really unfortunate since half the reason for us to upgrade to FIM 2010 R2 is for Exchange 2010 provisioning. I found that if I export the MA again (this time from FIM), and re-import, I can't lay it on top of the existing MA but if I rename it and step through all the other settings to create a second AD MA, it does appear to give the Exchange 2007 and 2010 options via drop-down box in the Configure Extensions pane. I did not complete the import because I wasn't anxious to reload the connector space right at that moment, but I expect that with the options shown it would work. I also attempted to export the server configuration from FIM and re-import it. It did not appear to make any changes to the ADMA. So the only possible solution I can offer is this, with the caveat I haven't fully tested it yet: 1. Export your AD MA. 2. Delete the MA (not just the connector space). 3. Import the AD MA from the XML file. 4. Run a full import and synchronization. Chris