Hi everyone, We are using FIM 2010 RTM code to link HR with Active Directory. We created two Management Agent, HRMA that connect to HR view and ADMA that connect to Active Directory. We were able successfully to link HR with AD and do all the synchronization. But we are having problem configuring ADMA with Exchange 2007. When we try to configure Exchange 2007 support we are getting an immediate error that FIM has detected a Microsoft Exchange version different from the one you have selected. Please see screenshot below. The exchange server that we have is Exchange 2007 SP1 version . 08.01.0240.006. We also have the exact version Exchange Management Console installed on the FIM synchronization server. If we do not configure FIM for exchange provisioning, all rename and account creation works fine but with no mailboxes. Once we add Exchange 2007 support, in addition to the immediate error we are receiving we are getting ma-extension-error once we ran the export procedure on ADMA. To create Active Directory accounts we are using MV extension code using ExchangeUtils.CreateMailbox function. Does anyone know why this is happening and how we can solve it? Thanks in advance Eihab Isaac

Can you use the Exchange management tools from that same computer successfully using the same creds the MA is using? IF not, then the issue may be related to security group memberships for the account.Ahmad Abdel-wahed, Microsoft

Ahmad, Thanks for the reply I was able to create a user with mailbox from exchange management console installed at FIM Synchronization Box. Yet i'm still getting the same error, so i digged in the event logs and found this error _______________ The description for Event ID 6500 from source FIMSynchronizationService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: There is an error in Exch2007Extension AfterExportEntryToCd() function when exporting an object with DN CN=Hale\,Darla,OU=Users,OU=Olympia,OU=NA,OU=TNS Global,DC=lab-win2k,DC=lab-corp,DC=tnsi,DC=com. Type: Microsoft.Exchange.Configuration.Tasks.ThrowTerminatingErrorException Message: Unable to find '192.168.200.20' computer information in domain controller '192.168.200.20:389' to perform the suitability check. Verify the fully qualified domain name. Stack Trace: at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target) at Microsoft.Exchange.Configuration.Tasks.Task.ProcessUnhandledException(Exception e) at Microsoft.Exchange.Configuration.Tasks.Task.BeginProcessing() at System.Management.Automation.Cmdlet.DoBeginProcessing() at System.Management.Automation.CommandProcessorBase.DoBegin() the message resource is present but the message is not found in the string/message table ______________________ thanks in advance Eihab Isaac

Eihab; I ran into similar issue. It seems that you used an IP address in your AD MA instead of domain /dc name. I ran into the same issue when I entered preferred DC by IP addresses. It seems that Exchange2007Extension does not like to use IP addresses and require communicating with the domain controller using its name. Please verify that you did not use IP address to reference your domain, forest, or preferred domain controllers. If you did replace IP address with the right names and this should fix your problem Issam Andoni

FYI - this detection feature was broken in RTM but is fixed in Update 1.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com