SCCM 2012 - Migrating SQL components to cluster including Reporting Services

Question

 
Current SCCM 2012 environment:
 - CAS with database on remote SQL (non-cluster) server in a named instance - SQLSRV\CASINST 
 - SQL Reporting Services in also installed in the SQLSRV\CASINST instance 
 - The SCCM Reporting Services Point role is installed on the SQLSRV\CASINST instance 
 - Primary server with database on the same remote SQL (non-cluster) server in a different named instance - SQLSRV\PRIINST 
Now I would like to move all of the database stuff to an existing SQL 2008 R2 cluster (SQLCLUSTER) and decommission the SQLSRV server.  SQLCLUSTER already exists and the default instance is already in use (for other applications) for both database engine
services and reporting services.
From my understanding:
 - SQL 2008 R2 Reporting Services cannot be clustered
 - Best practise is to install Reporting Services Point on a remote site server rather than a CAS server
 - SSRS can be installed on nodes in SQL cluster as standalone installs - with the caviat that they don't use instance names already in use
So I plan to:
 - Move CAS database to new named instance on cluster eg SQLCLUSTER\CASINST 
 - Move primary database to new named instance on cluster eg SQLCLUSTER\PRIINST 
 -  Install SQL Reporting Services on one of the cluster nodes (unclustered) using a named SSRS instance eg SQLCLUSTERNODE1\SCCMREPORTING
-  This article points out some interesting results of not have a default instance -  http://magalhaesv.wordpress.com/2012/05/24/system-center-configuration-manager-x-sql-server-reporting-services-x-wmi-english-version/
 - Move Reporting Services Point from SQLSRV\CASINST to the cluster node eg SQLCLUSTERNODE1\SCCMREPORTING
I have read on some forums (eg
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/40ad0cb4-a464-4576-b824-957ed6e1b2e2) things like '' If you have an app like SCCM that requires a default instance of SSRS, you are out of luck if your cluster already has a default
instance of the database engine.", but I cannot find this anywhere in Microsoft documentation.  From the MS documentation (http://technet.microsoft.com/en-us/library/7fd0d4f5-14e0-4ec7-b2e6-3b67487df555#BKMK_InstallReportingServicesPoint)
I understand that as long the current user has read access to WMI on the remote site server where SQL Reporting Services is installed, you should be able to use a named instance for SQL Reporting Services and successfully install the Reporting Services Point
on it.
So a 2 part question:
 - Anybody see any obvious flaws in my high level plan?
 - Anybody care to comment on the SCCM requiring a default instance of SSRS?
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

Answer 1

Yes, I know this is an old post, I’m trying to clean them up, Did you figure this out, if so how?
http://www.enhansoft.com/
Hi Garth,
Yes we moved the DBs and RS as outlined above. As expected, we needed to have a default instance of RS because otherwise the SCCM console doesn't see the Reporting Services instance when you try to deploy the Reporting Services site role.
So the above plan worked.
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au