We have a 2-node 2008r2 Node and Disk Majority Cluster that works fine. We have a service that always stays in a failed state, each time the cluster fails over. The service is not important enough to make it part of the cluster, because I do not want some weird failure in this service to cause a cluster failover. Just not that important, but I would like to automate it so that after a failover, the service gets started on the new active node. I tried setting the service recovery tabs, on both nodes, to attempt to restart the service after 65 minutes on first, second, and subsequent failures and to reset that count every day. I thought this would keep the passive node to continue to retry starting the service every 65 minutes(using system account) continually so that when the cluster does failover, the service would startup within 65 minutes. Not sure why that is not working, but I am sure there is a smarter way. Can I attach a post-failover task, or batch file, etc. to be executed every time, after a cluster failover?
Thanks,
Dan
Dan Heim