From 9ad3b8011ae31fd6e85531c8660f2cd625d6bff5 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Mon, 6 Oct 2025 10:01:13 +0300 Subject: [PATCH 01/24] draft --- dotnet-docs/windows-installation.md | 26 +++++++++++++++++-------- implementer-guide/setup/installation.md | 4 ++++ 2 files changed, 22 insertions(+), 8 deletions(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index c5c3edb6..95c4de94 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -10,15 +10,17 @@ position: 2 # Report Server for .NET: Installation on Windows -The Report Server for .NET (`RS.NET`) is currently distributed along with the installer for the .NET Framework 4.6.2. By default, the installer does not install RS.NET. Users must click `Customize` to install RS.NET. +Starting from **2025 Q4**, a dedicated Report Server for .NET (RS.NET) installer is introduced. This article explains the installation steps and the differences from the Report Server for .NET Framework installer. -## Installation Process +## Prerequisites + +RS.NET is an ASP.NET Core web application that requires the [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment. Install this module following the [Install the ASP.NET Core Module/Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0#install-the-aspnet-core-modulehosting-bundle) instructions before proceeding. The installation wizard will display a warning if this module is not available. -The RS.NET is an ASP.NET Core web application and its installation on the IIS requires the `ASP.NET Core Hosting Bundle` as explained in the Microsoft article [Host ASP.NET Core on Windows with IIS](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0). The installation wizard will show a warning if the module is not installed. The user can continue the installation even when the module is not found. +## Installation Process ->note Known issue: the detection returns false negative results on machines having `Windows 11`, `Windows Server 2016` and `Windows Server 2022`. This is fixed and will be included in our next release. +TODO: mention what the msi is called and guide the user through the installation steps (go to downloads, etc.). while guiding, mention that currently there is no examples/migration tool (possibly in a note) -The installer will configure the ports for installing the RS.NET and RS.NET Service Agent, taking the available ports from 80 upwards: +The installer automatically assigns available ports for RS.NET and RS.NET Service Agent. By default, these are ports 81 and 84 respectively, but it can assign the next available ones if these are already in use. ![Use the button Customize to allow installing the Report Server for .NET](../images/rs-net-images/rs-customize.png) @@ -26,18 +28,22 @@ The installer will configure the ports for installing the RS.NET and RS.NET Serv The __RS.NET__ is installed in `{Installation Folder}\Telerik Report Server\Telerik.ReportServer.Web.NET`. The cross-platform distribution of RS.NET is in the `_non-windows` subfolder. -The __RS.NET Service Agent__ is installed in `{Installation Folder}\Telerik Report Server\Services\.NET`. The cross-platform distribution of RS.NET Service Agent is in the '_non-windows' subfolder. +The __RS.NET Service Agent__ is installed in `{Installation Folder}\Telerik Report Server\Services\.NET`. The cross-platform distribution of RS.NET Service Agent is in the `_non-windows` subfolder. + +TODO: explain this further? what is the purpose of the cross-platform distribution now that RS.NET can be installed on Linux through the dedicated installer? there doesn't seem to be such a folder anymore. maybe move this whole section at the end of the article to keep the correct flow of actions (installation > configuration > additional details) ## Configuration ### Automatic Configuration on Windows -The installation wizard will do the initial configuration of _RS.NET_ and _RS.NET Service Agent_ on Windows, making them ready-to-run. +The installer is supposed to initially configure both RS.NET and RS.NET Service Agent on Windows, making them ready-to-run. If the automatic configuration fails, check the [instructions for manual configuration](#manual-configuration-on-windows). -If the automatic configuration fails, please, get familiar with the [initialization process](#initialization-process) and follow the [instructions for manual configuration](#manual-configuration-on-windows). +TODO: what a fail could mean here? a crash in the installer (likely not since no assets would be installed to be checked) or that there is an error once RS.NET is opened in the browser? maybe move this sentence at the end of the installation process and move installed assets at the end of the article to keep the correct flow of actions ### Initialization process +TODO: maybe explain 2 and 3 in the installed assets section? make 1 longer + 1. When the Report Server is started for the first time, the user is supposed to pass the _Configure Storage_ and _Register Administrator_ pages. The settings from these pages are stored in a file named `ReportServerAdmin.json`. 1. Next, the RS.NET checks its `appsettings.json` configuration file for the key __InitialAgentUrl__. If the installation has passed successfully, the key must exist and must have a valid value like __http://localhost:84__. This is where the MSI installation file for Windows has registered the __RS.NET Service Agent__. 1. The RS.NET calls the above URL and passes the storage settings to its Service Agent. They are saved in the file `ServiceAgent.json` in the RS.NET Service Agent's directory. If such a file does not exist, the agent was not initialized or registered in the IIS. @@ -55,3 +61,7 @@ If the automatic configuration fails, please, get familiar with the [initializat 1. Restart the RS.NET and RS.NET Service Agent. 1. Check the RS.NET's _Configuration_ -> _ServiceAgent_ page. The entry `"DefaultServiceAgent" : "http://localhost:84"` should now be present. The URL may differ, depending on your settings. 1. To use the RS.NET Service Agent, ensure the _Mail Server_ settings in _Configuration_ page are valid. + +TODO: what restart means in step 4? iisreset/recycling the app pool for rs.net and restarting the service agent through services.msc > rsnet service agent > restart? maybe change the section title to "debugging" to let know users are supposed to do this as last resort when the automatic configuration fails. explain that the pages that are mentioned have to be opened in the browser + +TODO: Upgrade from old version of RS.NET (the one distributed with the combined MSI)/Downgrade from new RS.NET MSI to combined MSI - ask Hristov what these mean from the gh issue - whether users should be doing something to upgrade/downgrade or is it supposed to happen automatically and what does this upgrade/downgrade mean after all \ No newline at end of file diff --git a/implementer-guide/setup/installation.md b/implementer-guide/setup/installation.md index 7a375dd1..e32ee2af 100644 --- a/implementer-guide/setup/installation.md +++ b/implementer-guide/setup/installation.md @@ -10,8 +10,12 @@ position: 200 # Report Server Installation +>note This article covers the installation of Telerik Report Server for .NET Framework 4.6.2. Starting from **2025 Q4**, Report Server for .NET (RS.NET) has its own dedicated MSI installer. For RS.NET installation instructions, check the [Report Server for .NET Installation on Windows]({%slug dotnet-installation-on-windows%}) article. + The Report Server web application is installed by a Windows MSI installer, which deploys two applications: a website named _Telerik Report Server_, automatically registered with its own application pool in the machine's IIS, and a non-UI application named _Telerik.ReportServer.ServiceAgent_, registered as a Windows Service. The Report Server web application is accessible by default on HTTP port 83 and the Service Agent on HTTP port 82. +TODO: mention what the msi for 462 is called + ## ReportServerUser, LocalSystem Indentity and Dedicated Users ### ReportServerUser From 770a6448f8f022e32beb9c7df33025af5edec771 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Fri, 31 Oct 2025 16:58:46 +0200 Subject: [PATCH 02/24] docs: refactor rs.net article and move troubleshooting to kb --- _config.yml | 3 + dotnet-docs/windows-installation.md | 69 +++++++++---------- implementer-guide/setup/installation.md | 10 ++- .../setup/system-requirements.md | 2 +- ...nual-configuration-rs-net-service-agent.md | 52 ++++++++++++++ 5 files changed, 97 insertions(+), 39 deletions(-) create mode 100644 knowledge-base/manual-configuration-rs-net-service-agent.md diff --git a/_config.yml b/_config.yml index 2e7d04ef..d173c73c 100644 --- a/_config.yml +++ b/_config.yml @@ -116,6 +116,9 @@ defaults: # Aliases available in the markdown template. The below will expand {{site.foo}} to Bar in the output # "foo": "Bar" +suiteversion: "2025 Q3" +buildversion: "19.2.25.1001" +reportserverversion: "11.2.25.1001" # Feedback Form Product code productCode: REPSERVER diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 95c4de94..39ada6b1 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -1,7 +1,7 @@ --- title: Installation on Windows -page_title: Installing ReportServer.NET on Windows -description: "Learn about the specifics, recommendations, and available approaches for installing the Telerik Report Server for .NET on Windows." +page_title: Installing Report Server for .NET on Windows +description: "Learn how to install Telerik Report Server for .NET on Windows using the dedicated MSI installer, including prerequisites, step-by-step installation, and troubleshooting." slug: dotnet-installation-on-windows tags: installation,dotnet,windows published: True @@ -10,58 +10,55 @@ position: 2 # Report Server for .NET: Installation on Windows -Starting from **2025 Q4**, a dedicated Report Server for .NET (RS.NET) installer is introduced. This article explains the installation steps and the differences from the Report Server for .NET Framework installer. +Starting from 2025 Q4, a dedicated Report Server for .NET (RS.NET) installer is available. This article explains how to install RS.NET on Windows and covers the available installation scenarios. -## Prerequisites - -RS.NET is an ASP.NET Core web application that requires the [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment. Install this module following the [Install the ASP.NET Core Module/Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0#install-the-aspnet-core-modulehosting-bundle) instructions before proceeding. The installation wizard will display a warning if this module is not available. - -## Installation Process +> Prior to 2025 Q4, RS.NET was distributed with the [.NET Framework 4.6.2 installer]({%slug installation%}). If you use an older version, make sure to click **Customize** during installation to include RS.NET. -TODO: mention what the msi is called and guide the user through the installation steps (go to downloads, etc.). while guiding, mention that currently there is no examples/migration tool (possibly in a note) - -The installer automatically assigns available ports for RS.NET and RS.NET Service Agent. By default, these are ports 81 and 84 respectively, but it can assign the next available ones if these are already in use. +## Prerequisites -![Use the button Customize to allow installing the Report Server for .NET](../images/rs-net-images/rs-customize.png) +Before installing RS.NET, ensure you have the following components installed: -## Installed Assets +- [System Requirements]({%slug system-requirements%}) +- [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment -The __RS.NET__ is installed in `{Installation Folder}\Telerik Report Server\Telerik.ReportServer.Web.NET`. The cross-platform distribution of RS.NET is in the `_non-windows` subfolder. +> The installation wizard displays a warning if the ASP.NET Core Hosting Bundle is not available. Ignoring it is not recommended, as this makes the installed Report Server non-functional. -The __RS.NET Service Agent__ is installed in `{Installation Folder}\Telerik Report Server\Services\.NET`. The cross-platform distribution of RS.NET Service Agent is in the `_non-windows` subfolder. +## Downloading the Installer -TODO: explain this further? what is the purpose of the cross-platform distribution now that RS.NET can be installed on Linux through the dedicated installer? there doesn't seem to be such a folder anymore. maybe move this whole section at the end of the article to keep the correct flow of actions (installation > configuration > additional details) +To download the RS.NET installer: -## Configuration +1. Navigate to [Downloads | Your Account](https://www.telerik.com/account/downloads). +1. Click **Progress® Telerik® Report Server**. +1. Select the desired version from the dropdown menu, then locate `Telerik_ReportServer_NET_{Your Version}.msi` and click on it to download the installer. -### Automatic Configuration on Windows +## Installing Report Server for .NET -The installer is supposed to initially configure both RS.NET and RS.NET Service Agent on Windows, making them ready-to-run. If the automatic configuration fails, check the [instructions for manual configuration](#manual-configuration-on-windows). +To install RS.NET for the first time: -TODO: what a fail could mean here? a crash in the installer (likely not since no assets would be installed to be checked) or that there is an error once RS.NET is opened in the browser? maybe move this sentence at the end of the installation process and move installed assets at the end of the article to keep the correct flow of actions +1. Double-click the downloaded MSI file to start the installer. +1. Read the license agreement and click **I Agree - Continue**. +1. Optionally, click **Customize** to customize the installed options, then click **Next**. +1. Choose a user option and click **Next**. + > Creating a dedicated Windows user is recommended for security purposes. For more information about these user options, see [ReportServerUser, LocalSystem Identity and Dedicated Users]({%slug installation%}#report-server-user-localsystem-identity-and-dedicated-users). +1. Click **Install** to proceed with the installation. -### Initialization process +The installer automatically creates IIS applications on port 81 (RS.NET) and port 82 (RS.NET Service Agent). If these ports are unavailable, it assigns the next available ones. -TODO: maybe explain 2 and 3 in the installed assets section? make 1 longer +When you first access RS.NET, you will be prompted to configure storage and register an administrator user. -1. When the Report Server is started for the first time, the user is supposed to pass the _Configure Storage_ and _Register Administrator_ pages. The settings from these pages are stored in a file named `ReportServerAdmin.json`. -1. Next, the RS.NET checks its `appsettings.json` configuration file for the key __InitialAgentUrl__. If the installation has passed successfully, the key must exist and must have a valid value like __http://localhost:84__. This is where the MSI installation file for Windows has registered the __RS.NET Service Agent__. -1. The RS.NET calls the above URL and passes the storage settings to its Service Agent. They are saved in the file `ServiceAgent.json` in the RS.NET Service Agent's directory. If such a file does not exist, the agent was not initialized or registered in the IIS. +## Upgrading Report Server for .NET -### Manual Configuration on Windows +To upgrade RS.NET from a previous version, run the new installer MSI file and follow the same installation steps mentioned in the [Installing Report Server for .NET](#installing-report-server-for-net) section. -1. Delete the file `\Services\.NET\ServiceAgent.json` from RS.NET Service Agent's folder if it exists. -1. Test whether the RS.NET Service Agent responds by calling the RS.NET Service Agent endpoint `/api/system/isalive` from the browser. By default, this would be the URL `http://localhost:84/api/system/isalive`. +When you upgrade from the combined MSI installer (versions prior to 2025 Q4), environment variables (such as encryption keys) are automatically migrated from the old `RSUser` to the new one. - If the agent is working, the result must be __HTTP ERROR 401 - Unauthorized__. +>caution The RS.NET installer does not support automatic backup. Make sure to perform a [manual storage backup]({%slug storage-backup%}#manual-backup) before upgrading to avoid data loss. - If the agent is not working, the result should be __404 - Not Found__. +## Troubleshooting -1. Open RS.NET's `appsettings.json` configuration file and add/edit the key `"InitialAgentUrl": "http://localhost:84"`. The value in the example assumes the RS.NET Service Agent is running on port _84_. Change the URL based on your settings. -1. Restart the RS.NET and RS.NET Service Agent. -1. Check the RS.NET's _Configuration_ -> _ServiceAgent_ page. The entry `"DefaultServiceAgent" : "http://localhost:84"` should now be present. The URL may differ, depending on your settings. -1. To use the RS.NET Service Agent, ensure the _Mail Server_ settings in _Configuration_ page are valid. +If scheduled tasks, data alerts, or email functionality is not working, the [Report Server Agent]({%slug service-agent%}) connection may not have configured automatically. See [Manual Configuration of RS.NET Service Agent Connection]({%slug manual-configuration-rs-net-service-agent%}) for detailed steps. -TODO: what restart means in step 4? iisreset/recycling the app pool for rs.net and restarting the service agent through services.msc > rsnet service agent > restart? maybe change the section title to "debugging" to let know users are supposed to do this as last resort when the automatic configuration fails. explain that the pages that are mentioned have to be opened in the browser +For issues like missing or corrupt files, use the installer's repair functionality: -TODO: Upgrade from old version of RS.NET (the one distributed with the combined MSI)/Downgrade from new RS.NET MSI to combined MSI - ask Hristov what these mean from the gh issue - whether users should be doing something to upgrade/downgrade or is it supposed to happen automatically and what does this upgrade/downgrade mean after all \ No newline at end of file +1. Run the same MSI installer again and click **Next**. +2. Select **Repair** to start the process. \ No newline at end of file diff --git a/implementer-guide/setup/installation.md b/implementer-guide/setup/installation.md index e32ee2af..cd6919e6 100644 --- a/implementer-guide/setup/installation.md +++ b/implementer-guide/setup/installation.md @@ -14,9 +14,15 @@ position: 200 The Report Server web application is installed by a Windows MSI installer, which deploys two applications: a website named _Telerik Report Server_, automatically registered with its own application pool in the machine's IIS, and a non-UI application named _Telerik.ReportServer.ServiceAgent_, registered as a Windows Service. The Report Server web application is accessible by default on HTTP port 83 and the Service Agent on HTTP port 82. -TODO: mention what the msi for 462 is called +## How to Download and Run the Installer? -## ReportServerUser, LocalSystem Indentity and Dedicated Users +To get started with the installation process, you need to download the MSI installer from your Telerik account: + +1. Navigate to [Downloads | Your Account](https://www.telerik.com/account/downloads). +1. Click **Progress® Telerik® Report Server**. +1. Select the desired version from the dropdown menu, then locate `Telerik_ReportServer_NET_[version].msi` and click on it to download the installer. + +## ReportServerUser, LocalSystem Identity and Dedicated Users ### ReportServerUser diff --git a/implementer-guide/setup/system-requirements.md b/implementer-guide/setup/system-requirements.md index 14c92da5..8bcf7cc8 100644 --- a/implementer-guide/setup/system-requirements.md +++ b/implementer-guide/setup/system-requirements.md @@ -21,7 +21,7 @@ position: 100 - **Operating System** - Windows or Linux platform - **Web Server** - ASP.NET Core web server, e.g. IIS 7+, Kestrel. If **IIS** is used, the [ASP.NET Core Module (ANCM) for IIS](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module) must be installed. -- **Runtimes** - [ASP.NET Core 8+ Runtim](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) +- **Runtimes** - [ASP.NET Core 8+ Runtime](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) ## Client diff --git a/knowledge-base/manual-configuration-rs-net-service-agent.md b/knowledge-base/manual-configuration-rs-net-service-agent.md new file mode 100644 index 00000000..9fe92133 --- /dev/null +++ b/knowledge-base/manual-configuration-rs-net-service-agent.md @@ -0,0 +1,52 @@ +--- +title: Manual Configuration of RS.NET Service Agent Connection +description: "Learn how to manually configure the connection between Report Server for .NET and its Service Agent when automatic configuration fails." +type: troubleshooting +page_title: Manual Configuration of RS.NET Service Agent Connection +slug: manual-configuration-rs-net-service-agent +tags: rs.net,service-agent,configuration,troubleshooting,installation +res_type: kb +--- + +## Environment + + + + + + + + + + + + +
ProductProgress® Telerik® Report Server
Product Version2025 Q4
+ +## Description + +During RS.NET installation, the installer automatically configures the connection between the RS.NET web application and the RS.NET Service Agent. However, if the automatic configuration fails, you may need to manually configure this connection. In case the automatic configuration fails, opening `http://localhost:82/api/system/isalive` in the browser returns `404`. + +> For versions prior to 2025 Q4 that relied on a combined installer for both RS and RS.NET, the RS.NET Service Agent is likely hosted on port 84 instead, and the URL should be `http://localhost:84/api/system/isalive`. + +The RS.NET initialization follows this process: + +1. When RS.NET starts for the first time, you go through the **Configure Storage** and **Register Administrator** pages. As a result, the settings are stored in the `ReportServerAdmin.json` file. +1. RS.NET checks its `appsettings.json` configuration file for the `InitialAgentUrl` key. This should contain a valid URL like `http://localhost:82` where the Service Agent is registered. +1. RS.NET calls the Service Agent URL and passes storage settings to it. These are saved in `ServiceAgent.json` in the Service Agent's directory. + +### Manual Configuration Steps + +If the automatic configuration fails, follow these steps: + +1. Delete the file `{Installation Folder}\Telerik Report Server .NET\Services\ServiceAgent.json` from RS.NET Service Agent's folder if it exists. +1. Test whether the RS.NET Service Agent responds by calling the RS.NET Service Agent endpoint `/api/system/isalive` from the browser. By default, this is the URL `http://localhost:82/api/system/isalive`. +1. Open RS.NET's `appsettings.json` configuration file and add/edit the key `"InitialAgentUrl": "http://localhost:82"`. The value in the example assumes the RS.NET Service Agent is running on port _82_. Change the URL based on your settings. +1. Restart the RS.NET and RS.NET Service Agent. +1. Check the RS.NET's **Configuration** -> **ServiceAgent** page. The entry `"DefaultServiceAgent" : "http://localhost:82"` should now be present. The URL may differ, depending on your settings. +1. To use the RS.NET Service Agent, ensure the **Mail Server** settings in **Configuration** page are valid. + +## See Also + +* [Report Server for .NET Installation on Windows]({%slug dotnet-installation-on-windows%}) +* [Troubleshooting Report Server for .NET]({%slug troubleshoot-report-server-net%}) \ No newline at end of file From b74bf920b2d96dea85c17fb154e937f653702e12 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Fri, 31 Oct 2025 17:25:25 +0200 Subject: [PATCH 03/24] docs: review article --- dotnet-docs/windows-installation.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 39ada6b1..4854ecde 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -37,9 +37,8 @@ To install RS.NET for the first time: 1. Double-click the downloaded MSI file to start the installer. 1. Read the license agreement and click **I Agree - Continue**. -1. Optionally, click **Customize** to customize the installed options, then click **Next**. -1. Choose a user option and click **Next**. - > Creating a dedicated Windows user is recommended for security purposes. For more information about these user options, see [ReportServerUser, LocalSystem Identity and Dedicated Users]({%slug installation%}#report-server-user-localsystem-identity-and-dedicated-users). +1. Optionally, choose **Customize** to customize the installed options, then click **Next**. +1. Choose a user option and click **Next**. Creating a dedicated Windows user is recommended for security purposes. For more information about these user options, see [ReportServerUser, LocalSystem Identity and Dedicated Users]({%slug installation%}#reportserveruser-localsystem-identity-and-dedicated-users). 1. Click **Install** to proceed with the installation. The installer automatically creates IIS applications on port 81 (RS.NET) and port 82 (RS.NET Service Agent). If these ports are unavailable, it assigns the next available ones. @@ -56,7 +55,7 @@ When you upgrade from the combined MSI installer (versions prior to 2025 Q4), en ## Troubleshooting -If scheduled tasks, data alerts, or email functionality is not working, the [Report Server Agent]({%slug service-agent%}) connection may not have configured automatically. See [Manual Configuration of RS.NET Service Agent Connection]({%slug manual-configuration-rs-net-service-agent%}) for detailed steps. +If scheduled tasks, data alerts, or email functionality is not working, the [Report Server Agent]({%slug service-agent%}) connection may not have configured automatically. See [Manual Configuration of RS.NET Service Agent Connection]({%slug manual-configuration-rs-net-service-agent%}) for detailed steps on how to do this manually. For issues like missing or corrupt files, use the installer's repair functionality: From 500c222ebd9c9959e6d659de8558095e7aedf9c5 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Thu, 6 Nov 2025 18:05:10 +0200 Subject: [PATCH 04/24] chore: refine the article a bit --- dotnet-docs/windows-installation.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 4854ecde..fd873644 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -12,7 +12,7 @@ position: 2 Starting from 2025 Q4, a dedicated Report Server for .NET (RS.NET) installer is available. This article explains how to install RS.NET on Windows and covers the available installation scenarios. -> Prior to 2025 Q4, RS.NET was distributed with the [.NET Framework 4.6.2 installer]({%slug installation%}). If you use an older version, make sure to click **Customize** during installation to include RS.NET. +> Prior to 2025 Q4, RS.NET was distributed with the [.NET Framework 4.6.2 installer]({%slug installation%}). If you use an older version that features this combined installer, make sure to click **Customize** during installation to include RS.NET. ## Prerequisites @@ -38,7 +38,8 @@ To install RS.NET for the first time: 1. Double-click the downloaded MSI file to start the installer. 1. Read the license agreement and click **I Agree - Continue**. 1. Optionally, choose **Customize** to customize the installed options, then click **Next**. -1. Choose a user option and click **Next**. Creating a dedicated Windows user is recommended for security purposes. For more information about these user options, see [ReportServerUser, LocalSystem Identity and Dedicated Users]({%slug installation%}#reportserveruser-localsystem-identity-and-dedicated-users). + >caution The RS.NET installer currently does not currently include SDK examples. This may be added in future releases. +1. Choose a user option and click **Next**. Creating a dedicated Windows user (`RSUserNET`) is recommended for security purposes. For more information about the available user options, see [ReportServerUser, LocalSystem Identity and Dedicated Users]({%slug installation%}#reportserveruser-localsystem-identity-and-dedicated-users). 1. Click **Install** to proceed with the installation. The installer automatically creates IIS applications on port 81 (RS.NET) and port 82 (RS.NET Service Agent). If these ports are unavailable, it assigns the next available ones. @@ -49,7 +50,7 @@ When you first access RS.NET, you will be prompted to configure storage and regi To upgrade RS.NET from a previous version, run the new installer MSI file and follow the same installation steps mentioned in the [Installing Report Server for .NET](#installing-report-server-for-net) section. -When you upgrade from the combined MSI installer (versions prior to 2025 Q4), environment variables (such as encryption keys) are automatically migrated from the old `RSUser` to the new one. +When upgrading from the combined MSI installer (versions prior to 2025 Q4), environment variables (such as encryption keys) are automatically migrated to the newly selected user option (for example, `RSUserNET` if creating a dedicated Windows user). >caution The RS.NET installer does not support automatic backup. Make sure to perform a [manual storage backup]({%slug storage-backup%}#manual-backup) before upgrading to avoid data loss. From 1703f1ed990ac593f5bca0a02108c310f3dda1fa Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Thu, 6 Nov 2025 18:06:30 +0200 Subject: [PATCH 05/24] chore: remove unused parameters --- _config.yml | 3 --- 1 file changed, 3 deletions(-) diff --git a/_config.yml b/_config.yml index d173c73c..2e7d04ef 100644 --- a/_config.yml +++ b/_config.yml @@ -116,9 +116,6 @@ defaults: # Aliases available in the markdown template. The below will expand {{site.foo}} to Bar in the output # "foo": "Bar" -suiteversion: "2025 Q3" -buildversion: "19.2.25.1001" -reportserverversion: "11.2.25.1001" # Feedback Form Product code productCode: REPSERVER From b027304454ffc09949b9bc1a3252af7a0a817004 Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:29:57 +0200 Subject: [PATCH 06/24] Update dotnet-docs/windows-installation.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index fd873644..ee5b5f1f 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -10,7 +10,7 @@ position: 2 # Report Server for .NET: Installation on Windows -Starting from 2025 Q4, a dedicated Report Server for .NET (RS.NET) installer is available. This article explains how to install RS.NET on Windows and covers the available installation scenarios. +Starting with 2025 Q4, a dedicated Report Server for .NET (RS.NET) installer is available. This article explains how to install RS.NET on Windows and covers the available installation scenarios. > Prior to 2025 Q4, RS.NET was distributed with the [.NET Framework 4.6.2 installer]({%slug installation%}). If you use an older version that features this combined installer, make sure to click **Customize** during installation to include RS.NET. From 435728bb310c127b344ac5fdca356cb064fd472d Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:30:11 +0200 Subject: [PATCH 07/24] Update dotnet-docs/windows-installation.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index ee5b5f1f..87c7175e 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -16,7 +16,7 @@ Starting with 2025 Q4, a dedicated Report Server for .NET (RS.NET) installer is ## Prerequisites -Before installing RS.NET, ensure you have the following components installed: +Before installing RS.NET, ensure that: - [System Requirements]({%slug system-requirements%}) - [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment From 68b8eb7f1efc1374a3fcd8cd19b8c6a56aae3d72 Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:30:23 +0200 Subject: [PATCH 08/24] Update dotnet-docs/windows-installation.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 87c7175e..4a862225 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -18,7 +18,7 @@ Starting with 2025 Q4, a dedicated Report Server for .NET (RS.NET) installer is Before installing RS.NET, ensure that: -- [System Requirements]({%slug system-requirements%}) +- Your system [meets the requirements]({%slug system-requirements%}) - [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment > The installation wizard displays a warning if the ASP.NET Core Hosting Bundle is not available. Ignoring it is not recommended, as this makes the installed Report Server non-functional. From 1c1d1fa8475d75a139bdb4b1e3a0ad1ed0ea5fc7 Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:30:39 +0200 Subject: [PATCH 09/24] Update dotnet-docs/windows-installation.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 4a862225..b9dd9d43 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -19,7 +19,7 @@ Starting with 2025 Q4, a dedicated Report Server for .NET (RS.NET) installer is Before installing RS.NET, ensure that: - Your system [meets the requirements]({%slug system-requirements%}) -- [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment +- [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment is installed. > The installation wizard displays a warning if the ASP.NET Core Hosting Bundle is not available. Ignoring it is not recommended, as this makes the installed Report Server non-functional. From 87466301cc69dce55706b1edae54e84cf2a966e3 Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:30:49 +0200 Subject: [PATCH 10/24] Update dotnet-docs/windows-installation.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index b9dd9d43..13941fee 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -21,7 +21,7 @@ Before installing RS.NET, ensure that: - Your system [meets the requirements]({%slug system-requirements%}) - [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment is installed. -> The installation wizard displays a warning if the ASP.NET Core Hosting Bundle is not available. Ignoring it is not recommended, as this makes the installed Report Server non-functional. +> The installation wizard displays a warning if the ASP.NET Core Hosting Bundle is not available. Ignoring it makes the installed Report Server non-functional. ## Downloading the Installer From 1d6ba309f456ad9e13a45588e435c8a8f19a2072 Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:31:05 +0200 Subject: [PATCH 11/24] Update knowledge-base/manual-configuration-rs-net-service-agent.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- knowledge-base/manual-configuration-rs-net-service-agent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/manual-configuration-rs-net-service-agent.md b/knowledge-base/manual-configuration-rs-net-service-agent.md index 9fe92133..b1e192e1 100644 --- a/knowledge-base/manual-configuration-rs-net-service-agent.md +++ b/knowledge-base/manual-configuration-rs-net-service-agent.md @@ -29,7 +29,7 @@ During RS.NET installation, the installer automatically configures the connectio > For versions prior to 2025 Q4 that relied on a combined installer for both RS and RS.NET, the RS.NET Service Agent is likely hosted on port 84 instead, and the URL should be `http://localhost:84/api/system/isalive`. -The RS.NET initialization follows this process: +The automatic RS.NET configuration and initialization process involves the following steps: 1. When RS.NET starts for the first time, you go through the **Configure Storage** and **Register Administrator** pages. As a result, the settings are stored in the `ReportServerAdmin.json` file. 1. RS.NET checks its `appsettings.json` configuration file for the `InitialAgentUrl` key. This should contain a valid URL like `http://localhost:82` where the Service Agent is registered. From 548c4761937cb1838ab5f456e5eb16f539db4e2e Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:31:14 +0200 Subject: [PATCH 12/24] Update knowledge-base/manual-configuration-rs-net-service-agent.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- knowledge-base/manual-configuration-rs-net-service-agent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/manual-configuration-rs-net-service-agent.md b/knowledge-base/manual-configuration-rs-net-service-agent.md index b1e192e1..cec01618 100644 --- a/knowledge-base/manual-configuration-rs-net-service-agent.md +++ b/knowledge-base/manual-configuration-rs-net-service-agent.md @@ -25,7 +25,7 @@ res_type: kb ## Description -During RS.NET installation, the installer automatically configures the connection between the RS.NET web application and the RS.NET Service Agent. However, if the automatic configuration fails, you may need to manually configure this connection. In case the automatic configuration fails, opening `http://localhost:82/api/system/isalive` in the browser returns `404`. +During RS.NET installation, the installer automatically configures the connection between the RS.NET web application and the RS.NET Service Agent. However, if the automatic configuration fails, you may need to [manually configure this connection](#solution). In case the automatic configuration fails, opening `http://localhost:82/api/system/isalive` in the browser returns `404`. > For versions prior to 2025 Q4 that relied on a combined installer for both RS and RS.NET, the RS.NET Service Agent is likely hosted on port 84 instead, and the URL should be `http://localhost:84/api/system/isalive`. From 41d3d349fb42f315d226eda56e817682e66393a9 Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:31:32 +0200 Subject: [PATCH 13/24] Update knowledge-base/manual-configuration-rs-net-service-agent.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- knowledge-base/manual-configuration-rs-net-service-agent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/manual-configuration-rs-net-service-agent.md b/knowledge-base/manual-configuration-rs-net-service-agent.md index cec01618..ccb7fc66 100644 --- a/knowledge-base/manual-configuration-rs-net-service-agent.md +++ b/knowledge-base/manual-configuration-rs-net-service-agent.md @@ -35,7 +35,7 @@ The automatic RS.NET configuration and initialization process involves the follo 1. RS.NET checks its `appsettings.json` configuration file for the `InitialAgentUrl` key. This should contain a valid URL like `http://localhost:82` where the Service Agent is registered. 1. RS.NET calls the Service Agent URL and passes storage settings to it. These are saved in `ServiceAgent.json` in the Service Agent's directory. -### Manual Configuration Steps +## Solution If the automatic configuration fails, follow these steps: From 675b0bec8333f5fc4037e17ac8355a643a6bb30a Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:31:45 +0200 Subject: [PATCH 14/24] Update knowledge-base/manual-configuration-rs-net-service-agent.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- knowledge-base/manual-configuration-rs-net-service-agent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/manual-configuration-rs-net-service-agent.md b/knowledge-base/manual-configuration-rs-net-service-agent.md index ccb7fc66..1a767c25 100644 --- a/knowledge-base/manual-configuration-rs-net-service-agent.md +++ b/knowledge-base/manual-configuration-rs-net-service-agent.md @@ -37,7 +37,7 @@ The automatic RS.NET configuration and initialization process involves the follo ## Solution -If the automatic configuration fails, follow these steps: +If the automatic configuration fails, configure the connection manually by following these steps: 1. Delete the file `{Installation Folder}\Telerik Report Server .NET\Services\ServiceAgent.json` from RS.NET Service Agent's folder if it exists. 1. Test whether the RS.NET Service Agent responds by calling the RS.NET Service Agent endpoint `/api/system/isalive` from the browser. By default, this is the URL `http://localhost:82/api/system/isalive`. From 76992c89c7d3e996888a56252dc614101ecf2331 Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:32:07 +0200 Subject: [PATCH 15/24] Apply suggestion from @yordan-mitev Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 13941fee..204ff3de 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -36,7 +36,7 @@ To download the RS.NET installer: To install RS.NET for the first time: 1. Double-click the downloaded MSI file to start the installer. -1. Read the license agreement and click **I Agree - Continue**. +1. Read and accept the license agreement. 1. Optionally, choose **Customize** to customize the installed options, then click **Next**. >caution The RS.NET installer currently does not currently include SDK examples. This may be added in future releases. 1. Choose a user option and click **Next**. Creating a dedicated Windows user (`RSUserNET`) is recommended for security purposes. For more information about the available user options, see [ReportServerUser, LocalSystem Identity and Dedicated Users]({%slug installation%}#reportserveruser-localsystem-identity-and-dedicated-users). From bcb9b849ccf5cd2df27228872b8ad7038716279e Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:32:16 +0200 Subject: [PATCH 16/24] Apply suggestion from @yordan-mitev Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 204ff3de..fb277c56 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -38,7 +38,7 @@ To install RS.NET for the first time: 1. Double-click the downloaded MSI file to start the installer. 1. Read and accept the license agreement. 1. Optionally, choose **Customize** to customize the installed options, then click **Next**. - >caution The RS.NET installer currently does not currently include SDK examples. This may be added in future releases. + >caution The RS.NET installer currently does not include SDK examples. This may be added in future releases. 1. Choose a user option and click **Next**. Creating a dedicated Windows user (`RSUserNET`) is recommended for security purposes. For more information about the available user options, see [ReportServerUser, LocalSystem Identity and Dedicated Users]({%slug installation%}#reportserveruser-localsystem-identity-and-dedicated-users). 1. Click **Install** to proceed with the installation. From 5f1bd35ab1c60b5c5994b236a38f5e14a762df05 Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:32:28 +0200 Subject: [PATCH 17/24] Apply suggestion from @yordan-mitev Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index fb277c56..6f34bb3a 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -48,7 +48,7 @@ When you first access RS.NET, you will be prompted to configure storage and regi ## Upgrading Report Server for .NET -To upgrade RS.NET from a previous version, run the new installer MSI file and follow the same installation steps mentioned in the [Installing Report Server for .NET](#installing-report-server-for-net) section. +To upgrade RS.NET from a previous version, download and run a new installer file and follow the [installation steps](#installing-report-server-for-net). When upgrading from the combined MSI installer (versions prior to 2025 Q4), environment variables (such as encryption keys) are automatically migrated to the newly selected user option (for example, `RSUserNET` if creating a dedicated Windows user). From 7cd8bb4b6527823b4209e9534cd4226c9049bd9b Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Fri, 7 Nov 2025 17:33:11 +0200 Subject: [PATCH 18/24] Apply suggestions from code review Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- dotnet-docs/windows-installation.md | 4 ++-- implementer-guide/setup/installation.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 6f34bb3a..0c3f43df 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -29,7 +29,7 @@ To download the RS.NET installer: 1. Navigate to [Downloads | Your Account](https://www.telerik.com/account/downloads). 1. Click **Progress® Telerik® Report Server**. -1. Select the desired version from the dropdown menu, then locate `Telerik_ReportServer_NET_{Your Version}.msi` and click on it to download the installer. +1. Select the desired version from the dropdown menu, then locate and click `Telerik_ReportServer_NET_{Your Version}.msi` to download the installer. ## Installing Report Server for .NET @@ -56,7 +56,7 @@ When upgrading from the combined MSI installer (versions prior to 2025 Q4), envi ## Troubleshooting -If scheduled tasks, data alerts, or email functionality is not working, the [Report Server Agent]({%slug service-agent%}) connection may not have configured automatically. See [Manual Configuration of RS.NET Service Agent Connection]({%slug manual-configuration-rs-net-service-agent%}) for detailed steps on how to do this manually. +If scheduled tasks, data alerts, or email functionality is not working, the [Report Server Agent]({%slug service-agent%}) connection may not have been configured automatically. See [Manual Configuration of RS.NET Service Agent Connection]({%slug manual-configuration-rs-net-service-agent%}) for detailed steps on how to do this manually. For issues like missing or corrupt files, use the installer's repair functionality: diff --git a/implementer-guide/setup/installation.md b/implementer-guide/setup/installation.md index cd6919e6..9afbbc8a 100644 --- a/implementer-guide/setup/installation.md +++ b/implementer-guide/setup/installation.md @@ -10,7 +10,7 @@ position: 200 # Report Server Installation ->note This article covers the installation of Telerik Report Server for .NET Framework 4.6.2. Starting from **2025 Q4**, Report Server for .NET (RS.NET) has its own dedicated MSI installer. For RS.NET installation instructions, check the [Report Server for .NET Installation on Windows]({%slug dotnet-installation-on-windows%}) article. +>note This article covers the installation of Telerik Report Server for .NET Framework 4.6.2. Starting with **2025 Q4**, Report Server for .NET (RS.NET) has a dedicated MSI installer. For RS.NET installation instructions, check the [Report Server for .NET Installation on Windows]({%slug dotnet-installation-on-windows%}) article. The Report Server web application is installed by a Windows MSI installer, which deploys two applications: a website named _Telerik Report Server_, automatically registered with its own application pool in the machine's IIS, and a non-UI application named _Telerik.ReportServer.ServiceAgent_, registered as a Windows Service. The Report Server web application is accessible by default on HTTP port 83 and the Service Agent on HTTP port 82. From 1b42b49eedc192f11f919d4dc1485ec60d3c42e3 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Fri, 7 Nov 2025 18:45:36 +0200 Subject: [PATCH 19/24] chore: remove duplicated content --- implementer-guide/setup/installation.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/implementer-guide/setup/installation.md b/implementer-guide/setup/installation.md index 9afbbc8a..09783a58 100644 --- a/implementer-guide/setup/installation.md +++ b/implementer-guide/setup/installation.md @@ -14,14 +14,6 @@ position: 200 The Report Server web application is installed by a Windows MSI installer, which deploys two applications: a website named _Telerik Report Server_, automatically registered with its own application pool in the machine's IIS, and a non-UI application named _Telerik.ReportServer.ServiceAgent_, registered as a Windows Service. The Report Server web application is accessible by default on HTTP port 83 and the Service Agent on HTTP port 82. -## How to Download and Run the Installer? - -To get started with the installation process, you need to download the MSI installer from your Telerik account: - -1. Navigate to [Downloads | Your Account](https://www.telerik.com/account/downloads). -1. Click **Progress® Telerik® Report Server**. -1. Select the desired version from the dropdown menu, then locate `Telerik_ReportServer_NET_[version].msi` and click on it to download the installer. - ## ReportServerUser, LocalSystem Identity and Dedicated Users ### ReportServerUser From 8a9444518378a101274a96abe8f247f0ce27982e Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Mon, 10 Nov 2025 18:06:04 +0200 Subject: [PATCH 20/24] chore: update prerequisites and installation directory info --- dotnet-docs/windows-installation.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 0c3f43df..498024be 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -16,12 +16,13 @@ Starting with 2025 Q4, a dedicated Report Server for .NET (RS.NET) installer is ## Prerequisites -Before installing RS.NET, ensure that: +Before installing RS.NET, ensure that you have the following components installed: -- Your system [meets the requirements]({%slug system-requirements%}) -- [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment is installed. +- [IIS (Internet Information Services)](https://www.iis.net/) +- [.NET 8 and ASP.NET Core 8 Runtimes](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) +- [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment -> The installation wizard displays a warning if the ASP.NET Core Hosting Bundle is not available. Ignoring it makes the installed Report Server non-functional. +> If IIS, .NET 8 Runtime, or ASP.NET Core 8 Runtime are missing, the installer interrupts the process and shows a message explaining what needs to be installed before proceeding. In the case where the ASP.NET Core Module for IIS is not present, the installer shows a warning but allows the installation to continue, since this module can be added later without affecting the initial setup. ## Downloading the Installer @@ -42,6 +43,11 @@ To install RS.NET for the first time: 1. Choose a user option and click **Next**. Creating a dedicated Windows user (`RSUserNET`) is recommended for security purposes. For more information about the available user options, see [ReportServerUser, LocalSystem Identity and Dedicated Users]({%slug installation%}#reportserveruser-localsystem-identity-and-dedicated-users). 1. Click **Install** to proceed with the installation. +By default, the installation directory is `C:\Program Files (x86)\Progress\Telerik Report Server .NET`. You can change this location during the **Customize** step of the installation. Within this directory: + +- RS.NET is installed at `\Telerik.ReportServer.Web`. +- RS.NET Service Agent is installed at `\Services`. + The installer automatically creates IIS applications on port 81 (RS.NET) and port 82 (RS.NET Service Agent). If these ports are unavailable, it assigns the next available ones. When you first access RS.NET, you will be prompted to configure storage and register an administrator user. From 8a3215a758fd65db458e696163ad0d2254cf9057 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Tue, 11 Nov 2025 17:47:55 +0200 Subject: [PATCH 21/24] chore: address review comments --- dotnet-docs/windows-installation.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 498024be..da4f1a95 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -50,15 +50,19 @@ By default, the installation directory is `C:\Program Files (x86)\Progress\Teler The installer automatically creates IIS applications on port 81 (RS.NET) and port 82 (RS.NET Service Agent). If these ports are unavailable, it assigns the next available ones. -When you first access RS.NET, you will be prompted to configure storage and register an administrator user. +When you first access RS.NET, you will be prompted to configure storage and register an administrator user. During this setup, you will also be asked to download [encryption keys]({%slug security%}#encryption) that secure your sensitive RS.NET assets. ## Upgrading Report Server for .NET To upgrade RS.NET from a previous version, download and run a new installer file and follow the [installation steps](#installing-report-server-for-net). -When upgrading from the combined MSI installer (versions prior to 2025 Q4), environment variables (such as encryption keys) are automatically migrated to the newly selected user option (for example, `RSUserNET` if creating a dedicated Windows user). +When upgrading from the combined MSI installer (versions prior to 2025 Q4), the installer automatically migrates: +- Environment variables (such as encryption keys) to the newly selected user option (for example, `RSUserNET` if creating a dedicated Windows user). +- Storage configuration and assets (when using `FileStorage`) to the new RS.NET location. ->caution The RS.NET installer does not support automatic backup. Make sure to perform a [manual storage backup]({%slug storage-backup%}#manual-backup) before upgrading to avoid data loss. +The original RS.NET assets created by the combined installer remain on your system for manual cleanup purposes and are not automatically removed. + +>caution The RS.NET installer does not support automatic backup. When upgrading from one RS.NET installer version to another, consider performing a [manual storage backup]({%slug storage-backup%}#manual-backup) before upgrading to prevent data loss. Automatic backup functionality will be added in a future release. ## Troubleshooting From af94933abb1a374247e47830847218befc83dc61 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Tue, 11 Nov 2025 17:53:29 +0200 Subject: [PATCH 22/24] chore: remove ai suggestion --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index da4f1a95..23f1eb1c 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -60,7 +60,7 @@ When upgrading from the combined MSI installer (versions prior to 2025 Q4), the - Environment variables (such as encryption keys) to the newly selected user option (for example, `RSUserNET` if creating a dedicated Windows user). - Storage configuration and assets (when using `FileStorage`) to the new RS.NET location. -The original RS.NET assets created by the combined installer remain on your system for manual cleanup purposes and are not automatically removed. +The original RS.NET assets created by the combined installer remain on your system and are not automatically removed. >caution The RS.NET installer does not support automatic backup. When upgrading from one RS.NET installer version to another, consider performing a [manual storage backup]({%slug storage-backup%}#manual-backup) before upgrading to prevent data loss. Automatic backup functionality will be added in a future release. From 7bf1357f6a76ccfe0a2784240590832256351020 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Tue, 11 Nov 2025 17:58:22 +0200 Subject: [PATCH 23/24] chore: make the prerequisites info as main info instead of note --- dotnet-docs/windows-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index 23f1eb1c..d8d85adb 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -22,7 +22,7 @@ Before installing RS.NET, ensure that you have the following components installe - [.NET 8 and ASP.NET Core 8 Runtimes](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) - [ASP.NET Core Hosting Bundle](https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0) for IIS deployment -> If IIS, .NET 8 Runtime, or ASP.NET Core 8 Runtime are missing, the installer interrupts the process and shows a message explaining what needs to be installed before proceeding. In the case where the ASP.NET Core Module for IIS is not present, the installer shows a warning but allows the installation to continue, since this module can be added later without affecting the initial setup. +If IIS, .NET 8 Runtime, or ASP.NET Core 8 Runtime are missing, the installer interrupts the process and shows a message explaining what needs to be installed before proceeding. In the case where the ASP.NET Core Module for IIS is not present, the installer shows a warning but allows the installation to continue, since this module can be added later without affecting the initial setup. ## Downloading the Installer From 18394a3a458be8d06b3116292a7bbec45ad92cb8 Mon Sep 17 00:00:00 2001 From: Dimitar Nikolov Date: Tue, 11 Nov 2025 18:38:35 +0200 Subject: [PATCH 24/24] Update windows-installation.md --- dotnet-docs/windows-installation.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/dotnet-docs/windows-installation.md b/dotnet-docs/windows-installation.md index d8d85adb..76439a2a 100644 --- a/dotnet-docs/windows-installation.md +++ b/dotnet-docs/windows-installation.md @@ -39,7 +39,9 @@ To install RS.NET for the first time: 1. Double-click the downloaded MSI file to start the installer. 1. Read and accept the license agreement. 1. Optionally, choose **Customize** to customize the installed options, then click **Next**. - >caution The RS.NET installer currently does not include SDK examples. This may be added in future releases. + + >caution The RS.NET installer currently does not include SDK examples. Those will be added in future releases. + 1. Choose a user option and click **Next**. Creating a dedicated Windows user (`RSUserNET`) is recommended for security purposes. For more information about the available user options, see [ReportServerUser, LocalSystem Identity and Dedicated Users]({%slug installation%}#reportserveruser-localsystem-identity-and-dedicated-users). 1. Click **Install** to proceed with the installation. @@ -71,4 +73,4 @@ If scheduled tasks, data alerts, or email functionality is not working, the [Rep For issues like missing or corrupt files, use the installer's repair functionality: 1. Run the same MSI installer again and click **Next**. -2. Select **Repair** to start the process. \ No newline at end of file +2. Select **Repair** to start the process.