Requirements and Configuration
To use Parallels RAS Reporting, you need to install and configure Microsoft SQL Server, SQL Server Reporting Services (SSRS), and the RAS Reporting component. This section describes installation and configuration requirements.
Note: RAS Reporting is described in greater detail in the Parallels RAS Reporting Guide, which can be downloaded from the Parallels website: https://www.parallels.com/products/ras/resources/
Operating System requirements
Parallels RAS Reporting can be installed on a server running one of the following Windows Server versions:
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2
- Windows Server 2008
.NET Framework 3.5 and .NET Framework 4.5 or higher must be installed.
User Account requirements
To view RAS reports, a default AD user account will be created by the RAS Reporting installer. The account name is RASREPORTINGVIEW . You can specify a different user during the RAS Reporting setup if you wish.
Microsoft SQL Server requirements
The following Microsoft SQL Server versions are supported:
- Microsoft SQL Server 2019
- Microsoft SQL Server 2017
- Microsoft SQL Server 2016
- Microsoft SQL Server 2014
- Microsoft SQL Server 2012
- Microsoft SQL Server 2008 R2 SP1
- Microsoft SQL Server 2008 SP1
RAS Reporting 17.1 brings the ability to use SQL Server Reporting Services (SSRS) and the SQL Server database engine deployed on separate hosts.
Installation locations
RAS Reporting must be installed on the same server where SSRS is installed.
The following table contains version compatibility information and locations where components necessary to use RAS Reporting can be installed:
RAS Reporting version
|
SSRS version
|
SQL Server version
|
Installation locations
|
17.1
|
2019
|
2019
|
SSRS - same host as RAS Reporting
SQL Server - can be a different host
|
17.1
|
2017
|
2019
|
SSRS - same host as RAS Reporting
SQL Server - can be a different host
|
17.1
|
2017
|
2019
|
SSRS - same host as RAS Reporting
SQL Server - can be a different host
|
17.1
|
2017
|
2017
|
SSRS - same host as RAS Reporting
SQL Server - can be a different host
|
17.1
|
2017
|
2016
|
SSRS - same host as RAS Reporting
SQL Server - can be a different host
|
17.0
|
2008 R2 - 2016
|
2008 R2 - 2016
|
SSRS and SQL Server on the same host
|
Microsoft SQL Server and SQL Server Reporting Services configuration
The Microsoft SQL Server instance must have the following features installed:
- Database Engine Services
- Reporting Services - Native
- Management Tools
The SQL Server instance must be configured as follows:
- Must be a named instance. The default instance name and instance ID used by Parallels RAS Reporting is RASREPORTING. You can specify a different name, but you have to make sure that you use the same name when configuring the RAS Reporting (as described later in this section).
- The SQL Server administrators must include system administrator, AD administrator, "System" user.
SQL Server Reporting Services must be configured as follows:
- Report Server Web Service virtual directory must be set to ReportServer_RASREPORTING.
- Report Server Web Service TCP port must be set to 8085.
- Report Manager TCP port must be set to 8085.
Note: For Parallels RAS installations running on multiple servers, it is recommended that Microsoft SQL Server is installed on a dedicated server.
Configure SQL Server for remote connections
When using Microsoft SQL Server 2016 and earlier version, it must be configured for remote connections as follows:
- Open Microsoft SQL Server Management Studio.
- Right-click on the server and select Properties.
- Go to Connections and select Allow Remote.
- Open SQL Server Configuration Manager and go to SQL Server Network Configuration > Protocols for RASREPORTING.
- Right-click on TCP/IP and choose Properties.
- Make sure the Enabled property is set to Yes.
- Select the IP Address tab and locate the IPAll section. Set the TCP Dynamic Ports field to be blank and the TCP Port field to "1433".
- Restart SQL Server. To do so, in the SQL Server Configuration Manager, right-click the SQL Server service and choose Restart.
- After the restart, in the SQL Server Configuration Manager, right-click on SQL Server Browser and choose Properties.
- Select the Service tab and set the Start Mode property to Automatic.
- Start the SQL Server Browser.
|