I update my fim2010 to Update1 but get same error "The synchronization server has detected a Microsoft Exchange version different from the one you have selected" I used Exchange 2010 SP1... After this I get error message "stopped-server" in MA AD in Export Stage... any solution? AD agent Export return call-failure:0x800706BE

Are you using an IP in your AD MA configuration, instead of a name? see http://social.technet.microsoft.com/forums/en-us/ilm2/thread/444A0892-D904-4568-922F-2BEE1438BA38 aswell Besides that, Update 1 should fix it.http://setspn.blogspot.com

i use only full computer name... server.domain.com

any solution? have someone working with the FIM 2010 Update 1 and Exchange 2010 SP1?

Am I the only one with this configuration?

What is a alternative solution? Is FIM2010 Update 1 supports Ehchange 2010 SP1?

I can say that having both Exch2010SP1 and Exch2007 in my production I still have provisioning set up to use Exch2007. thank's for your warning.

it's not warning for me, it's problem ))

FighterZP, Try setting exchange provisioning to None, then re-enabling Exchange 2010 provisioning. I have seen a similar error for ILM 2007 after installing very recent update where symptom is similar, disabling and re-enabling Exchange provisioning seems to fix it.

I try disable and re-enabling Exchange provisioning - but nothing change to better ( same problem with Exchange 2010 without SP1... additional symptoms: in Exchange Console I see all users, but they Recipient Type Details = Legacy Mailbox and primary SMTP Address field is empty When I double click on this entries - I get error: The properties on this object have invalid data. If you click OK, default values will be used instead and will be saved if you do not change them before hitting Apply or OK on the property page. If you click cancel, the object will be displayed read-only and corrupted values will be retained E-Mail Addresses Tab empty. When click "Add..." button and set SMTP address - I see new error -> "ExchangeGuid in mandatory on UserMailbox" My Fim Portal User Sync Rule configuration for Exchange: true -> mDBUseDefaults mailNickName -> mailNickname Trim(/o=Company/ou=Exchange Administrative Group (xxxxxxxxxxx)/cn=Configuration/cn=Servers/cn=MAIL01-SRV)->msExchHomeServerName Trim(CN=MailStorage1,CN=Databases,CN=Exchange Administrative Group (xxxxxxxxxxx),CN=Administrative Groups,CN=Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=com)->homeMDB This settings successfully add to user ADSI properties. In AD MA I set: Provisioning for -> Exchange 2010 Exchange 2010 RPS URI -> http://server1.company.com/powershell

I suppose you should have powershell errors on FIM server during export to AD. 'cause what this option was really doing for Exch 2007 support is just starting update-recipient cmdlet to set exchange attributes for a user. if it fails to run - you'll have legacy mailbox for a user.

how configure additional logging for catch this error?

in this article http://fabienduchene.blogspot.com/2010/02/fim-2010-exchange-2010-provisioning.html Synchronization Service manager Console -> Tools -> Options -> Rules extension name: Exch2010Extension.dll but in my configuration this field has custom rules DLL for another export agent. if I change Rules extension name to Exch2010Extension.dll, than almost all my MA generate errors like: stopped-extension-dll-no-implementation How use together Exch2010Extension.dll and custom rules dll (for export agents)?

FighterZP, What you referenced here: My Fim Portal User Sync Rule configuration for Exchange: true -> mDBUseDefaults mailNickName -> mailNickname Trim(/o=Company/ou=Exchange Administrative Group (xxxxxxxxxxx)/cn=Configuration/cn=Servers/cn=MAIL01-SRV)->msExchHomeServerName Trim(CN=MailStorage1,CN=Databases,CN=Exchange Administrative Group (xxxxxxxxxxx),CN=Administrative Groups,CN=Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=com)->homeMDB This settings successfully add to user ADSI properties. In AD MA I set: Provisioning for -> Exchange 2010 Exchange 2010 RPS URI -> http://server1.company.com/powershell Should be enough to have properly provisioned users in AD with mailboxes and which show up as expected in the Exchange Management Console. As for the extension dll referenced by Fabien, there is no need for this in the RTM version of FIM. Just use "provision for exchange 2010" As for additional logging, be sure to check the eventvwr's of your sync server and "server1" (your cas server). They will show errors if things go wrong with the "update-recipient" part which should mail-enable the user for you. On the other hand, I'm not 100% sure whether the "provision for exchange 2010" works when you flow those attributes after the original user was created in AD. I've always flown those attribute during the "provision add" phase towards AD... What are you doing? http://setspn.blogspot.com

bingo! :) I found my problem: fim create users on domain controller dc01.company.com. but exchange server work with dc02.company.com. In AD MA I changed preffered domain controller to dc02.company.com and mailbox created correctly. New question: how I can set preffred domain controllers list for Exchange Server? because I will have problems when Exchange change his current used domain controller.

FighterZP I was under the impression that the update-recipient had an extra parameter "domain controller" and that the FIM Sync Service provides the same domain controller in this parameter it used to create the actual user on. So while the command is indeed remotely (powershell) executed on an exchange server, it should use the same DC as the FIM Sync engine. Althouh I'm not 100% sure this is what they do. Perhaps someone from MS can clarify this. Regards, Thomas http://setspn.blogspot.com

There was an old bug in MIIS and Exch2007 provisioing - user was created on one DC and update-recipient cmdlet was connecting to another DC earlier than replication changes was committed to the second DC. then MS made a fix for it. it looks like you hit an old bug again.