The Complete Synchronization Process – Part 4: Delta/Full Import/Synchronization Explained

In “The Complete Synchronization Process – Part 1: New User Synchronization”, we covered the complete synchronization process as it relates to new objects.In “The Complete Synchronization Process – Part 2: Existing User Synchronization”, we stepped through the sync process for modifying a preexisting user object. In “The Complete Synchronization Process – Part 3: Joins”, we…

5

The Complete Synchronization Process – Part 3: Joins

In “The Complete Synchronization Process – Part 1: New User Synchronization”, we covered the complete synchronization process as it relates to new objects.In “The Complete Synchronization Process – Part 2: Existing User Synchronization”, we stepped through the sync process for modifying a preexisting user object. In both of those, we mentioned joins and the sync…

4

The Complete Synchronization Process – Part 2: Existing User Synchronization

In “The Complete Synchronization Process – Part 1: New User Synchronization”, we covered the complete synchronization process as it relates to new objects. To add to that, I’d now like to discuss the complete synchronization process as it relates to pre-existing objects. As you can see below, we have the same basic environment (SQL data…

13

The Complete Synchronization Process – Part 1: New User Synchronization

Let’s take a deep-dive look at the actual synchronization process. For the purpose of this example, we will keep our environment very simple. For the time being, forget about the FIM portal or any other data sources. In this scenario, we will have a SQL data source (HR, for example) and an Active Directory. The…

6

Provisioning a Mail Enabled User

I’d like to cover something that I get asked about a lot: provisioning mail enabled users with FIM. In this example, I’m going to focus more on the FIM pieces and much less on the Exchange piece as I am in no way an Exchange guy. (Heck, I’m just barely a FIM guy.) As such,…

1