Operational problems are caused by the present behaviour whereby the Event Broker scheduler ALWAYS starts when the Event Broker service is restarted (either explicitly or on a server reboot). This has caused a number of problems over the past week, and we are being forced to disable the Event Broker service while performing some FIM data reload scenarios. This is a usability issue ... and more of a problem in a production/migration scenario than say in DEV.
The following page should be deleted following completion of this issue:
EB31:Issues with FIM Event Broker Scheduler starting following a service restart
Customer support service by UserEcho