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

Managing users in a phone system


The phone system at The Company is a simple SQL table in the eyes of FIM. The basic idea is that all employees, but not contractors, should be in the phone system and FIM is responsible for creating them.

Once the users are created in the phone system, this system is responsible for entering phone and office location data, which is then imported back into FIM.

I have earlier stated that I tend not to mix inbound and outbound data flow directions in the same synchronization rule, but the phone system is one where this is possible. Why? Well, because it is very simple and the users are completely managed by FIM.

To manage the users in the phone system, we need to create the MA for the phone system, to begin with. Since we have walked through the steps on how to do this before, I will just point out some basics:

  1. Management Agent type is SQL Server and I give it the name Phone.

  2. Using a SQL alias of dbPhone, I connect to the database—CompanyIdM—and table—PhoneData...