All, In support we do discuss the topic of run profiles quite a bit. So i have compiled a wiki to kind of centralize the information, as well as add to it. REFERENCE: Run Profiles: http://social.technet.microsoft.com/wiki/contents/articles/12529.reference-run-profiles.aspx Additionally, I put together a wiki on automating run profiles using the script button. REFERENCE: How to automate run profiles via the script button: http://social.technet.microsoft.com/wiki/contents/articles/12528.reference-how-to-automate-run-profiles-via-the-script-button.aspx Tim Macaulay Security Identity Support Team Support Escalation Engineer

Tim - I would appreciate it if you would look at Event Broker yourself (link below) to understand our vision of how easy it can (and should) be to intuitively manage all run profile execution, together with pre/post processing, in a single web console, and do so in a non-preemptive manner to achieve near real time provisioning and sync. I understand that while many will want to take the scripting option, the more the sync config grows the more cumbersome this approach becomes, and the more unsatisfactory the result. While this is a commercial product designed to enhance both FIM and ILM/MIIS before it, what I want people to understand the philosophy behind the approach, and that it is time we stopped settling for the substandard. I should also mention that FIM continues to lose business to Oracle/Novell/IBM/etc. simply because it cannot tick the "event driven" checkbox on the feature list ... and this should no longer be the case, but will continue to be while there continues to be this lack of awareness which I am trying to address with posts like this. Thanks for your interest.Bob Bradley (FIMBob @ TheFIMTeam.com) ... now using Event Broker 3.0 for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM