I know there are circumstances where you might not want all the MV attributes you brought in through an inbound sync rule going through to FIM CSBut for everything I've done so far I end up defining attribute flow rules in the inbound sync rule and then duplicating them all in the FIM MA. It's a lot of work duplicating this and making sure it's consistent if you have frequent changes, and probably more so if you had many MAs/CSesMaybe a script that either replicates attribute flow rules or at least shows a side-by-side display of sync rule attribute flow & (each) MA attribute flow for each MV attribute? Maybe an enchancement to CS Sync Rule Viewer? (Apologies if this exists already and I just don't know where)

Thanks, Capriole.I'd be interested what these cases are.The FIM CS is supposed to be a mirror of the metaverse.Have you looked at the FIM Object Visualizer yet?This script comes with a synchonization rule documenter.I'm using it all the time to create reports of my configurations.The FIM Scriptor creates reports of IAFs and EAFs for groups and users on the FIM MA.Last but not least, there is the FIM Active Schema Documentor that lists the flow population of the metaverse.So, with the Active Schema Documenter, you can create a report of everything that goes into the metaverse and the Scriptor generates a report of what goes out.I would think, the only thing that's missing is EAF support for all object types - in case of the Scriptor.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Capriole,you should take a look at the most recent version of the FIM Object Visualizer.I've just uploaded a new version that includes a replication configuration report.In this report, you can see your current metaverse population.These are the metaverse attributes that have inbound attribute flows configured. In addition to this, the report also has a coloum called "Replicated", which indicates whether an EAF flow rule exists on the FIM MA.That way, you can see whether you have populated metaverse attributes that don't flow back to FIM: Metaverse Active Schema and FIMMA EAF Configuration Metaverse object type: group Metaverse AttributeTypeMulti-valuedIndexedImport-FlowsReplicated membershipLocked Boolean no no 1 yes membershipAddWorkflow String (non-indexable) no no 1 yes domain String (non-indexable) no no 1 yes accountName String (non-indexable) no no 1 no member Reference (DN) yes no 1 no type String (non-indexable) no no 1 yes scope String (non-indexable) no no 1 yes displayName String (non-indexable) no no 1 yes csObjectID String (non-indexable) no no 1 no The "partner" report to the Replication Configuration is the Flow Precedence. This report shows who and how each metaverse attribute is populated: Metaverse Attribute Flow Configuration for group accountName, ranked Management Agent Object Type Type Source Attributes Fabrikam ADMA group sr sAMAccountName - scope, ranked Management Agent Object Type Type Source Attributes Fabrikam ADMA group sr CustomExpression(IIF(Eq(BitAnd(2,groupType),2),"Global",IIF(Eq(BitAnd(4,groupType),4),"DomainLocal","Universal"))) - type, ranked Management Agent Object Type Type Source Attributes Fabrikam ADMA group sr CustomExpression(IIF(Eq(BitOr(14,groupType),14),"Distribution","Security")) Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Thanks Markus - the object visualiser is pretty much exactly what I was looking for.