Warning: Recommended version of Report Server for use with SharePoint 2010 Beta1 is SSRS 2008 R2 CTP2 / CTP3 only. The only version of SSRS Add-in for SharePoint with SharePoint 2010 Beta 2 is SSRS 2008 R2 November CTP Add-in. Using SSRS 2008 with Beta product - MOSS Beta 1 or Beta 2 is expected to work, however it is not a supported scenario esp. in production environments and has not been extensively tested at the time of publishing this blog. Hence, please proceed with utmost caution by backing up any previous data, etc. before trying out the steps below:

1. Enabling SSRS 2008 report server to load SharePoint 2010 Beta1 (Ignore this step for SharePoint 2010 Beta 2, because it is expected to support ASP .Net assembly binding redirect out-of-the box): Use ASP.Net assembly binding redirect to ensure an existing SSRS 2008 can load SharePoint 14 assemblies, details @ http://msdn.microsoft.com/en-us/library/2fc472t2(VS.80).aspx. Here is the entry to add under <System.data> element tags in %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config 
   <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
             <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
                  <assemblyIdentity xmlns="urn:schemas-microsoft-com:asm.v1" name="Microsoft.SharePoint" publicKeyToken="71e9bce111e9429c" culture="neutral" />
                  <bindingRedirect xmlns="urn:schemas-microsoft-com:asm.v1" oldVersion="12.0.0.0" newVersion="14.0.0.0" />
             </dependentAssembly>
        </assemblyBinding>
   </runtime>

2. Integrating SSRS Add-in with SharePoint 2010 Beta2: SSRS 208 R2 November CTP ships an SSRS 2008 R2 November CTP Add-in for SharePoint 2010 @ http://www.microsoft.com/downloads/details.aspx?FamilyID=16bb10f9-3acc-4551-bacc-bdd266da1d45&displaylang=en. This the only SSRS Add-in supported with SharePoint 2010 Beta2 and can be installed prior to installing SharePoint 2010 Beta 2. It also supportsinstalling after SharePoint 2010 is installed. Having said that, the recommended means to
• Installing SSRS 2008 R2 Nov. CTP Add-in before installing SharePoint 2010 Beta 2 WFEs
• Install rsSharePoint.msi (ships starting with SSRS 2008 R2 November CTP) 
• Install SharePoint 2010 Beta 2  
• Run SharePoint 2010 Beta 2  configuration wizard
• After this will activate the feature in the Central Admin site, however not in the SharePoint 2010 content sites  because no Report Server has been integrated into SharePoint 2010. In this state (called as Local mode) SSRS supports out-of-the-box rendering only of 2 types of reports - Access and SharePoint List reports.
• After successfull installation, configuring an integrated SSRS instance with SharePoint 2010 Beta2 entails:
• Goto the "Reporting Services Integration" web page in the "Application Management" in Central Administration,
• Provide the Report Server URL, Authentication Type and credentails and Press Apply.
• For additional instances of Reportings Services when you ahve configured SSRS in Scale-out configuration use the "Add an SSRS instance to the Integration" web page.
3. Integrating SSRS Add-in that ships in MOSS 2010 Beta1: (Note: SSRS Add-in is not supported with WSS 2010 Beta1.) Just like in prior versions of the SSRS Add-in for SharePoint you need to belong to the SharePoint Farm Administrator group to perform the following steps and step 1 also requires local admin credentials for the SSRS machine.  
1. Provision SSRS 2008 to access MOSS 2010 Beta1:
• Browse to "SharePoint Central Administration" -> "General Application Settings" -> "Add a Report Server to the integration" pages,
• Provide the machine name, instance name and press "OK", and
• Provide credentials in the credentials dialog box and press "OK".
2. Update Report Server URL and Authentication mode by running the powershell code below:
   echo "Loading Microsoft.SharePoint.Administration..."
   [reflection.assembly]::LoadWithPartialName(“Microsoft.SharePoint.Administration”)
   $services = [Microsoft.SharePoint.Administration.SPFarm]::Local.Services
   foreach ($service in $services) {
            if ([string]::Compare($service.Name, "ReportingService", $True) -eq 0) { 
               ##### Set Report Server Web Service URL
               $service.RSServerUrl = "http://<RS_Server_Name>:<RS_Server_port>/<RS_Web_Service_VDir>"; 
               ##### Set Authentication mode to "Windows" or "Trusted"
               $service.AuthenticationType ="Windows"; 
               $service.Update();
               echo $service;
           }
   }
