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

Schema management


Very early on in our FIM deployment, we ran into discussions regarding the need for schema changes in FIM.

The default schema is, in almost every case, not sufficient and needs to be modified.

I will only give a short overview in this chapter about this, and will try to explain more in the coming chapters, as we look into the details of FIM implementation at The Company.

FIM Sync versus FIM Service schema

One of the problems with the FIM Synchronization/FIM Service system is that it holds two schemas. We have one schema for the FIM Synchronization Service database and one for the FIM Service database.

Depending on our needs, we change one or both of these schemas. Whether the attributes or objects are required within FIM Service depends on whether or not they are managed using FIM Portal, or used in some policy. If not, we do not need them in the FIM Service schema.

On the other hand, if an attribute or object type is used in a policy within FIM Service, but is never supposed...