Installation

MRE consist of just two files that needs to be present on the Synchronization Server.

• FIM.MRE.dll - This is the provisioning engine DLL file that performs the actual provisioning. This file must exist in the default Extensions directory of the FIM installation. This is also the file that should be set in Synchronization Service Manager as the Metaverse Rules Extension. Some implementations of FIM make use of Metaverse Router. This is supported with MRE.

• _Rule files (XML files) - These files contain your rules and their filename must end with the name ‘.FIM.MRE.xml’. These files contains the provisioning and deprovisioning rules and you can have as many rule files as need. Template files are included in the Sample folder of the kit. As of version 1.2.5.0, all rule files that ends with .MRE.XML are loaded. This is to support gradually removing the FIM brand from this framework.

IMPORTANT_ - This kit requires an eventlog source named 'FIM Metaverse Rules Extension' in the Application log on the FIM Synchronization Server. If the service account has enough permissions to create the log, i.e. local administrator rights, you do not need to do anything. But if you prefer to keep the service accounts permissions to a minimum, you should create the event log source prior to using the FIM.MRE.dll.

This PowerShell command creates the required event log and event source on FIM Synchronization Service computer (requires PowerShell 3.0 or higher and must run with administrative privileges) -

New-EventLog -Source "FIM Metaverse Rules Extension" -LogName Application

Then, to start using the this kit, all you have to do is copy the FIM.MRE.dll to the extensions folder on the FIM Synchronization Server. The Extensions folder is typically C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service.

• Copy FIM.MRE.dll to this directory
• Edit the *.FIM.MRE.xml files to create the rules that fit your installation and places the files in the Extensions folder as well (you can specify an alternative path for the rule files - see below)
• Enable provisioning under Tools -> Options in the menu of the FIM Synchronization Service Manager.
• Select "Enable metaverse rules extension" and click 'Browse' and select 'FIM.MRE.dll' as the rules extension
• Select "Enable Provisioning Rules Extension" to put FIM.MRE.dll into action
• Off you go - do some synchronization and see your rules come into play

NOTE - if you edit the rules files *.FIM.MRE.xml, you should restart the FIM Synchronization Service to make sure the framework picks up the latest rule files.

To restart the service, use this PowerShell command line on the FIM Synchronization Server -

Get-Service FIMSync* | Restart-Service

Alternative path to rule files

If you prefer to, you can store the rule files (*.FIM.MRE.xml) in an alternative path as oppose to using the default Extensions folder of your Synchronization Service installation. MRE will look by default in the Extensions folder for rule files unless you specify otherwise.

To set an alternative folder for MRE to read rule files, add the following registry value under HKLM\SOFTWARE\Granfeldt\FIM\MRE -

RuleFilesAlternativePath (REG_SZ): , i.e. C:\Data\RuleFiles