NameLatest Version FIM Object Visualizer 6.0 Description: The FIM Object Visualizer is a community script to display and document configurable objects such as Synchronization Rules, Workflows and Management Policy Rules: Display – because the script has a UI to render your configuration Document – because you can copy a displayed configuration to the clipboard and save it to a file. The script is based on the HTA (HTML Application) framework – a framework that enables you to develop scripts that look like Windows applications without the need of writing code in Visual Studio. Important To run the script, you need a FIM server with PowerShell installed.Please read the FIM ScriptBox Read Me First prior to running this script The FIM Object Visualizer is a customizable community script to display and document configurable objects such as Synchronization Rules, Workflows and Management Policy Rules.You can use this script to document your current FIM deployment or to provide configuration information in case of a troubleshooting scenario.The script consist of two main components: Data Request Data Display The script assumes that all PowerShell scripts that are located in the Collection folder are scripts to request object information from your FIM server.When you start the script, the script code locates all these scripts and adds them to the left list box in the toolbar: To request new or update existing object information for a specific object type, select the object type you are interested in from the list box, and then click Get Objects.You can extend the number of supported object types by adding additional PowerShell scripts to the Collection folder.The second list box lists the object types for which you have already requested object information.To list the display names for an object type, select the object type from the list box, and then click Get Names: To display the configuration of an object, click the object's display name: As mentioned eelier in this post, the FIM Object Visualizer is a community tool.This means, the objective of this download is to get you started with the process of documenting your deployment; however, I expect that you will modify the components of this script.For example, if you don't like the "look & feel" of how an object type is rendered, you can easily customize it by modifying the related XSLT file. If you have questions, comments or even extensions for this script, please respond to this post. To download this script, use this link.To get to the FIM ScriptBox, use this link. Markus Vilcinskas, Technical Content Developer, Microsoft Corporation

I LOVE this tool! Great work!

I have updated the script with a new feature.In the toolbar, you will find a new button - HTML: The new HTML button enables you to copy the HTML code of an object to your clipboard.You can use this feature in your forum posts.The toolbar of the forum editor has a HTML button to open the HTML Source Editor for the post you are working on right now. In the HTML Source Editor, you can paste the HTML source code of a FIM Object Visualizer object to include the object into your post.That way, it is easy to share configuration information with the community.This feature is very helpful if you need help with an issue you have.In many cases, it is easier to provide help, if the configuration information is available.Below is an example for a Management Policy Rule: Management Policy Rule Configuration Name Administration - Schema: Administrators can change selected attributes of non-system attribute type description resources Description Administration - Schema: Administrators can change selected attributes of non-system attribute type description resources Created Time 6/25/2009 Grants Permissions True Is Disabled False Requestors and Operators Requestor Administrators Operation Modify Target Resources Before Request All Attribute Definitions After Request All Attribute Definitions Resources Attributes IntegerMaximum, IntegerMinimum, Localizable, StringRegex Cheers,Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

The most recent version supports the latest FIM version.I have also incorporated some of the FIM related reports into this script: Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

