Reporting Services 2005 advanced deployment options

re: Reporting Services 2005 advanced deployment options

jcnovoa — Sun, 13 Nov 2005 00:44:35 GMT

The best way to do this would be to take advantage of a Report Server portal on the DMZ and a SQL & IIS Server hosting a WebService on the LAN as to NEVER open port 1433.... regretfully, as I described in this post,
http://channel9.msdn.com/ShowPost.aspx?PostID=135454
it seems using the XML Data Source to attempt to do this when dealing with parameterized reports won't work unless you know how to include them in the <Query/> which is not documented on BOL

re: Reporting Services 2005 advanced deployment options

jjcorra — Fri, 01 Sep 2006 18:29:50 GMT

Is there any way to have more than one Virtual Directory in IIS mapped to a single Report Server instance? I'm essentially doing the opposite of what you've done--we have the Report Server available on the public site, but the Report Manager only available internally. Our client has a legacy ColdFusion application which we are trying to phase out over time and migrate to .NET. We've already replaced some of the existing reports with reports written in SQL Reporting Services. However, in the meantime until the whole application is ported to .NET, they don't want to have to login multiple times and manage multiple usernames and passwords in both the ColdFusion application and in Windows, so authentication is handled in ColdFusion and there's a Virtual Directory for Reporting Services set up in their public site with anonymous access enabled, mapped to a user account with the Report Browser security role. In SQL 2000 Reporting Services, we had the Report Manager and an additional Report Server Virtual Directory set up in a separate IIS site using NTLM and which was only available internally within their network for administrators to manage reports. However, they're upgrading to SQL 2005, and I've only been able to successfully set up a single Virtual Directory for the Report Server, which has to be in the public site with anonymous access enabled. Report Manager runs off of the Report Server web service, so in Report Manager you only get the options availabe to the account set up with the Report Browser role. Is there any way around this, other than disabling anonymous access on the Report Server whenever a report needs to be deployed?

Charlie Maitland’s Blog Tip on 407 Errors in Reporting Services «

Charlie Maitland’s Blog Tip on 407 Errors in Reporting Services « — Wed, 28 Feb 2007 23:43:49 GMT

PingBack from http://charliem.wordpress.com/2007/02/28/tip-on-407-errors-in-reporting-services/

Tudor s WebLog Reporting Services 2005 advanced deployment options | Paid Surveys

Sat, 30 May 2009 00:17:22 GMT

PingBack from http://paidsurveyshub.info/story.php?title=tudor-s-weblog-reporting-services-2005-advanced-deployment-options

Tudor s WebLog Reporting Services 2005 advanced deployment options | debt settlement program

Mon, 15 Jun 2009 20:20:12 GMT

PingBack from http://edebtsettlementprogram.info/story.php?id=22012