Hi all, I have problem with inbound and outbound syncronization, I can create AD user ID from FIM portal but when I create user ID from Active directory user and computer, it can not be imported to FIM database. display name and other attribute is blank. there is no error message during syncronization process. I have follow two guidance : http://technet.microsoft.com/en-us/library/ff686263(v=WS.10).aspx and http://technet.microsoft.com/en-us/library/ff686264(v=WS.10).aspx That document only works for single syncronization rule, but if I use it for inbound and outbound it doesnot works, Please Help

Is the object you created in the AD imported in the connector space? Where are you missing the attributes? Within the FIM Portal? if that is the case you need to add "export attribute flows" within the FIM ma that populate the attributes that you are missing for instance displayname. Can you find the user within the metaverse? if the attributes within the metaverse are missing then you need to add import attribute flows within the AD MA Need realtime FIM synchronization? check out the new http://www.traxionsolutions.com/imsequencer that supports FIM 2010 and Omada Identity Manager real time synchronization!

Is the object you created in the AD imported in the connector space? Where are you missing the attributes? Within the FIM Portal? if that is the case you need to add "export attribute flows" within the FIM ma that populate the attributes that you are missing for instance displayname. Can you find the user within the metaverse? if the attributes within the metaverse are missing then you need to add import attribute flows within the AD MA Need realtime FIM synchronization? check out the new http://www.traxionsolutions.com/imsequencer that supports FIM 2010 and Omada Identity Manager real time synchronization!

The problem is that the object created in AD is exported to FIM, but FIM attributes (e.g. DisplayName) have higher precedence in the metaverse, so what you see (the empty value) is FIM's value for the attribute. Maybe you could try to set equal precedence for the attributes, but I'm not sure that would work (I never tried it myself). However, why do you want to allow user creation directly in AD? Wouldn't it be better if the users were created only from one or two sources which are NOT Active Directory directly? Cheers, Paolo Paolo Tedesco - http://cern.ch/idm

The problem is that the object created in AD is exported to FIM, but FIM attributes (e.g. DisplayName) have higher precedence in the metaverse, so what you see (the empty value) is FIM's value for the attribute. Maybe you could try to set equal precedence for the attributes, but I'm not sure that would work (I never tried it myself). However, why do you want to allow user creation directly in AD? Wouldn't it be better if the users were created only from one or two sources which are NOT Active Directory directly? Cheers, Paolo Paolo Tedesco - http://cern.ch/idm