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

eparating roles


If we look at all the MIM features we are about to install, we need to understand that in theory, we might be able to put them all in one box; however, this is not practical, and in some cases, it is not even supported by Microsoft.

The example setup we will use in this book for The Financial Company can be used as a starting point.

Databases

As you will see, you need quite a few databases. Depending on the load and other factors, you can choose to install the databases locally on each box hosting a MIM feature, or choose to have them all on a central Microsoft SQL server. Alternatively, you can even mix the two approaches.

If you find that your initial approach was not optimal, don't be alarmed. Moving the databases is fully supported. In this book, we will use so-called SQL aliases when referencing the databases. One reason for this is that it makes moving the databases simpler.

System Center Service Manager Data Warehouse, required by the MIM Reporting feature, usually uses...