Export (0) Print
Expand All

Installing the FIM CM Server

Updated: November 8, 2010

Applies To: Forefront Identity Manager Certificate Management

You can install FIM CM and the CA on the same server or on separate servers. Since installing the FIM CM Server with the CA is rare, the steps here will cover the situation of keeping the components separate. However, if you do install them on the same computer, there are several configuration steps that you will not need to perform. Steps that you can skip by collocating these server roles will be mentioned in the relevant sections in this guide.

To install the FIM CM Portal and Forefront Identity Manager CM Update Service

  1. From the FIM CM installation CD, right-click setup and then click Run as administrator.

    Certificate Management.msi is located at media\certificate management\x64\, where media is represents the drive or share of your FIM CM installation media.

  2. On the Welcome to the Installation Wizard page, click Next.

  3. On the Certificate Lifecycle Manager License Agreement page, read the license terms, select the I accept the terms in the license agreement check box, and then click Next.

  4. On the Product Key page, type a valid product key, and then click Next. If you do not enter a valid product key, the installation software installs FIM CM as an evaluation copy, which you can use for 180 days.

  5. On the Custom Setup page, you can determine whether you want to install all the FIM CM components to install on a single server or to separate the CA from the FIM CM Server. However, if the server on which you are installing the software is not already a CA, then you will not have the option of installing the CA related files. If you want to prevent CM CA Files from installing on a CA, on the Custom Setup page, in the list next to CM CA Files, select This feature will not be available.

    noteNote
    The default installation path is <ProgramFiles>Microsoft Forefront Identity Manager\2010. To change where you install the files, click Change, select a different location, and then click OK.

  6. On the Virtual Web Folder page, you can leave the default name CertificateManagement or specify a different name for a virtual Web folder.

    noteNote
    1. This folder will be the address for the FIM CM Portal. The default virtual Web folder name is CertificateManagement. If you change the name of this folder, realize that other documentation may refer to this virtual folder by its default name of CertificateManagement and that you may need to translate the changed virtual folder name from the default in order to follow further instructions and discussions in the future.

    2. If an IIS 7 Role Service was missing or you did not have the appropriate permissions to install the server, you would see an installation error. The error message would read Installation Error: The wizard was interrupted before the Forefront Identity Manager Certificate Management could be completely installed. Your system has not been modified. To complete the installation process at another time, please run setup again. See Prepare IIS 7 for the specific components that need to be installed.

    noteNote
    This folder will be the address for the FIM CM Portal.

  7. On the Ready to Install the Forefront Identity Manager Certificate Management page, click Install to begin installation.

    noteNote
    If the FIM CM Portal IIS virtual directory is not configured to require SSL communications, you will receive a warning indicating that during installation. You can require SSL communications on the CertificateManagement virtual directory through the Internet Information Services (IIS) Manager. For specific instructions about how to configure SSL communications on IIS 7, see Require Secure Sockets Layer (IIS 7) (http://go.microsoft.com/fwlink/?LinkId=186305).

  8. On the Forefront Identity Manager Certificate Management Installation Complete page, click Finish.

ImportantImportant
FIM CM requires a server running 64-bit Windows Server 2008 or later. The CA modules can be installed on a 32-bit Windows Server 2003 CA or on a Windows Server 2008 installation with AD CS.

Previous topic

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft