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

Configuring sets for user management


Organizing objects in MIM Service is done using a set; all MPRs use a set to work.

Note

Sets are not groups. Sets are only used within MIM Service to organize managed objects, while groups are a type of managed object that can be synchronized with other systems.

It is common to have different employee types managed differently. In order to manage them differently, we would first group them into different sets.

If we look at all the sets that we get out of the box, you will find that many of them have a Display Name that you can relate to, and you can choose to reuse them or create your own. There are some predefined sets that we can use, such as All Contractors or All Full Time Employees. Take a look at the All Full Time Employees set, and notice that the criteria specifies a Full Time Employee. In our scenario, Employee Type, as defined by the HR system, is not Full Time Employee but the Employee value. Sure, we could change the data directly in the HR system...