SCOM 2012R2 – Issues with Chained Gateways

Question

We recently migrated from our SCOM 2012 SP1 to 2012R2.  In both versions of SCOM, we have set up designated chained gateway servers, whose sole purpose is to communicate between untrusted forests and the RMS.  It goes as follows:  Untrusted
Forest (AD Server) -> Chained SCOM Gateway -> RMS.  For example, ACLOUD -> SCOMGW01 -> SCOM01 
We recently added new site and duplicated the gateway installation process from our current site to our new site.  From the example above, rather than reporting upstream to the chained site gateway (SCOMGW01), ACLOUD
attempts to reach RMS server directly (SCOM01), which it has no route to resulting to the error event below:
“The OpsMgr Connector could not connect to [RMS Server]:5723.  The error code is 10061L (No connection could be made because the target machine actively refused it).”

Answer 1

That was a great post, thanks!  Unfortunately, because we are using 2012 R2 and no longer 2012, I saw some noticeable differences in the cmdlets.  All else equal, I think this is the part of our script that is the issue.  Because this exact
same part worked with our 2012 configurations.  Do you see anything here that may be the problem, or anything new/replaced for 2012 R2?
$CAName = "CA01.xxxxx.LOCAL\xxxxx-ROOTCA"
$SCOMApprovalToolPath = "C:\Program Files\Microsoft System Center 2012 R2\Operations               Manager\Server\Microsoft.EnterpriseManagement.GatewayApprovalTool.exe"
$SCOMGatewayInstallFilesPath = "C:\SCOMGatewayInstallationFiles"
$SCOMDefaultManagementServer = "SCOMGW01.xxxxx.LOCAL"
$SCOMFailoverServer = ”SCOMGW02.xxxxx.LOCAL”
Our management server (RMS) is SCOM01.xxxxx.local (xxxxx changed, of course) with SCOM02.xxxxx.local as the failover MS.  SCOMGW01 & SCOMGW02 are our chained gateways.