Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into ssas-1200-tutorial

Author: Owen Duncan

docs/reporting-services/install-windows/urls-in-configuration-files-ssrs-configuration-manager.md

@@ -47,7 +47,7 @@ ms.author: maggies
 
 |Setting|Usage|Description|  
 |-------------|-----------|-----------------|  
-|**ReportServerUrl**|Optional. This element is not included in the RSReportServer.config file unless you add it yourself.<br /><br /> Set this element only if you are configuring one of the following scenarios:<br /><br /> the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] provides Web front-end access to a Report Server Web service that runs on a different computer or a different instance on the same computer.<br /><br /> When you have multiple URLs to a report server and you want the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] to use a specific URL.<br /><br /> You have a specific report server URL through which you want all the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] connections to use.<br /><br /> For example, you might enable the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] access for all computers on network, yet require that the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] connect to the report server through a local connection. In this case, you might configure **ReportServerUrl** to "`https://localhost/reportserver`".|This value specifies a URL to the Report Server Web service. This value is read by the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] application at startup. If this value is set, the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] will connect to the report server that is specified in the URL.<br /><br /> By default, the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] provides Web front-end access to the Report Server Web service that runs within the same report server instance as the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)]. However, if you want to use the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] with a Report Server Web service that is part of another instance or runs in an instance on a different computer, you can set this URL to direct the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] to connect to the external Report Server Web service.<br /><br /> If a Secure Sockets Layer (SSL) certificate is installed on the report server to which you are connecting, the **ReportServerUrl** value must be the name of the server that is registered for that certificate. If you get the error, "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS security channel", set **ReportServerUrl** to the fully qualified domain name of the server for which the SSL certificate was issued. For example, if the certificate is registered to **https://adventure-works.com.onlinesales**, the report server URL would be **https://adventure-works.com.onlinesales/reportserver**.|  
+|**ReportServerUrl**|Optional. This element is not included in the RSReportServer.config file unless you add it yourself.<br /><br /> Set this element only if you are configuring one of the following scenarios:<br /><br /> the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] provides Web front-end access to a Report Server Web service that runs on a different computer or a different instance on the same computer.<br /><br /> When you have multiple URLs to a report server and you want the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] to use a specific URL.<br /><br /> You have a specific report server URL through which you want all the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] connections to use.<br /><br /> For example, you might enable the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] access for all computers on network, yet require that the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] connect to the report server through a local connection. In this case, you might configure **ReportServerUrl** to "`https://localhost/reportserver`".|This value specifies a URL to the Report Server Web service. This value is read by the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] application at startup. If this value is set, the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] will connect to the report server that is specified in the URL.<br /><br /> By default, the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] provides Web front-end access to the Report Server Web service that runs within the same report server instance as the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)]. However, if you want to use the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] with a Report Server Web service that is part of another instance or runs in an instance on a different computer, you can set this URL to direct the [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)] to connect to the external Report Server Web service.<br /><br /> If a Secure Sockets Layer (SSL) certificate is installed on the report server to which you are connecting, the **ReportServerUrl** value must be the name of the server that is registered for that certificate. If you get the error, "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS security channel", set **ReportServerUrl** to the fully qualified domain name of the server for which the SSL certificate was issued. For example, if the certificate is registered to **https:\//adventure-works.com.onlinesales**, the report server URL would be **https:\//adventure-works.com.onlinesales/reportserver**.|  
 |**ReportServerExternalUrl**|Optional. This element is not included in the RSReportServer.config file unless you add it yourself.<br /><br /> Set this element only if you are using the SharePoint 2.0 Web Parts and you want users to be able to retrieve a report and open it in a new browser window.<br /><br /> Add \<**ReportServerExternalUrl**> underneath the \<**ReportServerUrl**> element, and then set it to a fully qualified report server name that resolves to a report server instance when accessed in a separate browser window. Do not delete \<**ReportServerUrl**>.<br /><br /> The following example illustrates the syntax:<br /><br /> `<ReportServerExternalUrl>https://myserver/reportserver</ReportServerExternalUrl>`|This value is used by the SharePoint 2.0 Web Parts.<br /><br /> In previous releases, it was recommended that you set this value to deploy Report Builder on an Internet-facing report server. This is an untested deployment scenario. If you used this setting in the past to support Internet access to Report Builder, you should consider an alternative strategy.|  
 
 ## See Also