We have two generic services that are part of a Windows Failover Cluster role. We would like to have one of the services go to an Offline state upon a failover so that we can then start it manually when we choose to. Optionally, we would like to put the service in an Offline state before performing a planned failover and have the service remain Offline after the failover. It appears that the cluster will attempt to start all services in a role no matter what. I assume this is the intended behavior, but I wanted to verify this is the case.
If so, I think my best option is to split one of the services into its own role so that I can fail it over independently, but I'd be interested in other solutions if anyone has a similar situation.
Thanks,
Blaine