Hi thereI´m provisioning AD users with FIM 2010 RC1 from Oracle 10g, but when I change the name, last name or some info in my Oracle DB and I ran the run profiles, I cant see the changes in my AD user.Example Current User in AD Change in OracleFirst Name: Jane JohnLast Name: Connors SmithDisplay Name: Jane Connors Account Name: jconnorsEmail: jconnors@kichitan.comAfter Run profiles and SyncUsers container you could see (CN value): John Smith as the user name but, User propertiesFirst Name: John Last Name: Smith Display Name: John Smith Account Name: jsmithemail: jsmith@kichitan.comAs you can see the CN, AccountName and email address arent updated.Somebody has ideas of this behavior. Cheers

Hi, maybe a silly question, but did you check the "Initial Flow Only" for some of those attributes? I don't know about account name and email, but I think that the CN should be configured for initial flow only, since it's part of the dn, which is an anchor attribute for AD. Cheers, PaoloPaolo Tedesco - http://cern.ch/idm

Please post your synchronization rule configuration.You can use the FIM Object Visualizer to create a report of your configuration.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Hi Markus this is the configuration of my syn rule.AD User Synchronization Rule Data Flow direction: Inbound and outbound Relationship: employeeid a employeeid Outbound accountName => sAMAccountNamedisplayName => displayNameemployeeID=> employeeIDemployeeType => employeeTypefirstName => givenNamelastName => snCN=+firstName+ +lastName+,OU=FIMObjects,DC=Fabrikam,DC=com =>dn (Initial Flow) 512=>userAccountControl (Initial Flow) P@ssW0rd=>unicodePwd (Initial Flow) Inbound objectSid <= objectSiddomain_name <= domainCheers.

HelloYou should have two flows for dn:CN=+firstName+ +lastName+,OU=FIMObjects,DC=Fabrikam,DC=com =>dn (Initial Flow)CN=+firstName+ +lastName+,OU=FIMObjects,DC=Fabrikam,DC=com =>dn (Not Initial Flow checked)

HI JrvinenThnks a lot tha works great.

FIM 2010. I created two DN flows and the second one isn't being applied. I created custom attributes in the metaverse, and the portal. One is distinguishedname and the other mv_distinguishedname. I am building the DN in SQL and just flowing a static DN through the all the MA's. It is easier and offers more flexibility in SQL queries to set the DN. The original distinguishedname is set to initial flow only and the mv_distingusihedname isn't set to initial flow only. Any ideas. I thought I figured it out as I was typing and I needed to add the mv_distinguishedname the MPR Synchronization: Synchronization account controls users it synchronizes: But that didn't do the trick