Internet Information Services (IIS) is the Windows web server that receives browser connections to the WebReports website. IIS works with the ASP.NET Core Hosting Bundle to run the application. Installing the IIS role prepares the web host; the WebReports website, HTTPS binding, application pool, files, and database settings are configured later.
Use this procedure for a Windows Server deployment. For the supported server versions and other prerequisites, see WebReports Deployment Requirements and Network Architecture. Docker deployments use WebReports Setup for Docker.
What You Are Installing
| Component | What it does and why it is needed |
|---|---|
| Web Server (IIS) role | Provides Windows web hosting. Its default role services supply the starting set of web-server functions for this installation. |
| Management Tools → IIS Management Console | Provides IIS Manager, the graphical tool used later to configure the WebReports site, application pool, and HTTPS binding. |
| Security → Windows Authentication (conditional) | Adds the IIS authentication service used when the deployment identifies users through Windows accounts. Select it only when Windows Authentication is the chosen sign-in method. |
| ASP.NET Core Hosting Bundle (next step) | Adds the runtime and IIS hosting module used to run WebReports. It is installed separately after IIS. |
Before You Begin
- Confirm administrative access to the intended Windows Server and review the deployment requirements.
- Identify the destination server. Server Manager can manage more than one server; select the one that will host WebReports.
- Confirm the deployment's authentication method. Installing the Windows Authentication role service does not by itself configure WebReports sign-in.
- If IIS is already installed, review its existing role services and add only what the deployment needs. Do not remove roles or change other hosted sites as part of this procedure.
Demo image context: The illustrations below use existing Windows Server wizard references, with demo information edited where applicable. WR-DEMO-SRV and 192.0.2.10 are illustrative labels, not a server or address to enter in your environment. The destination-server example shows Windows Server 2019, which is among the supported versions in the requirements article. Wizard appearance and installed-feature counts can vary. These edited references are not fresh installation captures. Select an image to view it at full size.
Install the Web Server (IIS) Role
- Open Server Manager on the Windows Server or the management computer used to administer it.
- Select Manage → Add Roles and Features. The dashboard's Add roles and features link opens the same wizard.
- If the Before You Begin page appears, review it and select Next.
- On Installation Type, select Role-based or feature-based installation, then Next.
- On Server Selection, choose Select a server from the server pool, select the intended WebReports server, and select Next.
Edited demo example: select the server that will host WebReports. WR-DEMO-SRV and 192.0.2.10 are documentation examples; choose your actual server. Select the image to view it at full size.
Enable Web Server (IIS)
- On Server Roles, select Web Server (IIS).
- If prompted to add required features, leave Include management tools (if applicable) selected and choose Add Features. This includes the IIS Management Console used by the later deployment guide.
- Confirm that Web Server (IIS) is selected, then select Next.
Edited demo example: select Web Server (IIS), then review the management-tools prompt when it appears. Select the image to view it at full size.
A parent role checkbox may show a filled square when only some of its subfeatures are selected. Keep the intended defaults and conditional services; selecting every IIS service is not required by this procedure.
Reference dialog: leave Include management tools selected, then choose Add Features to include the IIS Management Console. Select the image to view it at full size.
- On Features, retain the wizard's selected dependencies and defaults unless your deployment instructions require an additional feature, then select Next.
- Read the Web Server Role (IIS) information page and select Next.
- On Role Services, retain the default IIS role services and verify Management Tools → IIS Management Console is included. Review the conditional Windows Authentication step below before continuing.
The IIS role and its role services are Windows components. The separate ASP.NET Core Hosting Bundle supplies WebReports' runtime and hosting module. See Microsoft's IIS configuration guidance for ASP.NET Core.
Enable Windows Authentication When Required
Windows Authentication uses Windows account identities for sign-in. If this is the method chosen for WebReports, enable its IIS role service before completing the wizard:
- In the IIS role-service tree, expand Web Server → Security.
- Select Windows Authentication.
- Keep the other role-service choices appropriate to your deployment, then select Next.
The IIS tree can also be expanded on the Server Roles page as Web Server (IIS) → Web Server → Security. The focused reference below shows that tree and the Windows Authentication choice.
Focused edited reference: select Windows Authentication only when required by the chosen sign-in method. The pictured installed-feature counts describe the example, not a list of features every deployment must enable. Select the image to view it at full size.
If WebReports will use another authentication method, leave Windows Authentication unselected unless another application on the server requires it. Do not remove an existing role service used by another site. The WebReports website's IIS authentication settings and the matching application settings are completed during deployment.
For background, see Microsoft's Windows Authentication documentation.
Complete the IIS Installation
- On Confirmation, review the destination server and selected components. Confirm the Web Server (IIS) role, IIS Management Console, and Windows Authentication if required.
- Select Install and wait for the operation to finish.
- On Results, confirm installation succeeded on the intended server. Review and resolve any reported failure before continuing.
- Select Close. If Windows reports a pending restart, coordinate and complete it with the server administrator.
Edited result example: check for success on your own destination server before selecting Close. This illustration shows the expected result wording; it is not evidence of a new installation. Select the image to view it at full size.
Verify Before Continuing
- Confirm Server Manager reports that the requested IIS installation or role-service additions succeeded.
- On the server, open Server Manager → Tools → Internet Information Services (IIS) Manager. Confirm the console opens and the intended server is available in its Connections pane.
- If Windows Authentication was required, confirm the role service is installed. The site's authentication configuration is verified during WebReports deployment.
If IIS Manager is missing, review whether IIS Management Console was included. If the role installation failed, review the wizard result and server notifications with the deployment administrator before proceeding.
A successful IIS installation confirms the Windows web host is available. It does not yet verify WebReports, its database connection, HTTPS certificate, folder permissions, or registration.
Next Steps
- Follow Download and Install the ASP.NET Hosting Bundle. Install IIS before the bundle. If the bundle was installed first, repair it after IIS is installed. Complete the restart instructions in that article.
- Return to Installing WebReports on Windows to continue with the application database and remaining installation tasks in order.
- When those prerequisites are ready, use Configure IIS and Deploy WebReports to configure the site, application pool, HTTPS binding, and application settings.





Comments
0 comments
Please sign in to leave a comment.