3. Activate the RS feature in all of MOSS 2010 Beta 1's content sites (Ignore for with SharePoint 2010 Beta2 and SSRS 2008 R2 November CTP Add-in for SharePoint 2010):
• Copy the attached RSIntegrationResults.aspx page into the %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS\ReportServer folder. ***
• Browse to "SharePoint Central Administration" -> "General Application Settings" -> "Reporting Services Integration" page, and
• Press OK,
• *** Note: This is a bug, wherein RSIntegrationResults.aspx page was not included amongst the SSRS Add-in for SharePoint files in MOSS 2010 Beta1. Hence, if you press OK without copying this page you will notice a generic SharePoint error page being shown on successful completion of activating the RS feature.

A] Forms Authentication

1. If using SQL 2005 SP2 make sure you have installed the sharepointrs.msi that includes the following fix http://support.microsoft.com/kb/939942/ else move onto step2.
2. Add the following entries to the Web.config file for the SharePoint web application you want to enable launching of Report Builder:
   <location path="_vti_bin/ReportBuilder/ReportBuilder.application">
     <system.web>
       <authorization>
         <allow users="*" />
       </authorization>
     </system.web>
   </location>
   <location path="_vti_bin/ReportBuilder/ReportBuilder.exe.manifest">
     <system.web>
       <authorization>
         <allow users="*" />
       </authorization>
     </system.web>
   </location>
   <location path="_vti_bin/ReportBuilder/ReportBuilder.chm.deploy">
     <system.web>
       <authorization>
         <allow users="*" />
       </authorization>
     </system.web>
   </location>
   <location path="_vti_bin/ReportBuilder/ReportBuilder.exe.deploy">
     <system.web>
       <authorization>
         <allow users="*" />
       </authorization>
     </system.web>
   </location> 
3. For non-English sites ensure you add the appropriate appropriate LCID and Culture entries as well to the Web.config file. For example enabling for launching in Japanese in addition to English (in Step 2) add the following:
   <location path="_vti_bin/ReportBuilder/1041/ReportBuilder.chm.deploy">
     <system.web>
       <authorization>
         <allow users="*" />
       </authorization>
     </system.web>
   </location>
   <location path="_vti_bin/ReportBuilder/ja/ReportBuilder.resources.dll">
     <system.web>
       <authorization>
         <allow users="*" />
       </authorization>
     </system.web>
   </location>
   For details on LCIDs and Cultures supported by the Reporting Services Add-in for SharePoint refer to "Supported Languages" section @ http://technet.microsoft.com/en-us/library/aa905871(SQL.90).aspx or the install folder under %programfiles%\Common Files\Microsoft Shared\web server extensions\12\ISAPI\ReportBuilder.
4. Enable anonymous access on the ReportBuilder folder via IIS manager. For more information, see "How to Enable Anonymous Access on the ReportBuilder Folder" section @ http://msdn.microsoft.com/en-us/library/ms365173(SQL.90).aspx

A known error you can run into if not setup correctly is "Cannot Start Application. Cannot continue. The application is improperly formatted. Contact the vendor for assistance."

B] Basic Authentication

1. If using SQL 2005 SP2 make sure you have installed the sharepointrs.msi that includes fix #50001712 from http://support.microsoft.com/kb/941450 else move onto step2.
2. If users encounter an HTTP 401 or 400 when launching ReportBuilder then you need to ensure users select the "Remember Password" checkbox when you are provided the user credentials dialog at login time. The root cause is that the login / authentication via the user credential dialog box results in SharePoint creating a WSS_KeepSessionAuthenticated cookie to ensure this user remains authenticated for the duration of their session. ReportBuilder is launched usingClick-once, which is not aware of nor supports using this WSS_KeepSessionAuthenticated cookie resulting in the error from SharePoint during launch of ReportBuilder.