Book Image

Microsoft Forefront Identity Manager 2010 R2 Handbook

By : Kent Nordstrom
Book Image

Microsoft Forefront Identity Manager 2010 R2 Handbook

By: Kent Nordstrom

Overview of this book

Microsoft's Forefront Identity Manager simplifies enterprise identity management for end users by automating admin tasks and integrating the infrastructure of an enterprise with strong authentication systems. The "Microsoft Forefront Identity Manager 2010 R2 Handbook" is an in-depth guide to Identity Management. You will learn how to manage users and groups and implement self-service parts. This book also covers basic Certificate Management and troubleshooting. Throughout the book we will follow a fictional case study. You will see how to implement IM and also set up Smart Card logon for strong administrative accounts within Active Directory. You will learn to implement all the features of FIM 2010 R2. You will see how to install a complete FIM 2010 R2 infrastructure including both test and production environment. You will be introduced to Self-Service management of both users and groups. FIM Reports to audit the identity management lifecycle are also discussed in detail. With the "Microsoft Forefront Identity Manager 2010 R2 Handbook" you will be able implement and manage FIM 2010 R2 almost effortlessly.
Table of Contents (21 chapters)
Microsoft Forefront Identity Manager 2010 R2 Handbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
8
Using FIM to Manage Office 365 and Other Cloud Identities
Afterword
Index

CM Management Agent


So what about connecting FIM CM to FIM Synchronization and FIM Service?

If you look at your FIM Synchronization Service, you will find that you can create a Management Agent for Certificate Management. This MA is used to connect to FIM CM.

This MA is not used very often, since it is basically not that good. In FIM CM, the ID used for users is AD GUID. So in order for us to join our users with the objects in FIM CM, we need the objectGUID attribute from AD in our MV. And for some unknown reason the MA is preconfigured to Join using guid.

The usage of this MA, as I have said, is limited. If you initiate a request using this MA, the request would end up as pending in the FIM CM portal and the user would still be required to go to the FIM CM portal to finalize the request.

I have also used this MA to import the status from FIM CM into FIM, in order to gather the current status of FIM CM requests into FIM, and then use the FIM Service to act in case the request or profile show...