MS does not official support any clustering configuration unless it is very specific in nature, that is nothing new.
That's all I am saying. I was SOLD on this thing by Microsoft and Dell for it's ability to keep juggin' along with failover. Both Claiming it was tested and "certified" The issue is, it's so touchy it almost never fails over and stays alive. And that is the sole reason I got it. Sure I can be very careful and fail the nodes over properly but what good is that? I grindge at any sort of minor error on the thing and it's Supposed to be fault tollerent. LOL. That is why you buy a cluster outside of distributing work load. I am with you on the lack of documentation. There is some more out now but back 2 years ago I had to feel my way in the dark. So I have to wonder if MS clustering 1. Sucks and 2. If other clustering models are better?

I am not on the list, but I did speak face to face with the product manager over Exchange 2003 and Outlook 2003 at a conference in Denver. It was his own words i was reiterating.

Oh and I do spend a lot of time taking it down (note not fault tolerance) and updating the firmware of a gazillion devices to keep up with it. If you don't take it down and update 1 node then chances are very good something will get corrupted so you take the whole thing down update 1 node, power it off, update the other then power the controlling node back up, then the passive and CROSS your fingers. That in my humble opinion is a waste and denys the very reason why clustering is useful outside of load balancing.

We are on the same page just a different book.