Once upon a time we used to be able to write Advanced Flow Rules for reference attributes. Admittedly this sometimes led to horribly inefficient code, but it was useful – particluarly when paired with FindMVEntries to lookup and then reference an existing Metaverse object.
With FIM we lost this capability, and Microsoft claim we were never [...]
Post deleted because it was a lot easier than I thought! See comments below.
There were a few FIM reporting sessions at TEC, none of which I managed to make it to, though I hope the presenters will be making their solutions generally available as they are undoubtably more correct and complete than what I’ve been doing. However a couple of people did ask that I post my method [...]
While trying to install update 241774 I got “Error 25009: The Forefront Identity Manager Synchronization Service setup wizard cannot configure the specified database. Windows NT user or group ‘mydomain\fimsync-service-account‘ not found. Check the name again.”
I’ve finally started using SQL 2008 Reporting Services in earnest to provide access to all that useful data in the FIM Metaverse. Like a good girl I’m replicating the tables to another database, instead of pointing straight at the active FIMSynchronizationService database. Here’s a simple little script that I’ve tacked on to the end of [...]
It’s actually pretty easy to query SQL 2008 from powershell.
This simple little script reads employeeID numbers from a text file and then queries the metaverse for selected attributes. The text file must have “id” as the first row, with the id numbers then listed one per line.
Why oh why does MIIS have such an insatiable appetite for transaction log space? I’m afraid I can’t answer this, but I can share a few tips.
I use a lot of SQL MAs. While ILM/MIIS is great at syncing data between directories, it really isn’t that great at calculating and comparing. As much as possible I like to do the data manipulation in SQL, and then keep ILM to what it’s best at – joins and syncs.
After exporting data to a SQL [...]
Thanks to Joe Stepongzi for pointing this one out to me: you can flow a metaverse string attribute direct to a connector space relational DN attribute, as long as the metaverse string holds a valid DN.
Function RunProfile - run a MA run profile
Sub ArchiveLog - copy import and export logs to a timestamped version, while modifying them to work with a XML stylesheet
Function ExportsPending - check if the MA has pending exports
Function DeltaImportsPending - check if a Delta table has any lines to import
Function RunSSIS – call a SQL 2005 SSIS Package