The goal of this script is to enable you to create reports of various configurations.The most recent version supports the following reports: Active Metaverse Schema Attribute Flow Precedence FIMMA Schema FIM Resource Management Policy Rules Metaverse Schema Provisioning Triple Schema Object Definitions Selected Management Agent Attributes Synchronization Rules Replication Configuration Workflows Below are some examples for what you can do with this script and also abbreviated examples Active Metaverse Schema - This report shows the inbound population of your metaverse grouped by object type: Metaverse Active Schema Configuration Metaverse object type: group Metaverse AttributeTypeMulti-valuedIndexedImport-Flows membershipLocked Boolean no no 1 membershipAddWorkflow String (non-indexable) no no 1 domain String (non-indexable) no no 1 accountName String (non-indexable) no no 1 member Reference (DN) yes no 1 type String (non-indexable) no no 1 scope String (non-indexable) no no 1 displayName String (non-indexable) no no 1 csObjectID String (non-indexable) no no 1 Replication Configuration - This report shows your active metaverse schema configuration and whether an export attribute flow rule exists on the FIM MA for each metaverse attribute 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 Attribute Flow Precedence - This report shows how each attribute in the metaverse is populated and the order: 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")) FIMMA Schema - This report shows the schema definition of your FIMMA: FIM MA Schema Object type: Group Attribute NameData TypeRequiredMulti-Valued AccountName String no no CreatedTime DateTime yes no Creator Reference no no DeletedTime DateTime no no Description String no no FIM Resource - This report shows the generic representation of an object in the FIM data store: Export Object - Person ObjectID 7fb2b853-24f0-4498-9534-4e10589723c4 AccountName administrator CreatedTime 1/20/2010 11:33:37 AM Creator 7fb2b853-24f0-4498-9534-4e10589723c4 DisplayName administrator Domain FABRIKAM DomainConfiguration 1aff46f4-5511-452d-bcbd-7f7b34b0fe14 MailNickname administrator MVObjectID {1FDD4880-9B68-4509-BAB1-AC34ABF50AC1} ObjectSID AQUAAAAAAAUVAAAAVn2Q+4bZuFuYINe99AEAAA== ObjectType Person Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

You can run the latest version of FIMOV on other computers than your FIM Server.While the data retrieval still has to happen on your FIM Server, you can work with a copy of the script that includes the data on your local workstation.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Hi Markus,On selecting either Get All Objects or Get All Reports I get an Error: Failure on making enumeration web service call...Env: FIM Visualizer version 6. Running with HTA 64-bit. Running tool on the FIM Service box, FIM Portal is on a separate MOSS 2007 server.The error screen is located at: http://fim2010.blogspot.com/2010/03/how-to-handle-new-object-types-with.htmlCheers,AB

AB, Did you ever resolve this problem? I am getting the same error, but while running one of the powershell scripts directly. Thanks! -Ryan

Ryan, I did not get the error in FIM RTM. If you still get the error in RTM, ensure you have the latest version of the script, and any constant value in the powershell script's opening few lines is correctly set. AB

Markus, After Update 1 to the FIM 2010 RTM, I can no longer use the object visualizer because any reports I do "Get Report" on, fails with telling me Error: There is no MV data object on your system! This has only happened since the upgrade. Any ideas as to why? There are no other problems with the system.

Please make sure that you have the latest version of the script and that both (FIM Synchronization Service and FIM Service) are on the same patch level. The script should work. To me, this sounds more like an issue of the patch levels. Is there anything in the event log regarding a replication issue between FIM Sync and FIM? Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

When I run this, I get the following error: "You are running your HTA in 32bit mode!"... This is running on a 2008 64bit server. Can it run on a 64bit machine?

You to use the x86 version of mshta.exe. There are two on your x64 system: c:\windows\SysWOW64\mshta.exe c:\windows\system32\mshta.exe By default it takes x64 one. I think you need the one in system32. What I do is create a shortcut next to the hta file which points to the correc mshta.exe and has the hta script as a parameter. I'll give the exact syntax here tomorrow. This topic is also covered in the FIM Scriptbox readme: http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/5a735217-66e4-492d-baa4-fdb4ba8d2196 http://setspn.blogspot.com

That's a good idea, Thomas. In addition to that, you can also start FIMOV with the FIM Object Visualizer.vbs. The VBScript starts the HTA file with the correct engine. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

FYI, this is the path I use: C:\Windows\System32\mshta.exe "C:\FIM\FIM Object Visualizer\FIM Object Visualizer.hta" Ofcourse that's hardcoded to c:\fim\... perhaps it can be optimized. Or just use on of the alternatives mentioned in the ScriptBox readme.http://setspn.blogspot.com

Thanks Markus, that worked :)