It's out, the docs are updated, now get to work!
- ILM Best Practices: ILM 2 RC 0 is here!
- ILM Best Practices: Other interesting changes in ILM RC0
- Bobby and Nima's ILM Blog: Announcing Identity Lifecycle Manager "2" Release Candidate
I am certainly glad to see the "managed:" moniker go away but the requirement for SQL Server 2008 has me concerned. Will adoption of ILM 2 be stalled because of this requirement?
2 comments:
Does ILM support synchronous provisioning, with retry, etc..?
If I want to require update AD, then after complete, get unique id from AD create user, then create a user in MSCRM, once complete, take another ID, create user in SQL, etc... synchronous and dependent, with retry etc..
I understand i add user to metaverse, MA's take that difference/delta, and provision out, how can i get status, and possibly get attribute from that process?
thanks!
Yes, using a feature in ILM 2 called a DetectedRulesEntry. When using an Outbound Sync Rule you can select one of the attribute flows to "use as existence test". Checking this box creates a DetectedRulesEntry object once the attribute in question has been exported and then confirmed on the next import. You can then attach policy to the existence of this object to trigger the next step in your process.
Post a Comment