Last week the Product group announced the new name for FIM and MIM’s the word Microsoft Identity Manager.
Of course as a good futurist I had made enough guesses that I got this one right, even though as an honest man I must admit I also had it wrong – Azure is not part of the name.
Fortunately, they didn’t go with APE nor AILMENT, nor MIME, nor MIAMI, nor MICE, nor MAIM, nor WIMP. MIM’s the word!
In Part 1 of How to import the Domain attribute into the FIM Portal I provided you the simple technique for the single domain forest, and the technique that works although is a bit unwieldy – that of looking at the first 41 characters of the object’s SID and using a lookup table through nested IIF statements and this doesn’t .
What if there was a simpler way?
What about using the Domain Component option in the attribute flow?
So by now all of you know that understanding Windows Workflow Foundation is going to be quite helpful in implementing ILM 2.
Having lived 9 of the last 12 months in Redmond, WA, I now understand a lot more about sprinkling
So I thought I would provide a sprinkling of understanding about Windows Workflow Foundation: a categorization of the built in workflows.
| Cateory | Activity | Composite | Notes |
|---|---|---|---|
| Conditional | Invoke Web Service | ||
| Conditional | Conditional Activity Group | ||
| Conditional | IfElse | ||
| Conditional | Policy | Akin to a switch statement or Select Case | |
| Conditional | While | ||
| Custom | Code | ||
| Error | Compensate | ||
| Error | Fault Handler | ||
| Error | Throw | ||
| Flow | Delay | ||
| Flow | EventDriven | ||
| Flow | Listen | X | 2+ event driven |
| Flow | Parallel | x | 2+ sequence for each |
| Flow | State | ||
| Flow | Sequence | X | |
| Flow | SetState | ||
| Flow | StateInitialization | X | |
| Flow | Suspend | ||
| Flow | Terminate | ||
| Flow | Transaction Scope |
http://feeds.feedburner.com/IdentityLifecycleManagerilmBestPractices
