Share via


Release Notes for Forefront Identity Manager 2010 R2 SP1

Welcome to the release notes for Microsoft® Forefront® Identity Manager (FIM) 2010 R2 SP1. Before you install this application, we recommend that you read this entire document and the Forefront Identity Manager 2010 R2 Deployment Guide. You can use these notes to guide you as you troubleshoot issues that may arise when you use FIM 2010 R2.

Release Notes for Forefront Identity Manager 2010 R2 SP1 – Known Issues

The following sections provide more details about the required upgrade steps and known issues.

Pre-Installation and Upgrade of the FIM Service and Portal

Before you can upgrade a computer that has the FIM service deployed to FIM 2010 R2 SP1, you need to stop the service. This is because the upgrade process modifies the database of the FIM service.

The following table provides a comprehensive overview of potential upgrade scenarios and the related steps:

Current OS

FIM Component

Desired  OS and Application

Minimum Version to support Desired OS and Application

Recommended Upgrade steps

Windows SharePoint Services or SharePoint Foundation 2010

FIM Portal

Windows Server 2008 R2 SP1 with SharePoint Foundation 2013

FIM 2010 R2 SP1

  • Uninstall FIM Portal

  • Uninstall SharePoint or WSS

  • Install SharePoint Foundation 2013

  • Install FIM 2010 R2 SP1 Portal

  • Install FIM 2010 R2 SP1 Language Packs (optional)

Windows SharePoint Services or SharePoint Foundation 2010

FIM Portal

Windows Server 2012 with SharePoint Foundation 2013

FIM 2010 R2 SP1

  • Uninstall FIM Portal

  • Uninstall SharePoint or WSS

  • Upgrade operating system to Windows Server 2012

  • Install SharePoint Foundation 2013

  • Install FIM 2010 R2 SP1 Portal

  • Install FIM 2010 R2 SP1 Language Packs (optional)

Windows Server 2008 or Windows Server 2008 R2

FIM Password Reset Portal

Windows Server 2012

FIM 2010 R2 SP1

  • Uninstall FIM Password Reset Portal

  • Upgrade operating system to Windows Server 2012

  • Install FIM Password Reset Portal

SQL Server 2008

FIM Sync database

SQL Server 2012

FIM 2010 R2 SP1

  • Upgrade FIM Sync to FIM 2010 R2 SP1

  • Stop FIM Sync

  • Backup Database [in case rollback needed]

  • Upgrade SQL to SQL Server 2012

  • Start FIM Sync

SQL Server 2008

FIM Service database

SQL 2012

FIM 2010 R2 SP1

  1. Upgrade FIM Service servers to FIM 2010 R2 SP1

  2. Stop FIM Service on all servers

  3. Backup Database [in case rollback needed]

  4. Upgrade SQL to SQL Server 2012

  5. Start FIM Service on all servers

Windows Server 2008 or Windows Server 2008 R2

FIM Service

Windows Server 2012

FIM 2010 R2 SP1

  1. Uninstall FIM Service

  2. Upgrade Windows to Windows 2012

  3. Install FIM 2010 R2 SP1 Service

Windows Server 2008 or Windows Server 2008 R2

FIM Sync

Windows Server 2012

FIM 2010 R2 SP1

  • Uninstall FIM Sync

  • Upgrade Windows to Windows Server 2012

  • Install FIM 2010 R2 SP1

Windows Server 2008 or Windows Server 2008 R2

Password Change Notification Service

Windows Server 2012

FIM 2010 R2 SP1

  • Upgrade FIM Sync to FIM 2010 R2 SP1

  • Uninstall PCNS

  • Upgrade Windows to Windows Server 2012

  • Install PCNS

System Center Service Manager 2010 with Windows Server 2008 and SQL Server 2008

FIM Reporting

System Center 2012 Service Manager with Windows Server 2008 and SQL Server 2008

FIM 2010 R2 SP1

  1. Upgrade FIM to FIM 2010 R2 SP1

  2. Upgrade System Center to System Center 2012

  3. Run PowerShell Scripts

Outlook 2007 or Outlook 2010

Outlook Add-in

Outlook 2013

FIM 2010 R2 SP1

  • Uninstall FIM client components

  • Upgrade to Outlook 2013

  • Install FIM 2010 R2 SP1 client components

Windows XP, Windows Vista or  Windows 7

FIM extension for Windows [SSPR]

Windows 8

FIM 2010 R2 SP1

  • Uninstall FIM client components

  • Upgrade to Windows 8

  • Install FIM 2010 R2 SP1 client components

Pre-Installation and Upgrade of the FIM CM

The following table lists examples for typical FIM CM upgrade scenarios:

Current Environment Target Environment

Windows Server 2008 R2 SP1 + FIM R2 RTM Server

Windows Server 2012 + FIM R2 SP1 Server

Windows Server 2008 R2 SP1 with SQL Server 2008

Windows 2012 Server with SQL Server 2012

Windows Server 2008 R2 SP1 CA

Windows Server 2012 CA

Windows Server 2008 R2 SP1 DC

Windows Server 2012 DC

Windows 7 Client + FIM R2 RTM Client

Windows 8 Client + FIM R2 SP1 Client

Windows 7 Client + FIM R2 RTM Bulk Client

Windows 8 Client + FIM R2 SP1 Bulk Client

To upgrade to FIM R2 SP1, you should follow the following steps:

  1. Upgrade all FIM CM components on all computers to FIM CM SP1.

  2. Upgrade the SQL Server version on SQL Server computer.

  3. Upgrade the operating system on the computers that are domain controllers and the CA.

  4. Upgrade the operating system on the FIM CM server.

  5. Upgrade the operating system on the SQL Server computers (if desired).

  6. Upgrade the operating system on the computers that have the FIM CM client installed.

  7. Upgrade the operating system on computers that have the FIM CM Bulk client installed.

Enabling Support for IE 10 as Browser

To enable support for IE 10 as browser for the FIM portal, the following .NET hotfixes are required on the FIM portal computer:

Outlook Add-in Deployment

There are issues in conjunction with the installation of the FIM Outlook add-in when a 32-bit Office 2013 has been installed on a 64-bit Windows computer using a “Click-To-Run” deployment method.

You can address this issue using the following steps:

  1. Create the following registry string value in the 64-bit registry hive:

    • Key: HKLM\SOFTWARE\Microsoft\Office\15.0\Outlook

    • Name: Bitness

    • Type: REG_SZ

    • Value: x86

  2. Install the Service Pack 1 for FIM 2010 R2 Add-ins and Extensions.

  3. (Optional) Install the Service Pack 1 for FIM 2010 R2 Add-ins and Extensions Language Packs.

  4. Remove the registry key created in step 1.

The add-in does not support the Office 2010/2013 side-by-side (sxs) mode.