Book Image

Microsoft Identity Manager 2016 Handbook

By : David Steadman, Jeff Ingalls
Book Image

Microsoft Identity Manager 2016 Handbook

By: David Steadman, Jeff Ingalls

Overview of this book

Microsoft Identity Manager 2016 is Microsoft’s solution to identity management. When fully installed, the product utilizes SQL, SharePoint, IIS, web services, the .NET Framework, and SCSM to name a few, allowing it to be customized to meet nearly every business requirement. The book is divided into 15 chapters and begins with an overview of the product, what it does, and what it does not do. To better understand the concepts in MIM, we introduce a fictitious company and their problems and goals, then build an identity solutions to fit those goals. Over the course of this book, we cover topics such as MIM installation and configuration, user and group management options, self-service solutions, role-based access control, reducing security threats, and finally operational troubleshooting and best practices. By the end of this book, you will have gained the necessary skills to deploy, manage and operate Microsoft Identity Manager 2016 to meet your business requirements and solve real-world customer problems.
Table of Contents (22 chapters)
Microsoft Identity Manager 2016 Handbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Managing users in a phone system


A phone system could be a simple SQL table. The basic idea is that all employees should be in the phone system, and MIM is responsible for creating them. We discuss this simple example to show you how to add additional data from a secondary system to an identity created by a system configured for Metaverse projection.

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

To manage the users in this SQL-based phone system, we need to create the MA. Since we have walked through the steps on how to do this for our HR system, we will point out some basics:

  1. The Management Agent type would be SQL Server, and we give it the name Phone. Using an SQL alias of dbPhone, we connect to the Phone database and the PhoneData table containing the phone data.

  2. Next, we set the ID column as anchor and the Object Type as person:

  3. MIM will manage the users in the phone system, and...