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

MIM synchronization best practices


Here are some of MIM synchronization's best practices to follow:

  • Index any Metaverse object you are using for a join.

  • The account used for the MIM Synchronization service should be different from the account used for the MIM Service MA.

  • The source code for all rules extensions should be backed up and maintained in a source control program. You will need the source code if you ever need to debug a rules extension.

  • When writing a rule extension, check whether the attribute is present before looking for a value. An example is as follows:

    if (csentry["department"].IsPresent) {...}
  • We suggest performing a full import run profile and a full synchronization on each MA at least every 30 days.

  • Clear the synchronization operational run history regularly as the data will make the database grow over time and have an impact on its performance.

  • Avoid using the Joiner tool as much as possible because any explicitly joined or projected object will not honor existing or future...