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

SQL best practices


Microsoft's official best practices for FIM holds true for MIM too. These items should be implemented before releasing the system to a production environment. We have highlighted several SQL practices that we've found to solve customer problems:

  • Never modify any of the MIM database tables directly in SQL because you can corrupt the database.

  • Do not query the Metaverse table within a rules extension, workflow, or external process. Doing so creates SQL deadlock conditions that MIM would not expect.

  • Do not change SQL permissions set by the MIM installer.

  • The Synchronization service database and MIM Service database should be in their own SQL instances and on different disks, if possible.

  • Isolate the SQL data and log files on different disks.

  • Presize the SQL databases and avoid relying on SQL autogrow to improve performance.

  • Monitor SQL databases to ensure that there is enough disk space.

  • Limit the amount of memory that SQL will use if SQL is running on the same server as the sync...