SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have code similar to what is described in this blog post to set binding redirects in owstimer.exe.config using the FeatureInstalled event; the post specifically states that this event should run on each WFE, but testing shows that it is running on one, arbitrary WFE (when the feature is deployed using stsadm or Central Admin).

I am wondering if there is perhaps some setting that can be changed to cause the event to run on every WFE, or if that blog post is just plain wrong (and if the latter, if anyone has a suggestion on a better way than manually editing the config on each WFE).

share|improve this question
up vote 2 down vote accepted

This isn't my forte but I ran across the note below on this MSDN posting; perhaps that will help.

If you wanted a job to run on all servers, including application servers, your class should derive from SPServiceJobDefinition. Pass the timer service (SPFarm.Local.TimerService) as the SPService parameter of the SPServiceJobDefinition(String, SPService) constructor.

share|improve this answer
I found this other source who also found that FeatureInstalled doesn't run on all servers, and that a timer job is the way to go, and the author of the original blog post responded to my comment saying he's found it unreliable on a retract/deploy.… – lgaud Mar 28 '13 at 16:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.