Maqsood Bhatti - iDENTITY

If during sync if you have your custom attributes defined in your FIMMA's "Configured Attribute Flows" and if those attributes HAVE values, you could come across the error on Export run as "failed-creation-via-web-services"! Well.. When you extend the FIM2010 Schema with some of custom attributes binded to the Users resource, don't forget to edit the MPR ( Synchronization: Synchronization account controls users it synchronizes ) first!!!. This is under the "Target Resource/select specific attribute" for MPR(Synchronization: Synchronization account controls users it synchronizes), just add your custom attribute..

Okk... finally I have now installed FIM2010 after doing lots of programming excercises on ILM 2007 software.. my first try was to setup a Novell eDirectory Management Agent in FIM2010... uH... It really didn't work... LDAP traces on the Novell Directory shows that FIM2010 is asking for something here LDAP : New cleartext connection 0x456d5c0 from FIMIDIOT:21575, monitor = 0x684, index = 1 LDAP : DoBind on connection 0x456d5c0 LDAP : Bind name:**********, version:3, authentication:simple LDAP : Sending operation result 0:"":"" to connection 0x456d5c0 LDAP : DoSearch on connection 0x456d5c0 LDAP : Search request: base: "" scope:0 dereference:0 sizelimit:0 timelimit:0 attrsonly:0 filter: "(objectClass=*)" attribute: "vendorVersion" LDAP : Sending search result entry "" to connection 0x456d5c0 LDAP : Sending operation result 0:"":"" to connection 0x456d5c0 LDAP : DoUnbind ...

Hmm... Microsoft Identity Manager 2010 is out.. but i really wanted to see how the new version is better then its older versions... i have read lots of documentation about FIM2010 and its declarative programming capabilities, MPRs (Management policy rules), workflows, Sets, Group etc, so before touching the fancy parts, i decided to dig into first how the sync-engine or as it previously called MIIS works before doing hands-on with the fancy FIM2010 and the sharepoint based user portal.. Going back to its earlier version and doing hands-on was necessary for me, since FIM2010 documentation always referred the "Classic-rules" as the more powerful then the declarative rules/programming in FIM2010. So i wanted to experience the power into Microsoft IdM before touching the declarative programming(less-power'd) stuff in FIM2010. Having already worked with event-based IdM products such as nOvell identity manager, i was excited to work with the state-based systems such as FIM2010....