Deploy and Configure 2X Reports
Before you can generate reports using 2X RAS you first have to install and configure MS SQL and the 2X Reporting Service. Before doing so, first check whether your machine complies with the prerequisites outlined below . Once confirmed, proceed with the installation and configuration process.
- A machine running Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 or Windows Server 2012 R2
- An Active Directory user with Username: RASREPORTINGVIEW. This user will be used to view reports.
- 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 2X Remote Application Server or a different machine running within your network.
SQL Configuration Requirements
- MS SQL Server Features installed - Database Engine Services, Reporting Services - Native, Management Tools.
- MS SQL Named Instance: RASREPORTING, Instance ID: RASREPORTING
- SQL Server Administrators - SA (System Administrator), AD Administrator, System User.
- SSRS port set to 8085
For the full step by step recomended MS SQL installation and configuration procedure, please review the following guide: http://www.2x.com/support/ras/setting-up-reporting/
Note - For installations running on a multi server farm environment it is recommended that MS SQL is installed on a dedicated machine.
Installing Parallels 2X RAS Reporting
Log in to the machine running MS SQL with an account that has administrative privileges (AD) required to install 2X RAS reports.
- Download the latest version of the Parallels 2X RAS Reporting setup from the 2X Website.
- Double click 2XRASReporting to run the installation Wizard. Click Next when prompted.
- Review and approve the end-user license agreement and click Next.
- Specify the folder location where 2X RAS will be installed and click Next.
- Click “Install” to commit the config and initiate the installation. Upon completion, click finish.
Configure Reports from Parallels 2X Remote Application Server
Reports are generated from the Parallels 2X Remote Application Server Console. To generate reports 2X RAS must be configured to communicate with the reporting service.
Reporting settings in the Administration Category
Configure reporting from the Parallels 2X Remote Application Server Console, navigate to Administration > 2X Reporting. Enable the Enable 2X Reporting checkbox to enable reporting and configure the options below:
- Server - Specify the IP address of the machine hosting your SQL database that the Reporting service is installed on. If the database is located on the same machine you have installed Mobile Device Management on, you can also use localhost.
- Port - Specify the port used to communicate with the 2X 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
Subsequently click “Test Connection” to test the configuration and “Apply” to commit the configuration.
Note: The default user is RASREPORTINGVIEW created during the installation process. Alternate users need to be configured in SSRS with browser permissions.
Advanced settings allow the administrator to fine tune data collected by the reporting service and define how long this data is retained for before purged.
2X Reporting Advanced Settings
To access the reporting advanced options, navigate to Administration > Reporting > Advanced and configure the options below:
- From the Session Information section configure the options below:
- Enable Tracking - records sessions data (affects all reports except Server Reports)
- Retain information for - specify the period session information is retained for before purged
- From the Server Counters Information section configure the options below:
- Enable Tracking - records server counter data (affects Server Reports only)
- Retain information for - specify the period server counters information is retained for before 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 will be shown in reports generated for the previous period.