Change Reporting Configuration

System > Server Management > Configure > Change Reporting Config...

The Change Reporting Configuration dialog selects the type of reporting server used to run reports.

• A built-in, proprietary report server is provided that requires no additional configuration.
• If instead, a SQL Server Reporting Services (SSRS) is preferred, you can configure the VSA connection to the SSRS instance used to generate VSA reports. The SSRS may be installed locally or remotely from the Kaseya Server and locally or remotely from the SQL Server instance hosting the ksubscribers database.

Actions

• Edit - Edits the reporting server configuration.
• Test - Tests that reporting server configuration is working.
• Run Registration - This button is used by developers to register newly created data sets for customizable reports, instead of running Reapply Schema for the entire VSA.

Options

• Use Kaseya Reporting - If checked, a built-in, proprietary report server is used to run reports. Intended for smaller implementations of the VSA. This report server is used by default for new installs of the VSA. If blank, an SSRS report service is used to run reports. SSRS is intended for larger implementations. If blank, you must provide a Host Name URL to a SQL Server Reporting Services instance to run reports.
• Reporting Timeout (Min) - Sets the time to wait for a report to complete publishing.
• Host Name - The URL used by the VSA to connect to a SQL Server Reporting Services instance. Mandatory to run reports. The VSA typically uses one of the following URL patterns to connect to a SQL Server Reporting Services instance. Specifying the appropriate URL is mandatory to run reports.

  Note: - See the Kaseya Server Setup for a visual walkthrough of the steps required to configure an SSRS reporting server.

  SQL on the same box as VSA

  http://localhost/ReportServer (most common)
  http://localhost/ReportServer$SQLExpress http://localhost/ReportServer$<SQLINSTANCENAME> (2005)
  http://localhost/ReportServer_<SQLINSTANCENAME> (2008)
  http://localhost:<PORTNUMBER>/ReportServer$<SQLINSTANCENAME> (2005)
  http://localhost:<PORTNUMBER>/ReportServer_<SQLINSTANCENAME> (2008

  SQL box separate from VSA

  http(s)://<SQLSERVERNAME>/ReportServer (most common)
  http(s)://<SQLSERVERNAME>/ReportServer$SQLExpress
http(s)://<SQLSERVERNAME>/ReportServer$<SQLINSTANCENAME> (2005)
  http(s)://<SQLSERVERNAME>/ReportServer_<SQLINSTANCENAME> (2008)
  http(s)://<SQLSERVERNAME>:<PORTNUMBER>/ReportServer$<SQLINSTANCENAME> (2005)
  http(s)://<SQLSERVERNAME>:<PORTNUMBER>/ReportServer_<SQLINSTANCENAME> (2008)

• User Name - The user name used to access the Reporting Services instance when running reports. Applies to some configurations. See the User Name section below for more details.
• Logo - The URL of the image displayed in the header of reports. Applies to some configurations. By default, VSA report headers display the image specified by the System > Site Customization > Site Header. Changing the value in the System > Configure > Change Reporting Config... > Logo field overrides this default, changing the URL for report headers only. Changing the URL in the Change Reporting Config... > Logo field does not affect the display of the Site Header image. If a logo does not display in SSRS reports it may be due to either of the following conditions:
  • The SSRS is installed on the same machine as the Kaseya Server. SSRS is unable to retrieve the logo because of firewall issues. Change the URL to localhost from the externally available URL/IP address.
  • The VSA has been configured using a self-signed security certificate. Change the protocol from https to http.
• Report URL Base - Overrides the URL used for CURL reports. For most reports the external VSA URL is used to generate reports but, an issue called "router loopback" can occur with CURL reports. Enter a different URL from the external VSA URL to avoid this issue. Defaults to http://localhost:80/
• Concurrent Reports - Sets the number of reports that can be published simultaneously. Concurrent reports greater than this number are queued.
• Keep All Reports - If No, Number of Days determines how long reports are kept. If Yes, all reports are kept and Number of Days setting is not applicable.
• Keep Number of Days - Sets the number of days to keep a report after its creation date. Must be at least 30 days.

  Note: Only deletes reports created after the Number of Days value is enabled. Reports can be manually deleted from the <Kaseya_Installation_Directory>\WebPages\DataReports directory.

User Name

You can provide all VSA users with a credential that lets them run SSRS reports. This eliminates the need to maintain access rights for each VSA user requiring access to the SSRS. This applies in particular to VSA users in a workgroup instead of a domain, who don't have a centralized method of authentication such as Active Directory to manage access rights to the SSRS.

Credentials are specified in three locations:

• User Accounts in the system hosting the SSRS.
• SSRS Report Manager.
• VSA > System> Configure > Change URL... > User Name

This procedure creates a dedicated user—in this example, KaseyaReport—in the system hosting the SSRS. The SSRS Report Manager is used to give the KaseyaReport user access to running reports in the SSRS. Finally, the KaseyaReport credential is registered in the System> Configure > Change URL... > User Name fields. From that point forward the VSA uses that credential to access the SSRS every time a VSA user runs a report.

1. On the system hosting the SSRS, add a KaseyaReport user using the Microsoft Management Console. Using the console enables you to set the checkboxes below for the new user.
   • Give the user a strong password.
   • Uncheck the User must change password at next logon field.
   • Check the User cannot change password and Password never expires fields.
2. Apply appropriate permissions to the new user for your environment.
3. On the system hosting the SSRS, open a browser and type in the URL for Report Manager, for example, http://localhost/Reports, using the Administrator account.
4. Click Site Settings at the top right hand corner.
5. Click Security in the left hand sidebar.
6. Click New Role Assignment along the menu bar.
7. Enter the username that was created in step 1 in the Group or user name field, for example, KaseyaReport.
8. Select System User checkbox.
9. Click Add.
10. In the VSA, display the System > Server Management > Configure page. Click on the Change URL button to open the dialog.
11. Click on the Edit button at the top of the page.
12. Enter the credential you defined in step 1 and make sure the Specify Account checkbox is checked. This means SSRS will use the credential you entered. If the user, for example KaseyaReport, is not a domain user you can leave the Domain field blank.
13. Click Save and then click on the Test button to test the changes.