Yeah George, I've been trying to get an SSRS instance tied into my Staging database.

I jumped on a RDC session to my Node02 machine and ran the SQL Server setup program there.

In the SETUP.exe program:

Installation / New Installation or add features to an existing installation

It installs some setup support files, then it prompts for an installation type. My choices are "New installation or Add shared features" or "Add features to an existing instance of SQL Server 2008 R2."

When I select to "Add features to existing..." it displays a pull-down with the name of my cluster in it, not the individual node that I'm working on. It doesn't allow me to change it or to type in the name of the machine (Node02) by hand. I go with the instance name that is there, and choose Report Services. Next it prompts me for some Service account info. The next panel is Reporting Services configuration panel, and I choose "Install, but do not configure the report server."

At this point, SETUP.exe rolls through some Installation configuration rules, and all pass except for one titled "Existing clustered or cluster-prepared instance" The error text states: "The instance selected for installation is already installed and clustered on computer NODE02. To continue, select a different instance to cluster."

I think that what is hosing up the install is that I cannot specify the specific Node02 name...instead it shows the cluster name as the instance I'm trying to install into.

I figure I'm going to have to take Node02 out of the cluster some-how to get RS installed on it. Not having ever done this before, I've got questions about how to do this. I see to have a couple of choices in Failover Cluster Manager interface: Pause the node, Evict the node, or I can stop the cluster service. (...or maybe there is another way?)

Does this make it clearer? I'm not trying to implement high availability of reporting services. Node01 is already running an instance of RS tied to a production db...what I'm trying to do here is to install RS on Node02 and tie it to a Staging db.