I configured an ILM Management Agent with both import and export attributes flow for the attributes accountName, displayName and domain, just to make a minimal test. I import some user objects in the metaverse from an Active Directory management agent, where I configured those 3 attributes for inbound flow, and in the rule definition I checked the 'create object in ILM' option. When I run a synchronization, the new users end up in the ILM MA connector space with the only MVObjectID attribute set, and all the other attributes empty; if I run an export, I see the new users in the ILM portal with a "(No Display Name)" caption, and no attributes. Am I doing something wrong? Has anybody seen this problem? Thanks for any help, Paolo

Dod you configure Export flows in the ILM MA for the person object? This is the most common error.Did you import from AD using Sync Rules? Do you see valued in the Metaverse?EricEric

The getting started documenation for ILM "2" includes this topic.http://technet.microsoft.com/en-us/library/cc678643(WS.10).aspxAhmadAW

Hi Eric and Ahmad, thanks for your answers. The problem was actually in the configuration of the attribute flow precedence: the AD agent had a lower priority than the ILM agent. What I don't understand is why the priority applies also during the object creation; shouldn't the ILM agent recognize that the object did not exist before and accept the initial values, even if its precedence is higher? Paolo

There are known issues with attribute precedence in RC0. The ILM MA always wants to be the most precedent every time you do a full sync when you have a Sync Rule. Some people get around it by setting equal precedence.Eric