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

Rule extension logging


If you have a rules extension, it may be useful to utilize logging. You can create a log file for a rules extension by adding the \Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions\Logging.dll reference to your Management Agent project:

Then, within your rules extension code, add a logging event similar to this:

Logging.Log("Error in account: " + csentry.DN.ToString(), True, 2)

The three parameters are as follows:

Logging.Log(logMessage, addTimeStamp, loggingLevel)

Here is what they mean:

  • logMessage: This is a string message to write to the log. In the preceding example, we concatenate a custom string with a string value of the connector space's DN.

  • addTimeStamp: This is a Boolean value that determines whether a time stamp should be included.

  • loggingLevel: This is the logging level at which the message is written to the log. The log file entry is only written if loggingLevel is equal to or greater than the value set in the logging...