Share via


FIM Reference: Portal, Password Registration Portal, and Password Reset Portal Software Requirements

We have seen quite a few Self-Service Password Reset, and Self-Service Password Registration Portal for FIM 2010 R2 cases recently.  In troubleshooting them, we have found that there are some configuration settings missed.  Here are the Software and Hardware requirements for the Self-Service Password Reset, and Self-Service Password Registration Portal for FIM 2010 R2.

For the Software and Hardware requirements for the other FIM 2010 R2 Server Components, review the following Microsoft TechNet document. (http://technet.microsoft.com/en-us/library/hh332708(v=ws.10).aspx)

FIM Portal, FIM Password Registration Portal, and FIM Password Reset Portal Software Requirements

The server or servers that host the FIM Portal, FIM Password Registration Portal, and FIM Password Reset Portal must have the following software installed:

http://sharepoint/sites/dscilm/fimblog/Lists/Photos/011913_1856_FIMPortalFI1.gifNote

If you decide to install the FIM Portal and Password Portals on different servers, the software prerequisites for both servers are the same.

http://sharepoint/sites/dscilm/fimblog/Lists/Photos/011913_1856_FIMPortalFI2.gifNote

The FIM Password Registration and Reset Portals may be installed on a server with other IIS sites.

  • The 64-bit edition of Windows Server 2008 or Windows Server 2008 R2 Standard or Enterprise

http://sharepoint/sites/dscilm/fimblog/Lists/Photos/011913_1856_FIMPortalFI3.gifImportant

When you install Windows Server 2008, do not install Windows Server 2008 Terminal Services (not to be confused with Remote Desktop). If you install Terminal Services, the FIM 2010 R2 server components do not install.

  • The .NET Framework 3.0 (Windows Server 2008) or .NET Framework 3.5.1 (Windows Server 2008 R2)

http://sharepoint/sites/dscilm/fimblog/Lists/Photos/011913_1856_FIMPortalFI4.gifNote

.NET Framework features can be installed from the Features options interface that is included with Windows Server 2008.

It is necessary to install the .NET 3.5 SP1 Framework only on Windows Server 2008. The .NET 3.5 SP1 Framework is included in Windows Server 2008 R2.

Visit the Microsoft Download Center to download .NET Framework 3.5 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=129538).

  • Windows SharePoint Services 3.0 Service Pack 2 (SP2) or Microsoft SharePoint Foundation 2010.

http://sharepoint/sites/dscilm/fimblog/Lists/Photos/011913_1856_FIMPortalFI5.gifNote

Visit the Microsoft Download Center to download Windows SharePoint Services 3.0 x64 with SP2 (http://go.microsoft.com/fwlink/?LinkID=181113) or Microsoft SharePoint Foundation 2010 (http://www.microsoft.com/download/en/details.aspx?id=24983).

http://sharepoint/sites/dscilm/fimblog/Lists/Photos/011913_1856_FIMPortalFI6.gifNote

For more information, see these installation guides: Deployment for Windows SharePoint Services 3.0 Technology (http://go.microsoft.com/fwlink/?LinkID=123878), Deployment Guide for SharePoint Foundation 2010 (http://www.microsoft.com/download/en/details.aspx?id=6841) and, Upgrading to SharePoint Foundation 2010 (http://technet.microsoft.com/en-us/library/cc303309.aspx). For a step-by-step example of upgrading from WSS 3.0 to SharePoint Foundation 2010 see Test Lab Guide: Upgrading to FIM 2010 R2.

http://sharepoint/sites/dscilm/fimblog/Lists/Photos/011913_1856_FIMPortalFI7.gifNote

If you upgrade to SharePoint 2010 prior to upgrading from FIM to FIM 2010 R2 the FIM help files will may no longer be accessible by end users. This is because of improved security in SharePoint 2010 which removes the authenticated users permissions from the FIM help files that was granted by SharePoint 2007. To fix this, re-apply the authenticated users permissions at the MSILM2 level with 'Replace all child objects..' checked

http://sharepoint/sites/dscilm/fimblog/Lists/Photos/011913_1856_FIMPortalFI8.gifWarning

If the upgrade from FIM R2 Service and Portal setup fails half-way with an error that says SharePoint 2010 app not found. Then be aware that this can occur under certain topologies when upgrading from WSS 3.0 to SharePoint Foundation 2010.

The following topology experienced this issue:

  • FIM Service and Portal on one IIS server (Server A). FIM Service DB on one SQL Server (Server B). FIM Sync Service on separate server with SQL Server (ServerC).
  • The FIM Service and Portal that users connect to are separate from the Administrator instance of the FIM Service and Portal. Both connect to the same database. A virtual name for the FIM Portal (the users instance) maps to the IIS server name.

The workaround is to add computer name and localhost as internal name on SharePoint 2010.

  • SharePoint Language Pack.

http://sharepoint/sites/dscilm/fimblog/Lists/Photos/011913_1856_FIMPortalFI9.gifNote

If you have installed Windows SharePoint Services 3.0 or SharePoint Foundation 2010 in a language other than English, you must install the appropriate Language Pack. Visit the Microsoft Download Center to download the Windows SharePoint Services 3.0 Language Pack Service Pack 2 (SP2), 64-Bit Edition (http://go.microsoft.com/fwlink/?LinkID=178266) or Service Pack 1 for Microsoft Sharepoint Foundation 2010 Language Pack (http://www.microsoft.com/download/en/details.aspx?id=26629).

  • The FIM Password Registration and Reset Portals support the following browsers:
    • Microsoft Internet Explorer 9, 8, 7, and 6
    • Other browsers which support Javascript, have cookies enabled, and support CSS 3.0 media queries.
  • The FIM Password Registration and Reset Portals are supported in production environments using https. The FIM Password and Registration and Reset Portals are supported in lab/pre-production environments using http or https.
  • The FIM Password Registration Portal is supported on IIS with Kerberos, NTLM, and/or Basic Authentication enabled.
  • The FIM Password Reset Portal is supported on IIS with Anonymous Authentication enabled.
  • The FIM Password Registration and Reset Portals may be published via a proxy, such as Microsoft Threat Management Gateway.