none
FIM 2010 R2 SP1 Missing Exchange 2013 Support RRS feed

  • Question

  • Hi,

    Forefront Identity Manager 2010 R2 SP1 is supposed to have Exchange 2013 support.  In the AD MA I see only Exchange 2007 and Exchange 2010 listed as options for Exchange provisioning.

    According to the following article:

    http://technet.microsoft.com/en-us/library/aa998597(v=exchg.150).aspx

    There should be an option to specify Exchange 2013.  I don't see this at all.  I'm running Forefront Identity Manager 2010 R2 (4.1.3419.0).

    Anyone see Exchange 2013 listed or know a fix?

    Thanks,

    Stefan

    Tuesday, March 5, 2013 1:42 AM

Answers

  • Paul recentry wrote in his blog:

    "Support for the following systems when using the OOB management agents: AD DS and AD LDS 2012; SQL 2012; Exchange 2013 (you need to pick Exchange 2010, there’s no separate option within the ADMA); Sun 7.x and Oracle 11 for the Sun and Netscape DS (now renamed to Oracle directory servers). "

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

    However, this differs from the picture that you linked. I checked this in my build 4.1.3419.0 enviroment and can't see the Exchange 2013 option either (there isn't dll either).

    Wednesday, March 6, 2013 1:30 PM
  • Buchman,

    I believe Gaston is correct, the way that FIM R2 SP1 runs update-recipient to work with Exchange 2013 is the same as with Exchange 2010. I was under the impressions(I have't tested this yet) that the dropdown looks the same and we use the same helper DLL file. I will investigate and get back to you...............

    Thursday, March 7, 2013 5:41 AM

All replies

  • Hi,

    For Exchange 2007/2010, the management agent configuration wizard performed a few checks, based on the Active Directory schema. I assume that a check was built-in for Exchange 2013 as well. Do you have Exchange 2013 running on the AD domain you're configuring?


    Best regards,
    Pieter.


    Pieter de Loos - Consultant at Traxion (http://www.traxion.com) http://fimfacts.wordpress.com/

    Tuesday, March 5, 2013 12:54 PM
  • I do.

    Domain has only ever had Exchange 2013.  Also I noticed there's no Extension DLL for Exchange 2013.

    Stefan


    Tuesday, March 5, 2013 11:17 PM
  • Paul recentry wrote in his blog:

    "Support for the following systems when using the OOB management agents: AD DS and AD LDS 2012; SQL 2012; Exchange 2013 (you need to pick Exchange 2010, there’s no separate option within the ADMA); Sun 7.x and Oracle 11 for the Sun and Netscape DS (now renamed to Oracle directory servers). "

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

    However, this differs from the picture that you linked. I checked this in my build 4.1.3419.0 enviroment and can't see the Exchange 2013 option either (there isn't dll either).

    Wednesday, March 6, 2013 1:30 PM
  • Buchman,

    I believe Gaston is correct, the way that FIM R2 SP1 runs update-recipient to work with Exchange 2013 is the same as with Exchange 2010. I was under the impressions(I have't tested this yet) that the dropdown looks the same and we use the same helper DLL file. I will investigate and get back to you...............

    Thursday, March 7, 2013 5:41 AM
  • How is it showing Exchange 2013 as an option in the drop down here?
    http://technet.microsoft.com/en-us/library/aa998597%28v=exchg.150%29.aspx

    Jimmy George

    Tuesday, February 18, 2014 6:54 PM
  • This is not a correct statement as per the Galsync issues that are being encountered upon Export run. Here is an example that there are many people who are facing issues when Exchange 2013 is involved during Galsync due to its msExchversion value being pushed to destination contacts originated from Exchange 2013 forest which Exchange 2010 forest is not able to validate. 

    Jimmy George

    Wednesday, June 4, 2014 1:22 PM
  • http://technet.microsoft.com/en-us/library/aa998597%28v=exchg.150%29.aspx is a GAL Synch MA; not an AD MA configured for Exchange 2013.

    I still have not found a detailed explanation as to how to provision mail into Exchange 2013 -- when I try to do it using the 2010 extension, all the mailboxes get created as Legacy.

    It would be really nice if Microsoft would give us some guidance.


    Ed Bell - Specialist, Network Services, Convergys

    Wednesday, April 18, 2018 7:16 PM