Geoff,

I pinged Allan for more details. Here is his reply, HTH:

SSAS is not really recommended to be clustered for a few reasons, not the least of which is that it is not cluster aware. It is just a generic application. It definitely should never be installed at the same time as an FCI and be in the same resource group/role with it. A clustered SSAS installation should be in its own group. I hope that’s what you have if you’ve clustered SSAS.

You need to be careful on a cluster because services should only be restarted using the cluster cmdlets against the role (if everything) or the specific resource(s), so the Restart-Service thing here would potentially break things and should not be used for clustered SSAS. The name portion where Tom goes against the name needs to be checked so it hits the network name for the SSAS install, not any local name on the node otherwise it won’t work. I’m thinking this script will work well for standalone installs of SSAS, not so much for clustered without modifications and testing.

As an aside, A/P and A/A are not proper terms. http://www.sqlha.com/once-more-with-feeling-stop-using-activepassive-and-activeactive/

Well, here’s the WP on clustering SSAS: http://msdn.microsoft.com/en-us/library/dn736073.aspx, and in there (p58) Allan Hirt says “use powershell”, so I’d tell you that my script should be OK, but I really don’t know for certain without testing it against your configuration.