System Center 2012 RTM (SAV 188.8.131.521)
Windows Server 2008 R2
Microsoft SQL Server 2008 R2 SP1 Reporting Services (Datacenter Edition)
This recipe describes a scale-out deployment of SQL Server Reporting Services. In a scale-out deployment, a new instance of a report server is deployed and connected to an existing report server database which is shared among other instances of the report server. With Virtual Machine Manager Service Templates and Server App-V, it is easy to configure service templates to quickly add new scale-out nodes.
Prepare for Sequencing
- On the existing report server to which this new scale out node will be added, use the Reporting Services Configuration tool to backup the encryption key for the database. Save this key to a shared location. It will be used again later when you deploy the Reporting Service package that you create during sequencing.
- Reporting Services requires .NET 3.5. Be sure to enable the .NET 3.5 server feature before proceeding.
SAV Sequencer Steps
- Start the SAV Sequencer and select “Create a New Virtual Application Package”.
- Address any issues highlighted in the “Prepare Computer” phase. Double-clicking a message will provide more details as well as a suggested resolution. Click Next.
- Click Browse in the sequencer UI and locate the SQL Server installer. Click Next.
- Give the package a name (e.g., in this example I chose RS2008R2).
- Leave the Primary Virtual Application Directory as-is (the default is fine to use, but you can optionally change it to a different path if you desire). Click next. This will start the SQL Server installer.
SQL Server Installer Steps
- In the SQL Server installer, click on “Installation” in the left-hand menu.
- Select “New installation or add features to an existing installation”
- If it presents action items for you, they must be resolved before the installer will let you proceed. If the rule check is clean, click OK.
- Enter your SQL Server product key and click “Next”
- Accept the EULA terms, and click “Next”
- Install the setup support files (these are files required before SQL Server setup can proceed). To do this, click “Install”
- In the next page you will see a list of setup support rules. Resolve any ones that will block installation. Once they all pass, click “Next” to proceed.
- Select the “SQL Server Feature Installation” radio button and click “Next”.
- From the list of components to install, select only “Reporting Services”
- In the Shared Feature Directory and Shared Feature Directory (x86) textboxes, change the installation path to the package root folder that you specified in step #5. In this example since the package name is RS2008R2, the paths will start with “Q:\RS2008R2”
- Click "Next"
- Click “Next” again to proceed past the Installation Rules page.
- On the Instance Configuration page, specify a name for your SSRS instance.
- In the Instance Root Directory textbox, change this path the same way you changed the path in step #15 (so that it installs into Q:\RS2008R2).
- On the “Disk Space Requirements” page, click “Next”
- Specify an account as which the SSRS service will run. In this example, I chose “Network Service”, but you can choose whichever works for your environment. Click “Next”.
- Select the “Install, but do not configure the report server” radio button, then click “Next”. You will configure the report server manually later in this recipe.
- Click “Next” to proceed through the error reporting page.
- Click “Next” to proceed past the “Installation Configuration Rules” page.
- On the “Ready to Install” page, click “Install” to begin the SQL Server installation procedures that you just selected.
- When the installation is complete, you can exit the SQL Server installer.
- When the installation completes, click Close to exit the SQL Server installer.
- In the Services manager, verify that the SQL Server Reporting Services service is running. This indicates that the installation was successful.
- Locate and run the SQL Server 2008 R2 Service Pack 1 installer.
Reporting Services Configuration Steps
- In the Start menu, locate and open the Reporting Services Configuration Manager.
- Connect to the local SSRS instance that was just installed.
- Browse to http://msdn.microsoft.com/en-us/library/ms159114(v=sql.105).aspx, and follow the directions here to add the new SSRS report server to a scale-out deployment. Start with Step #3 under “To install and configure the second report server instance”.
- Also complete the section entitled “To join the second report server instance to the scale-out deployment”
- Exit the Reporting Services Configuration Manager tool.
- Browse to the URL for Reporting Manager that you just created, and verify that it is working properly.
SAV Sequencer Steps
- Return to the Server App-V Sequencer and select "I am finished installing."
- On the Configure Software dialog, click Next
- On the Package Completed dialog, click Close
- Under the file menu, select Save to save your package. On the "Package Completed" screen, click Close.
How to Deploy
Reporting Services requires that an encryption key be specified during deployment in order to add a node to a scale-out deployment. Because of this, there are some special steps you need to take with Server App-V to make sure the key gets deployed correctly with the server instance. This is where you will use the key that you saved from the existing instance of Reporting Services in step #1.
To configure the package for successful deployment, there are several values in the deployment configuration file (deploymentconfig.xml) that need to be set:
Value to Set
MSSQLSERVER temporary encryption key password
This is a temporary password used only during the deployment process. You’ll never need to remember this or use it again, but whatever you type here must be compliant to your domain’s policy (that’s what Server App-V has to ask for it).
MSSQLSERVER Encryption Key Password
This is the password that you used to encrypt your key when you exported it from the running SSRS instance in step #1 above.
MSSQLSERVER Encryption Key File
The full filesystem path to the key file. This has to be accessible from the machine on which the SAV agent is running, where you are deploying the new SSRS scale-out node.
MSSQLSERVER Database Logon Account
Account that SSRS will use to connect to the ReportServer database.
- Changed type Aaron.ParkerMVP, Owner Wednesday, September 19, 2012 9:35 PM