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

Installation and configuration


MIM certificate management (CM) can be used in many ways, but to show you a little bit about how we can use its basics, The Financial Company will use it to allow managers (such as Jeff) to issue smart cards to users (such as David) with the help from the Modern App. We will also configure autoenrollment for EFS certificates using the policy module to recap the accounts being used in this setup.

Extending the schema

Before we can do anything, we need to extend the Active Directory schema to support MIM CM. We will go over multiforest configurations later in this chapter under various scenarios.

Note

All schema changes in Active Directory should be planned carefully.

If we don't, the configuration wizard will stop and tell us to extend the Active Directory schema if we try to run it. As you can see in the following screenshot, the installer is reminiscent of the branding transition:

Note

Remember that all modifications to the schema require the schema admin's permissions...