Search

Language:  
Search for:

Available article translations:

Setting up Reporting with Parallels Remote Application Server

APPLIES TO:
  • Parallels Remote Application Server 15.0

Before you can generate reports from the Remote Application Server console, MS SQL and the Reporting Service must be installed and configured. Before doing so, first check whether your machine complies with the prerequisites outlined below. Once confirmed, proceed with the three stage process: MS SQL installation and configuration, Reporting Services installation, and Remote Application Server configuration.

Environment Requirements

  1. A machine running Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2.
  2. To view Remote Application Server reports, a default AD user account will be created by the Remote Application Server Reporting installation process. The account name is RASREPORTINGVIEW.
  3. Microsoft SQL Server 2008 SP1, Microsoft SQL Server 2008 R2 SP1, or Microsoft SQL Server 2012 - You are required to have a database instance installed either on the same machine running Parallels Remote Application Server or a different machine running within your network.

SQL Configuration Requirements

  1. MS SQL Server Features installed - Database Engine Services, Reporting Services - Native, Management Tools.
  2. MS SQL Named Instance: RASREPORTING, Instance ID: RASREPORTING
  3. SQL Server Administrators - SA (System Administrator), AD Administrator, System User.
  4. SSRS port set to 8085

Note: For installations running on a multi-server farm environment, it is recommended that MS SQL Server is installed on a dedicated machine.

Stage 1: Installing MS SQL

Reporting requires a database instance installed either on the same machine running Parallels Remote Application Server or on a different machine running within the Remote Application Server local network (recommended).

alttext

  1. Run the SQL Server setup file > Installation. Select New SQL Server stand-alone installation or add features to an existing installation to launch the setup.

    alttext

  2. The Setup Support Rules page will attempt to identify any issues during the SQL Server Setup Support Files installation. Upon completion, click Next to continue.

    alttext

  3. Enter the product license key, click Next, and accept the license terms to continue to the Setup Role dialog.

    alttext

  4. Next, select SQL Server Feature Installation and click Next.

    alttext

  5. Next, enable the features listed below that are required for reporting and click Next to continue:

    • Database Engine Services
    • Reporting Services – Native
    • Management Tools

    alttext

    Reporting Services requires that the SQL server has been configured using a specific named instance.

  6. From the Instance Configuration page, select the option Named instance,input the information below and click Next to continue:

    • Named Instance:RASREPORTING
    • Instance ID:RASREPORTING

    Without the named instance above, Reporting setup will not complete.

  7. Subsequently, the Disk Space Requirements and Server Configuration dialogs are shown. Confirm the information and click the Next button to proceed.

    alttext

  8. In the Database Engine Configuration window select Windows authentication mode and add the users below as SQL Server administrators:

    • Systems Administrator
    • AD Administrator
    • System User

    alttext

  9. The next step introduces the Reporting Service Configuration that is used by Remote Application Server to generate reports. Select the Install and configure option, and click Next to continue.

    alttext

  10. In the Ready to install section, ensure that:

    1. Features to be installed include:
      • Database Engine
      • Reporting Services
      • Management Studio Tools
    2. Instance Name
      • MUST BE: RASREPORTING

    Once confirmed, click Install to proceed with the installation. Upon completion, proceed to the verification process and port setup procedures.

    alttext

  11. Next, verify that reporting services have been set up correctly. Open the Reporting Services Configuration Manager.

  12. Input the server name from the Report Server Instance drop-down, select RASREPORTING, and click Connect.

    alttext

  13. Verify that the Report Service Status = Started.

    alttext

  14. Verify the Web Service URL is set to ReportServer_RASREPORTING.

  15. Next, change the SQL Reporting Services default (for Web Service URL and Report Manager URL) to 8085, in order to avoid conflicts between Remote Application Server gateways and SSRS (port 80). More information can be found here.

Stage 2: Reporting Setup

Log in to the machine running MS SQL Server with an account that has administrative privileges (AD).

  1. Download the latest version of the RAS Reporting setup from download.parallels.com/ras/v15/RASReporting.msi
  2. Double-click RASReporting.msi to run the installation wizard.
  3. Click Next when prompted.
  4. Review and approve the end-user license agreement and click Next.
  5. Specify the target folder for the installation and click Next.
  6. Click Install to commit the configuration and initiate the installation.
  7. Click Finish.

Stage 3: Configure Reporting in the RAS Console

To configure RAS Reporting:

  1. Select the Administration category in the RAS Console and then click the Reporting tab in the right pane.
  2. On the Reporting tab page, specify the following options:
    • Select the Enable RAS Reporting option to enable the Remote Application Server reporting functionality.
    • Server. Specify the IP address of the server hosting your SQL Server database where the Reporting service is installed. If the database is located on the same machine where you have Mobile Device Management installed, you can use localhost.
    • Port. Specify the port used to communicate with the Reporting service.
    • Prompt user for Login Details. Will prompt the user for AD credentials when generating reports.
    • Use following credentials. Specify AD username and password to be used each time a report is generated
  3. When done, click the Test Connection button to test the configuration.
  4. Click Apply to commit the configuration.

    Note: The default user RASREPORTINGVIEW is created during the installation process. Alternate users need to be configured in SSRS with browser permissions.

Stage 4: Advanced Settings

Advanced settings allow the administrator to fine tune the data collected by the reporting service and define how long this data is retained before being purged.

To access the reporting advanced options:

  1. In the RAS Console, navigate to Administration / Reporting.

  2. On the Reporting tab page, click the Tracking Settings button. The Advanced Settingdialog opens.

  3. In the Session Information section, configure the following options:

    • Enable Tracking. Records session data (affects all reports except Server Reports).
    • Retain information for. Specify how long session information is retained before being purged.
  4. In the Server Counters Information section, configure the following:

    • Enable Tracking. Records server counter data (affects Server Reports only).
    • Retain information for. Specify how long server counters information is retained before being purged.
    • Track CPU / Memory counter when change is more than. Set the minimum CPU/Memory resource usage required to record data.

Data is not collected subsequent to disabling tracking options. However, all data collected and retained prior to this will be shown in reports generated for the previous period.

Viewing the Reports

After the configuration is complete and credentials are verified via the test button, switch to the Reporting category to generate and view the reports.

Note: The first time you view reports, you may be asked to add http://RAS server domain / IP address as a trusted website. This will appear depending on the Remote Application Server machine’s Internet Explorer Enhanced Security Configuration settings.

Search words:

RAS




17333b9b93206d7dd8962eace050749d 1d70d1f9c41d01c5f7202a4290e434e1

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