Getting Started with Microsoft Forefront Identity Manager 2010 RC1

Getting Started with Microsoft Forefront Identity Manager 2010 RC1

Microsoft Forefront Identity Manager (FIM) 2010 RC1 represents a massive leap forward from its predecessor, Microsoft Identity Lifecycle Manager (ILM) 2007. While ILM operated strictly as a background service, FIM 2010 brings identity management directly to the foreground. It introduces a user-facing portal, a native workflow engine based on Windows Workflow Foundation, and codeless, declarative provisioning rules.

For IT pros evaluating the Release Candidate 1 (RC1) build, this guide covers the core architecture, new RC1 enhancements, and how to successfully build your first test lab environment. Core Components of the FIM Platform

To get started, you must understand how FIM divides its architecture across three core components:

FIM Synchronization Service: The evolution of the classic MIIS/ILM engine. It uses ⁠Management Agents (MAs) to pull data from external systems (like HR databases or Active Directory) into a staging area called the Connector Space. This data then merges into a single central inventory known as the Metaverse.

FIM Service: A web-service-based application layer built on top of the synchronization engine. It manages the primary object types (users, groups, sets, and requests) and evaluates security policies at runtime.

FIM Portal: A SharePoint-hosted user interface that shifts management tasks from IT staff directly to business users. Users can manage their own distribution groups, request access to applications, and update personal details. Key Enhancements in Release Candidate 1 (RC1)

Compared to earlier beta releases (such as RC0), RC1 includes several critical bug fixes, UI improvements, and foundational changes to prepare the software for its final Release to Manufacturing (RTM) build: Microsoft Learn

Forefront Identity Manager Service Overview – Microsoft Learn