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

FIM Service and Metaverse


We now have a scenario where we create distribution groups in FIM and import security groups from HR. So, how do we configure this in respect to the FIM Synchronization Service and the Metaverse?

Well, first of all, we need to configure the attribute flows on the FIM Service MA.

As you can see, we will need to both import and export many attributes regarding group objects between FIM Service and the Metaverse.

We are using the same Metaverse object type, group, in our inbound synchronization rule for orgUnit, from the HR system. This will cause a precedence problem in the Metaverse.

We need to go through all attributes with multiple import flows and make sure the precedence is correctly configured. In this case, we want the HR system to have higher precedence in order for FIM Service to accept values from it. There is no conflict in the other direction, since no groups managed in FIM should also be managed in HR.

Note

If you change and import new configurations of FIM...