Create the data source in Reporting Services with the stored credentials that you specified in the wizard. This account is the Windows user account and password that Reporting Services uses to connect to the site database when you run reports. Create the Configuration Manager root folder in Reporting Services.
Retrieve the mapping between report folders and Configuration Manager secured object types. Configuration Manager maintains this map in the site database. Configure the following rights for administrative users in Configuration Manager to specific report folders in Reporting Services: Add users and assign the ConfigMgr Report Users role to the associated report folder for administrative users who have Run Report permissions for the Configuration Manager object.
Add users and assign the ConfigMgr Report Administrators role to the associated report folder for administrative users who have Modify Report permissions for the Configuration Manager object. Configuration Manager connects to Reporting Services and sets the permissions for users on the Configuration Manager and Reporting Services root folders and specific report folders.
After the initial installation of the reporting services point, Configuration Manager connects to Reporting Services every 10 minutes to verify that the user rights configured on the report folders are the associated rights that are set for Configuration Manager users. When users are added or user rights are modified on the report folder by using Reporting Services Report Manager, Configuration Manager overwrites those changes by using the role-based assignments stored in the site database.
Configuration Manager also removes users that don't have Reporting rights in Configuration Manager. Reporting Services security roles When Configuration Manager installs the reporting services point, it adds the following security roles in Reporting Services: ConfigMgr Report Users: Users assigned with this security role can only run Configuration Manager reports.
ConfigMgr Report Administrators: Users assigned with this security role can do all tasks related to reporting in Configuration Manager. Verify installation Verify the installation of the reporting services point by looking at specific status messages and log file entries. Use the following procedure to verify that the reporting services point installation was successful. Note] If you see reports in the Reports subfolder of the Reporting node in the Monitoring workspace in the Configuration Manager console, you can skip this procedure.
Verify installation by status message In the Configuration Manager console, go to the Monitoring workspace, expand System Status, and select the Component Status node. Specify a date and time for a period before you installed the reporting services point, and then select OK. Verify status message ID This status message indicates that the reporting services point was successfully installed.
Typically the reports are only revealed to users able to run them, and SQL connections in the source allow anyone to run with sufficient privileges. The reporting service itself has to have the configuration edited to enable Kerberos protocols The latter method allows reports to be embedded directly into web pages or. NET Windows applications. The ReportViewer control will process reports by: a server processing, where the report is rendered by the Report Server; or b local processing, where the control renders the RDL file itself.
The Report Server Installation Instance Selection dialog box appears so that you can select the report server instance you want to configure. Verify installation by log file Open the Srsrp. Figure 8: Install the Default instance Be sure to click Add current user to make your account an administrator. Step through this log file starting from the time that the reporting services point was successfully installed.
Security will be covered in more detail in a later article on deploying reports. Installing and Configuring SQL Server and Reporting Services Since this series is focused on report development, it will cover just enough about installation and configuration to help you get things set up on your development computer.
At the same time, we find some information about this job in Report Server database, the below query returns the following information about subscription.
Note] If you see reports in the Reports subfolder of the Reporting node in the Monitoring workspace in the Configuration Manager console, you can skip this procedure. Configure report execution properties, report history, and report parameters. You can also use the Web Portal to view reports. In the main tab of configuration manager, we can start and stop Report Server service and at the same time we can find out Report Server edition, product version and other main information about SQL Server Reporting Service. The specific certificate's friendly name is the FQDN of the site server in the Trusted People certificate store for the local computer.
Look for the string Installation was successful.
In the Server type list, select Reporting Services. You can create or edit reports from the Configuration Manager console when you run it from one of these servers. You can view a report, its general properties, and past copies of the report that are captured in report history. You can customize Report Manager in very limited ways.
For that we've added a new report type: mobile reports, based on the Datazen technology we acquired about a year ago and integrated into the product. If you are a previous developer or user of Datazen reports, these will look familiar to you as Microsoft acquired the company and brought the technology into SSRS. Figure Install Reporting Services Click through the installation wizard. Security roles and rights are inherited and can be overloaded. Figure 8: Install the Default instance Be sure to click Add current user to make your account an administrator. The new web portal is a complete rewrite of Report Manager.
In this tab execution logging option can disable. Web portal For end users of native-mode Reporting Services, the front door is a modern web portal you can view in most browsers. The data returned by the data sources is merged with the report definition into a report.
The first layer of security is built into the Web Portal. You can export to new formats such as PowerPoint. Figure 9 shows these options. Configuration Manager also removes users that don't have Reporting rights in Configuration Manager. Step through this log file starting from the time that the reporting services point was successfully installed. When you start Report Manager, the pages, links, and options that you see will vary based on the permissions you have on the report server.
You can control access to folders and individual reports based on network groups or user accounts. This view helps us to find out usage frequency of reports, execution times and what parameters are used in the reports. I first saw it demonstrated at the PASS Summit and had the Beta version installed and running at work as soon as I could get my hands on the media.