I am having issues with Attributes not showing up within the Source and Destination Attribute lists for my Synchronization Rules. Below are a few issues/questions I am looking solutions/answers for. BTW: For attributes added to the Schema in the FIM Portal I have followed the documented process for creating the Attribute, Bindings, MPRs, etc.. After adding an attribute to a Management Agent (i.e. ADMA); the attributes do not show up within the list of available attributes in a Sync Rule (even after an iisreset on the FIM Service server) Exchange attributes are not listed within a Sync Rule I guess the trend to these questions are, how to get an Attribute to appear in the list of available attributes for a Sync Rule? Rick

Hi... You can try to refresh the schema... You did not mention it in your question. This action will bring the attributes created in portal to the Synchronization Engine Some attributes, such as the Exchange attributes must be created in the Metaverse (Person Objec Type) then you can flow these attributes from your AD to FIM2010. I Hope that it explains something to you. Cheers,***** Paulo H. Campos - So Paulo/Brasil ***** http://identitypedia.blogspot.com (in PT-BR)

Hi Rick, You also need to make sure that you define attribute flow between the metaverse attributes and the FIM MA Agent. Only those attributes showup in the Synchronizatio Rule which have attribute flows defined between the Metaverse and FIM MA. Hope that helped! Thanks & Regards, Jameel Syed Principal Consultant, fimGuru - Your window into simplified identities jameel.syed@fimguru.com - http://www.fimguru.com

To have an attribute appear you only have to select it as an attribute on the target MA (AD MA in your case). To see the exchange attributes, make sure you check them all (so they have a check box). If you do not see all attributes you are looking for make sure you select to see all attributes. If they do not turn up in the Sync Rule, then probably the sync of the configuration isn't happening. Look in the eventvwr after an error from the same time you saved the configuration on your MA. If you see an error, then the FIM MA is having issues contacting the SQL server and updating the configuration. /AndreasThis posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/copyright.htm

I appreciate your replies. I have double checked everything I think and still the Synchronization Rule Attribute List still does NOT contain the attributes. I did however check the event log on the Syncrhonization server and the FIM Service server and discovered a number of the following events on the FIMSyncrhonization Server, which looks as though its causing the attribute list problem. Log Name: Application Source: FIMSynchronizationService Date: 11/29/2009 11:26:25 AM Event ID: 6331 Task Category: MA Extension Level: Error Keywords: Classic User: N/A Computer: fimserver.mydomain.local Description: A update on the configuration of a MA or MV failed to replicate to a target connector directory that is capable of storing MA/MV configurations. As a result, the MA/MV configuration data in this connector directory is not up to date. Please correct the condition that causes the error, and triggers a resync by updating the password information of the target MA. Additional information: Error Code: 0x80230709 Error Message: (The extension operation aborted due to an internal error in FIM Synchronization Service.) Operation: Update MV Name of the MA to replicate: I attempted removing the MAs, Reinstalling Sync Service and recreating the MAs and I still have the same events. I really am running out of solutions.

Ok. The problem was resolved after completely unistalling and reinstalling FIMService and FIM Sync Service. Not a happy camper about that but it worked.

If you have come to the end of this thread and you are still having this problem, verify that FIM 2010 Update 1 has applied properly to your system. You need to make sure that the update for the FIM Service and the update for the FIM Sync engine have both applied correctly. -Jeremy