Hi,
If you want to make MSMQ higly available, most guides I have seen is about creating the Message Queuing role. That's fine.
However, I'm in a process of sorting out the other options of MSMQ in a Failover Cluster and I have done those tests:
1. Created an Message Queuing resource in existing application group, made it dependent on the disk and network name already in there. Test ok.
2. The same as above but used a separate shared disk only for MSMQ. Test ok.
3. Created a Message Queuing role and moved that one into an existing application group. Test ok.
4. The other way around from point 3; Moved an existing application group into the Message Queuing group. Test ok.
"Test ok" in my case is that it didn't produce any errors, but I have not tested the MSMQ functionality because I'm actually not an application guy, more on the infrastructure level.
Also, one thing about creating a separate role for MSMQ is that you get the "Manage Message Queuing" in the GUI, that's not the case with options 2 and 3 if you don't tweak the registry or use gwmi (http://blogs.msdn.com/b/clustering/archive/2010/01/12/9946994.aspx).
Now to my question :-)
Are any or all of those other options described valid ways to set up MSMQ i a clustered environment? What is your exeprience out there?