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

The SCSM ETL process


The SCSM ETL process is broken into several steps, which we will outline here. To understand this, we will first start with the MIM service. As we have discussed previously in this chapter, we executed the initial job and watched this job get created in the portal. Now, we will explain what is happening under the hood so that it can help you troubleshoot and manage the reporting system.

The steps to move the data are defined as follows:

  • Initial: This process reads data directly from the Service Objects database.

  • Initial-Partial: This process allows for the movement and configuration of the schema attribute.

  • Incremental: This process runs every 8 hours, or as set by the SQL agent job. This ETL job reads the export log table only.

When you first kick off reporting the Initial job, this job extracts data from the [fim].[Objects] table. So, if you're just turning on Reporting but you have had MIM up for a while and have a large set of data, your initial sync could take a bit...