My run cycle consists of a batch file with a dozen or so run profiles which are required to complete what we class as a run cycle. Currently I'm running it manually but now need a solution where it runs automatically. My main goal is to have propagation of entities take as little time as possible, so ideally as soon as the cycle is complete, it should start another one. I guess that's the only way to have timely propagation times? I'm going to experiment with Windows scheduled tasks to run the batch file, but I wondered how others have approach this? Is there a more efficient system, i.e. can we only do a run cycle if there are changes in FIM (FIM is our authoratative datasource, so we only really care about FIM's changes).

I've been asking exactly this same question since MIIS days :). Check out this thread on exactly this subject ... there IS an affordable commercial shrink-wrapped product that provides this feature amonst others. Refer to my company's website for more details, and email me direct if you need.Bob Bradley, www.unifysolutions.net (FIMBob?)

I found a vb script on the FIM Ramp-Up site here: http://technet.microsoft.com/en-us/ff793470.aspx In subject 8, "Other considerations" I took the virtual lab and there is a good example for writing your own scripts.

I found a vb script on the FIM Ramp-Up site here: http://technet.microsoft.com/en-us/ff793470.aspx In subject 8, "Other considerations" I took the virtual lab and there is a good example for writing your own scripts.

I'm currently using the scheduled tasks - powershell approach. Got two "run cycles" scripts: one who does delta runs, one who does full runs. The powershell code is based on one of the scripts posted in the scriptbox here: http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/c7e204be-05b4-40e1-bf95-e0191a76ece3 I'm still playing around, but I think I'll do delta's every 2 hours and once a full every evening. Still playing around with it though. If you really want to have an optimum propagation time, you should look into running your import/export profiles in parallel, combined with the synchronizations which run sequential (never run them together on multiple MA's).http://setspn.blogspot.com

Take a look at the IMSequencer. - you can visually and intuitively schedule your ILM \ FIM management agents without using script languages like VBScript and still have all the advantages and power of a Windows GUI - you have an overview what identity data is being provisioned and synchronized in your systems - you can see at what time your ILM \ FIM management agents will run - a tool that protects your connected systems from getting corrupted if your source systems provides incorrect datayou got a tool that protects your connected systems from getting corrupted if your source systems provides incorrect data - flexibily combining different kind of steps - send notifications - intuitive logging and reporting - lots more interesting features... Try it out! Drop me a mail if you need more information. HTH, Peter Peter Geelen (Traxion) - Sr. Consultant IDA (http://www.fim2010.be) [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or "Helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

Thanks all, I'll look into your suggestions :) Peter, I've asked them for a quote, it looks like something that would work well for us as our MA count grew, but I fear the price!

Amethi ... the IMSequencer and Event Broker are 2 totally different approaches to "orchestrating" your FIM Sync Server or ILM/MIIS server ... one is event-driven and one is not, but other than that the features are going to be very similar. Try both out and see for yourself. For the Event Broker, please read the write-up on our website and then contact support@unifysolutions.net for a free 30 day trial.Bob Bradley, www.unifysolutions.net (FIMBob?)

Just wanted to chip in with my "simple" solution - a skeleton for a VBScript - you could build in a loop easily http://granfeldt.blogspot.com/2010/03/scheduling-fim-2010-without-masequencer.html Regards, SorenRegards, Soren Granfeldt http://granfeldt.blogspot.com

Soren ... a slight adjustment to your scipt will allow you to avoid hard-wiring guids, which will change when you migrate from one environment to another ... i.e. for the "FIM MA" the following line ... Set FIM = Service.ExecQuery("select * from MIIS_ManagementAgent where Guid = '{2B299011-65BA-4DD5-9A59-9BAF8A5C5332}'") ... would become ... Set FIM = Service.ExecQuery("select * from MIIS_ManagementAgent where Name = 'FIM MA'")Bob Bradley, www.unifysolutions.net (FIMBob?)

Hi, Bob.. Valid point - and actually I've already done this at a few customer sites (even though names can change as well :-)); however, in some certain situations, I like to make sure that the script will fail and not run if taking out the environment. Happy christmas, SorenRegards, Soren Granfeldt http://granfeldt.blogspot.com