Hey, I've looked in the threads about RSP role in the forums and gone through the documentation and couldn't find answer to this question i have regarding setting up this role in our architecture, we have MP mixed mode that stores SCCM DB on a remote SQL 2008 server (same lan, different machine), so far so good, we have another 2 servers that have SQL Reporting Services 2005 (RSP1 & RSP2) they are available from one network name "SYSRSP" (http://sysrsp/reports/) which is load balanced by F5, these 2 servers use 1 SQL DB as their DB, that SQL is on a different SQL machine, these 2 SRSS do however know about the existence of one another as shown in this image taken from reporting services configuration tool: like i stated these server were around before our SCCM deployment for other applications that use SRSS so they have been pre-configured to be redundant (tho SRSS DB isn't redundant). that is being used for other services in the company that integrate to SQL Reporting Services, my questions are: Do i need to have sccm client installed on the machines that i designate as Reporting Services point?When i configure the role do i need to add Reporting Services point role to each of the 2 servers?If the answer to question number 2 is yes, then don't i lose the redundancy in working with the one network name "http://sysrsp/reports/"? Thanks!

I prefer to install SRS for SCCM on the same SQL server running the Site Database, and dedicated the SRS instance to SCCM. Having tried to configured multiple SC products to use the same SRS instance, it's pretty ugly. You can put the SRS database anywhere, I just like having it on the same SQL box because it's a one stop shop for SQL services. I'm also not sure what'd you gain from having more than one Reporting Service point... If you're looking for SRS redundancy, I think you get that from Failover Clustering. 1. No, you don't need to install the client before you configure the site role. 2. If you wanted to have 2 servers hosting the role, then yes, you have to install and configure the role both places. 3. There will be no redundancy. Everything will have to be configured identically on both servers. Look at the fault tolerant options in SQL...

I prefer to install SRS for SCCM on the same SQL server running the Site Database, and dedicated the SRS instance to SCCM. Having tried to configured multiple SC products to use the same SRS instance, it's pretty ugly. You can put the SRS database anywhere, I just like having it on the same SQL box because it's a one stop shop for SQL services. I'm also not sure what'd you gain from having more than one Reporting Service point... If you're looking for SRS redundancy, I think you get that from Failover Clustering. 1. No, you don't need to install the client before you configure the site role. 2. If you wanted to have 2 servers hosting the role, then yes, you have to install and configure the role both places. 3. There will be no redundancy. Everything will have to be configured identically on both servers. Look at the fault tolerant options in SQL...

Thanks for the reply, i also thought of this after i opened this thread, i might just setup a new SRSS for this.

Thanks for the reply, i also thought of this after i opened this thread, i might just setup a new SRSS for this.

Thanks for the reply, i also thought of this after i opened this thread, i might just setup a new SRSS for this.