Microsoft Identity Management Solutions Supported by Exchange Server

Microsoft Identity Management Solutions Supported by Exchange Server

For years Exchange administrators have been a little confused, when it came to which Microsoft identity management solution had support for provisioning Exchange objects for the Exchange Server version(s) used in their particular organization.

This Exchange Wiki page lists the Microsoft identity management solutions supported with Exchange 2003, Exchange 2007, and Exchange 2010 respectively.


Exchange Server 2003

Exchange 2003 supports the following versions:

  • Identity Integration Feature Pack 2003 (IIFP 2003)
  • Microsoft Identity Integration Server 2003 (MIIS 2003)
  • Identity Lifecycle Manager 2007 (ILM 2007)
  • Forefront Identity Manager 2010 (FIM 2010)

note Note
Identity Integration Feature Pack 2003 (IIFP 2003) is the free version of MIIS 2003.


Exchange Server 2007

Exchange 2007 supports the following versions:

  • Identity Lifecycle Manager 2007 (ILM 2007) Feature Pack 1 and later
  • Forefront Identity Manager 2010 (FIM 2010) RTM and later

It's also possible to use IIFP 2003 or MIIS 2003 for synchronizing Exchange 2007 users as mail-enabled contacts, but it requires that you either customize the GalSync agent or perform a semi-manual post step when users have been replicated. This is because these versions depends on the recipient update service (RUS) to perform two required tasks. RUS in Exchange 2003 was responsible for setting the LegacyExchangeDN and ShowInAddressBook attributes on the mail-enabled contacts in the target organization. But since Exchange 2007 no longer used RUS, you have to run the Set-MailContact cmdlet against the synchronized contact objects in the Exchange 2007 organization. See this KB article for a detailed explanation on this topic.

For guidance on how you use one of the above synchronization solutions to perform a cross-forest migration to Exchange 2007, see this section in the Exchange 2007 documentation on Microsoft TechNet.


note Important
MIIS 2003 (and IIFP 2003) is currently in extended support. For more information see the support lifecycle here.


Exchange Server 2010

Exchange 2010 supports the following versions:

  • Identity Lifecycle Manager 2007 (ILM 2007) Feature Pack 1 Service Pack 1 and later
  • Forefront Identity Manager 2010 (FIM 2010) RTM and later

    Its also worth mentioning that with Exchange 2010, ILM 2007 Feature Pack 1 Service Pack 1 and FIM 2010 RTM no longer requires that the Exchange Management tools are installed on the ILM/FIM server. Instead the GalSync management agent takes advantage of the remoting features in PowerShell 2.0 to contact the Update-Recipient cmdlet.

     

    Like is the case with Exchange 2007, it's also possible to use IIFP 2003 or MIIS 2003 for synchronizing Exchange 2010 users as mail-enabled contacts, but again it requires that you either customize the GalSync agent or perform a semi-manual post step when users have been replicated. This is because these versions depends on the recipient update service (RUS) to perform two required tasks. RUS in Exchange 2003 was responsible for setting the LegacyExchangeDN and ShowInAddressBook attributes on the mail-enabled contacts in the target organization. But since Exchange 2010 no longer used RUS, you had to run the Set-MailContact cmdlet against the synchronized contact objects in the Exchange 2010 organization. See this KB article for a detailed explanation on this topic.

    For guidance on how you use one of the above synchronization solutions to perform a cross-forest migration to Exchange 2010, see this section in the Exchange 2010 documentation on Microsoft TechNet.

    When planning to perform a cross-forest migration to Exchange 2010, also makes sure you read this section.

    note Important
    MIIS 2003 (and IIFP 2003) is currently in extended support. For more information see the support lifecycle here.

     


    See Also



    Others Languages

    This article is also available the following languages:

Leave a Comment
  • Please add 8 and 5 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
  • Ed Price - MSFT edited Revision 27. Comment: Spacing

  • Ed Price - MSFT edited Revision 25. Comment: Reverting: (1) Failed TOC attempt. (2) Also caused indentation bug.

  • Peter Geelen edited Revision 17. Comment: Added Technet Magazine link to See also

Page 1 of 1 (3 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • Peter Geelen edited Revision 17. Comment: Added Technet Magazine link to See also

  • Ed Price - MSFT edited Revision 25. Comment: Reverting: (1) Failed TOC attempt. (2) Also caused indentation bug.

  • I understand that by default, Exchange 2010 doesn’t support  IIFP.  I already have IIFP in-place in my Ex2003 environment.  So what will happen if I introduce an Exchange 2010 server?  

  • social.technet.microsoft.com/.../eeadad2c-4c5b-46e6-80a9-a9c9786fd7c3

  • It's also worth mensioning freeware tool from Quest - www.quest.com/.../quickconnect-express-for-active-directory.aspx, also available for Exchange 2010 version.

  • Hey Konrad, thanks for the feedback. I'll create a section that list 3rd party tools such as the Quest tool and the PowerShell based sync that's available.

    Henrik

  • Ed Price - MSFT edited Revision 27. Comment: Spacing

  • Yagmoth555 edited Revision 43. Comment: adding a fr-FR's translation's link, and the a multi language tag

  • Richard Mueller edited Revision 45. Comment: Fixed HTML <h> tags so header lines show up in the TOC

  • Nominating this article to be featured. Great job!

  • Good  one !

  • Good  one !

  • THNX

  • Nice article. Thanks for delving into this to benefit the community.

Page 1 of 1 (14 items)