FIM 2010 for GALSync cross forest, Exchange 2013

hi All, 

We have a AD in Multiple Forest Multiple domain. Each forest and domain represent the single company. Each company have different Exchange version, Exchange 2007, Exchange 2010, and Exchange 2013. We only have FIM 2010 (not R2 version). Just simple question, Can FIM 2010 do the GALSync for Exchange 2013?

Based on this article, http://technet.microsoft.com/en-us/library/aa998597(v=exchg.150).aspx, Exchange 2013 is only supported by FIM 2010 R2 Sp1.

Thanks.

May 16th, 2013 3:24pm

That is correct support for Exchange 2013 was not added until FIM 2010 R2 SP1

http://blog.ilmbestpractices.com/2013/01/fim-2010-r2-sp1-documentation-and-bits.html (feature # 7)


Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2013 7:04pm

Hi David, 

i already install FIM 2010 R2 With SP1 Build number: 4.1.3419.0. but no extension for Exchange 2013? is it right?

August 22nd, 2013 11:32am

You select Exchange 2010, there is no separate option on the ADMA:

http://blog.msresource.net/2013/01/30/forefront-identity-manager-2010-r2-service-pack-1-released/




Free Windows Admin Tool Kit Click here and download it now
August 23rd, 2013 2:56am

You select Exchange 2010, there is no separate option on the ADMA:

http://blog.msresource.net/2013/01/30/forefront-identity-manager-2010-r2-service-pack-1-released/




August 23rd, 2013 2:56am

Hi fellas, 

Thanks,it's work, but we get another problem.

When we run the GALsync from Exchange 2013 to Exchange 2010, we get error:

1. ma-extension-error, event viewer error:

Log Name:      Application
Source:        FIMSynchronizationService
Date:          8/30/2013 12:13:46 AM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FIM.endrik-it.com
Description:
The description for Event ID 0 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 Exch2010Extension AfterExportEntryToCd() function when exporting an object with DN CN=Steven Gerrard(1),OU=GALSync,DC=endrik-it,DC=com.

Type: System.Management.Automation.RemoteException

Message: The property 'AddressListMembership' is on a read-only object and can't be modified.

Stack Trace:    at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.Invoke()
   at Exch2010Extension.Exch2010ExtensionClass.AfterExportEntryToCd(Byte[] origAnchor, String origDN, String origDeltaEntryXml, Byte[] newAnchor, String newDN, String failedDeltaEntryXml, String errorMessage)

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="FIMSynchronizationService" />
    <EventID Qualifiers="0">0</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-30T07:13:46.000000000Z" />
    <EventRecordID>1576</EventRecordID>
    <Channel>Application</Channel>
    <Computer>FIM.endrik-it.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

There is an error in Exch2010Extension AfterExportEntryToCd() function when exporting an object with DN CN=Steven Gerrard(1),OU=GALSync,DC=endrik-it,DC=com.

Type: System.Management.Automation.RemoteException

Message: The property 'AddressListMembership' is on a read-only object and can't be modified.

Stack Trace:    at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.Invoke()
   at Exch2010Extension.Exch2010ExtensionClass.AfterExportEntryToCd(Byte[] origAnchor, String origDN, String origDeltaEntryXml, Byte[] newAnchor, String newDN, String failedDeltaEntryXml, String errorMessage)</Data>
  </EventData>
</Event>

2. if we check on the OU GALSync and mail contact on the Exchange 2010, we got double contact created.

anyone can tell me how to fix it?

same problem here http://social.technet.microsoft.com/Forums/en-US/0be32d4d-5b38-4a72-8cbf-bed0ab98a3e8/fim-galsync-maextensionerror#97bfaad5-7df4-46fb-9d33-5425fcce98d2, but need to hard coded the msExchversion attribute, and I dont know how to hard coded. Please if anyone can help.

Thanks.

Endrik

Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2013 6:25am

hi All, 

this is related to the Exchange version attribute. You need add some code for msExchVersion and re-build the GALSync.dll.

Thanks.

Endrik

January 8th, 2014 7:05am

What code is inserted?  How do you get FIM 2010 R2 Sp1 to work properly with Exchange 2013 cross forest galsync?  I cannot find information anywhere... 

I am also having this exact same issue, I am performing a cross forest migration, exchange 2010 in old forest, exchange 2013 in new forest.  Contacts created from MEU's in new forest throw above error and duplicate contacts build up in galsync OU after every export.  Right now there are only 3 users but soon we will start migrating and GAL will become a mess.   Any detailed help to resolve issue would be much appreciated, at this point the client is losing confidence in project.  I am losing confidence in using FIM to maintain galsync.

Free Windows Admin Tool Kit Click here and download it now
February 24th, 2015 3:24pm

Microsoft just released a patch for it:

http://support.microsoft.com/kb/3022704

February 26th, 2015 10:55am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics