• Article for your preferred language does not exist. Below is international version of the article.
Available article translations:

Installation and configuration of Parallels Remote Application Server Reporting Service

  • Parallels Remote Application Server 16.5
  • Parallels Remote Application Server 16.2

Installation and configuration of Parallels Remote Application Server Reporting Service

Parallels Remote Application Server Reporting Service requires Microsoft SQL Server Reporting Service. SQL Server Express Edition with Advanced Features which include Reporting Service can be used.

The latest version of Parallels Remote Application Server Reporting Service supports SQL Server versions up to 2016.

Since SQL Server Express Edition is free we recommend to use the latest versions. SQL Server 2016 Express Edition with Advanced Features x64 can be downloaded from here: SQLEXPRADV_x64_ENU.exe.



1. Please create Active Directory account which will be used to view the reports.

2. Make sure that account which will be used for SQL and Reporting Services installation is a domain account and has local Administrative permissions on the Windows Server machine. If required, add the account to the local Administrators group using. The same domain account can be used for both steps.


SQL Server Installation

1. Launch the installer and select New SQL Server stand-alone installation or add features to an existing installation option:


2. On the License Terms page accept the license terms:


3. On the Microsoft Update page if required select Use Microsoft Update to check for updates:


4. On the Feature Selection page specify Database Engine Services and Reporting Services - Native:

Note that we will install SQL Management Console later since it is no longer included in the list of available features during Database Engine installation.


5. On the Instance Configuration page select Named instance and enter the name:


6. On the Server Configuration page specify the accounts which will be running SQL services:

We will be using the default ones.


7. On the Database Engine Configuration page add local NT AUTHORITY\SYSTEM account and Active Directory account in the SQL Server administrators pane.

You should add the AD account that will be used to view the reports from the Parallels Remote Application Server Console. Add additional accounts if required.

No need to change any other settings if it is not required.


8. On the Reporting Service Configuration page select the default option Install and configure:


9. On the Complete page click Close once the installation is finished:


10. Get back to the SQL Server Installation Center and click on Install SQL Server Management Tools:


11. Web Browser will open Download SQL Server Management Studio page. Follow the link to download it.


12. Once installer is downloaded launch it and click on Install button:


13. When prompted restart computer to complete the installation:


SQL Server Configuration

1. After the computer is restarted locate and launch Microsoft SQL Server Management Studio:


2.Click on Connect button. Make sure you are using the account that was added to SQL Administrators a little while ago:


3. When you are logged in, in the left pane navigate to Security > Logins and make sure that NT AUTHORITY\SYSTEM and domain accounts are added and have sysadmin Server Roles in their properties:

Close Microsoft SQL Server Management Studio Console.


4. Locate and launch Reporting Services Configuration Manager:


5. Click on Connect button:


6. After you are connect in the left pane click on Web Service URL and then click on the Advanced in the right pane:


7. Advanced Multiple Web Site Configuration dialog will open. Change the TCP Port to 8085 using Edit button and click OK:


8. Now switch to Web Portal URL pane in the left pane and click Advanced button:


9. Advanced Multiple Web Site Configuration dialog will open again. Change the TCP Port to 8085 using Edit button here as well and click OK:


10. Close Reporting Services Configuration Manager


Installation and configuration of Parallels Remote Application Server Reporting Service

1. Download the latest version of Parallels Remote Application Server Reporting Service here: Download Links.


2. Launch the installer on the same server with MS SQL:


3. On the Database Instance pane enter the Instance name exactly as it was specified during SQL Server installation on the on the step 5 - in the Instance ID field:

Note that uppercase / lowercase format matters.


4. On the Viewing Reports User pane specify theuser name of the  domain account that will be viewing the reports.


5. Complete the installation:


6. Launch Parallels Remote Application Server Console and navigate to Administration > Reporting:

  • Enable RAS Reporting;
  • Specify the Port that will be used by Parallels Remote Application Server Components to connect to Parallels RAS Reporting Service
  • Specify the domain user credentials and click on Test Connection button
  • When succeeded click OK and click on Apply in the bottom-right corner to save the configuration changes.

7. It's required to add the specified port in the firewall exceptions for incoming traffic on the server with SQL and Reporting services.


8. Now switch to Reporting pane and make sure that you can see the names of the reports in the middle pane. Double click on any of the reports and make sure the Report dialog opens in the right pane:

Starting from this moment Parallels Remote Application Server will collect the data and show it in the available Reports.



  1. Parallels Reporting Service will start collecting info about new sessions that will be established on the server. No current sessions.
  2. Parallels Reporting Service writes the session information in database after it is reset, i.e. after user is logged off. If information about some users is missing, make sure they log off their sessions, not just disconnecting.
  3. Parallels Reporting Service logs location:
    • %PROGRAMDATA%\Parallels\RASLogs\ReportingSetup.log
    • %PROGRAMDATA%\Parallels\RASLogs\reporting.log

8c1bd7ac0efc8c4ffbb530ad3ab16fae 1d70d1f9c41d01c5f7202a4290e434e1 e672fec7c544b9c6972eababa324d634 4a54b6f3e325683094bb814b9bc24cd3 ede48a144be425de4bf9a9d265a8dd3e

Was this article helpful?
Tell us how we may improve it.
Yes No