The process of deploying an ASP.NET Core application to IIS is often simple. However, error signals may frequently be deceptive when anything goes wrong. I just deployed a.NET 10 Web API on Windows Server 2022 and ran into a number of problems that first suggested a missing Hosting Bundle. After troubleshooting for several hours, I came to the conclusion that there might have been multiple setup problems rather than simply one.

In this article, I'll walk you through the exact troubleshooting process I followed. Whether you're facing HTTP Error 500.19, AspNetCoreModuleV2 errors, Hosting Bundle issues, or your application refuses to load after deployment, this guide will help you identify the root cause step by step.

For reference, here's the environment I was working with:

• Windows Server 2022
• IIS 10
• ASP.NET Core .NET 10 Web API
• SQL Server
• Visual Studio 2022

The Initial Problem
After publishing my application to IIS, opening the website immediately displayed the following error:
HTTP Error 500.19 - Internal Server Error
Error Code: 0x8007000d

At first, it looked like IIS couldn't read the application's web.config file. In many cases, this error also appears when the ASP.NET Core Hosting Bundle is missing or IIS cannot load the ASP.NET Core Module.

Instead of reinstalling everything immediately, I decided to troubleshoot the problem systematically.

Step 1: Verify the web.config File
The first thing I checked was the web.config file generated during publishing.

For an ASP.NET Core application hosted in IIS, it should look similar to this:
<aspNetCore
    processPath="dotnet"
    arguments=".\YourApplication.dll"
    stdoutLogEnabled="true"
    stdoutLogFile=".\logs\stdout"
    hostingModel="InProcess" />

I carefully verified:

• The DLL name matched the published application.
• The XML structure was valid.
• The hosting model was correct.
• Stdout logging was enabled for troubleshooting.

Everything looked fine, so I moved to the next step.

Step 2: Check Whether the .NET Runtime Was Installed
The Hosting Bundle depends on the correct .NET runtime being installed.

To verify this, I opened Command Prompt and executed:
dotnet --list-runtimes

The output confirmed that both the ASP.NET Core Runtime and the .NET Runtime were installed.
Microsoft.AspNetCore.App 10.0.x
Microsoft.NETCore.App 10.0.x

If these runtimes are missing, your application will never start, regardless of IIS configuration.

Step 3: Verify the ASP.NET Core Hosting Bundle
Next, I checked whether the Hosting Bundle was installed.

Open:
Control Panel
→ Programs and Features

Look for something similar to:
Microsoft .NET 10.x Windows Server Hosting

If it isn't listed, download and install the correct Hosting Bundle for your .NET version from Microsoft.

If it is already installed, continue troubleshooting instead of reinstalling it immediately.

Step 4: Verify the ASP.NET Core Module
The Hosting Bundle installs the IIS module responsible for running ASP.NET Core applications.

Navigate to:
C:\Program Files\IIS\Asp.Net Core Module\V2

Make sure the following file exists:
aspnetcorev2.dll

If this file is missing, IIS won't be able to launch your application.

Step 5: Verify IIS Module Registration
Even if the DLL exists, IIS must register the module correctly.

Run the following command in PowerShell:
& "$env:windir\System32\inetsrv\appcmd.exe" list modules

Look for:
AspNetCoreModuleV2

If you don't see it, repairing or reinstalling the Hosting Bundle usually resolves the issue.

Step 6: Verify the Global Module Registration
Then verified that IIS had registered the module globally.

Open:
C:\Windows\System32\inetsrv\config\applicationHost.config

Search for:
<globalModules>

Inside the XML there will be section, you should find:

<add
    name="AspNetCoreModuleV2"
    image="%ProgramFiles%\IIS\Asp.Net Core Module\V2\aspnetcorev2.dll" />

If this entry is missing, IIS cannot load ASP.NET Core applications.

Step 7: Verify the IIS Website
Sometimes the simplest things are overlooked.

I checked whether my website was actually running.
Import-Module WebAdministration
Get-Website

The website status should be:
Started

If the site is stopped, start it before continuing.

Step 8: Verify the Application Pool
This turned out to be one of the most important checks.

I opened the Application Pool settings and found:
Managed Runtime Version : v4.0

For ASP.NET Core applications, this setting is incorrect.

The Application Pool should be configured as:

• .NET CLR Version: No Managed Code
• Managed Pipeline: Integrated
• Enable 32-Bit Applications: False

Although ASP.NET Core doesn't use the .NET Framework runtime inside IIS, many deployments are still configured incorrectly with v4.0, which often causes confusion.

Step 9: Verify IIS Bindings
Next, I confirmed that the website bindings were correct.

I verified:

• HTTP binding
• HTTPS binding
• Host name
• SSL certificate

An incorrect host name or missing SSL certificate can prevent requests from reaching your application.

Step 10: Run the Application Outside IIS
This was probably the most useful step during the entire troubleshooting process.

Instead of relying on IIS, I ran the application directly.
cd C:\inetpub\wwwroot\YourApplication
dotnet YourApplication.dll

The application started successfully.

Starting Application...
Application started successfully.

This immediately told me that the application itself was healthy and that the problem was somewhere in IIS rather than the application code.

Whenever you're troubleshooting deployment issues, this should be one of the first tests you perform.

Step 11: Enable Stdout Logging
If the application fails to start inside IIS, enable stdout logging temporarily.
stdoutLogEnabled="true"

After making a request, check the generated log files inside:
logs

These logs often contain the exact exception that caused the application to fail.

Remember to disable stdout logging once the issue has been resolved.

Step 12: Check Event Viewer
Windows Event Viewer provides valuable information when IIS fails to launch an application.

Navigate to:
Event Viewer
→ Windows Logs
→ Application

Look for errors related to:

• IIS AspNetCore Module V2
• IIS-W3SVC-WP
• .NET Runtime

These events often reveal missing dependencies or startup exceptions.

Step 13: Test a Health Check Endpoint
Instead of opening the root URL, I tested my Health Check endpoint.
https://yourdomain.com/health

The response was:
Healthy

This single response confirmed that:

• IIS was working correctly.
• The Hosting Bundle was installed correctly.
• ASP.NET Core Module was working.
• HTTPS was configured properly.
• The application had started successfully.

Health Check endpoints are extremely useful when validating deployments.

Step 14: Test the Application with cURL or PowerShell
You can also verify your deployment without opening a browser.

Using Command Prompt:
curl https://yourdomain.com/health

Or PowerShell:
Invoke-WebRequest https://yourdomain.com/health

Receiving a 200 OK response confirms that IIS is successfully forwarding requests to your application.

Step 15: Verify Swagger Configuration
One thing that often confuses developers is Swagger returning a 404 Not Found error.

In my case, Swagger was only enabled for Development and Staging environments.
if (app.Environment.IsDevelopment() || app.Environment.IsStaging())
{
    app.UseSwagger();
    app.UseSwaggerUI();
}

When deployed to Production, /swagger naturally returned 404.

This wasn't a deployment problem it was simply how the application was configured.

Step 16: Verify the Root Endpoint
Another thing I discovered was that visiting the root URL returned 404 Not Found.

Initially, I thought the deployment had failed.

However, after reviewing my application, I realized I hadn't mapped an endpoint for /.

My application only exposed:

• Controllers
• Health Checks
• SignalR Hub

Since there was no route for /, ASP.NET Core correctly returned 404.

Adding a simple root endpoint solved this.
app.MapGet("/", () =>
{
    return Results.Ok(new
    {
        Application = "My API",
        Status = "Running"
    });
});

Step 17: Verify the Published Files
Before blaming IIS, make sure the publish folder contains all required files.
A standard ASP.NET Core publish output should include:

• Application DLL
• .deps.json
• .runtimeconfig.json
• web.config
• appsettings.json

Missing files can prevent the application from starting correctly.

Step 18: Verify Database Connectivity
Many applications execute database migrations or seed data during startup.
If the SQL Server is unavailable, the connection string is incorrect, or the credentials are invalid, the application may fail before it even starts serving requests.

Always verify your database connectivity as part of deployment troubleshooting.

Complete Troubleshooting Checklist

Before concluding that the Hosting Bundle is the problem, verify the following:

The biggest lesson I learned was not to jump straight to reinstalling the Hosting Bundle.

A deployment issue can originate from several different layers, including:

• Missing .NET Runtime
• Missing Hosting Bundle
• Unregistered ASP.NET Core Module
• Incorrect Application Pool configuration
• Invalid IIS bindings
• Startup exceptions
• Database connection failures
• Missing published files
• Environment-specific configuration
• Missing application routes

By troubleshooting each layer one at a time, it's much easier to identify the real cause without making unnecessary changes.

Conclusion
Deploying ASP.NET Core applications to IIS doesn't have to be frustrating. Most deployment failures can be resolved by following a structured troubleshooting process rather than guessing or repeatedly reinstalling software. I hope this guide saves you time the next time you encounter an IIS deployment issue. If you're deploying ASP.NET Core applications regularly, consider bookmarking this checklist, it's a practical reference that can help diagnose almost every common IIS deployment problem before it becomes a lengthy debugging session.

Today, I am going to show you how to deploy the React App to the IIS server, so let's grab a cup of coffee and start coding.

What is IIS?
IIS stands for "Internet Information Services", which is a web server provided by Microsoft to host the websites and other stuff on the web.

How to enable IIS?
If you have already enabled IIS then you can skip this step. But if you have not enabled it already then follow the below steps:

• Open Control Panel and then click on the "Programs and Features".
• Click on "Turn Windows features on or off".
• Select Internet Information Services and click on the OK button.
• To see whether or not IIS is enabled, press Windows + R key and type inetmgr and click on OK.
• IIS Manager is open.

Create a Simple React App
Open a command prompt or your favorite terminal and type the below command to create a react app.
    npx create-react-app my-react-app

After successfully creating the app go to the new app.
    cd my-react-app

To see how it look likes type the below command.
    npm start

and it will start the development server and navigate you to http://localhost:3000/

You can see the default landing page: 

To host an app in any web server we first need to create a production build. To create a production build of our react app use the below command.
    npm run build

The output of the above command creates a new build folder inside the project which contains production build. So far we have created a React app & created a production build of that app. Now the next step is to deploy it on IIS. Press Windows + R key and write inetmgr to open the IIS Manager. You can see the below screen.

First, we will create a new Application Pool, so right-click on Application Pools and click on Add Application Pool. Then give it a name as you want and click on OK button.
After that right-click on the new app pool and select Advanced Settings. You will see the below window.

Then click on Identity and choose a Custom account and click on the set button and then add your windows credentials and click on OK.
After that right-click on Sites and then click on Add Website. Add the Site name and select application pool which we created earlier. After that under the physical path section, you have to give the path of build folder & also give the port number where you want to host.

Now right click on new website i.e ReactApp -> Manage Website -> Browse. Your react app is now successfully deployed.

Now the next step is to add routing in our react application. So I have created 2 components and also added react-router-dom package for routing. Here we are not going into detail about react routing.

Home page

Blog page

Create a production build again and try to browse the application which we hosted on IIS. You will see the application is working fine but now try to refresh the page and see what happens. You will get the below error.

So to fix this issue you have to install URL Rewrite module. After successful installation, you have to create a web.config file under public folder of app and copy-paste the below content into it.
    <?xml version="1.0"?>
    <configuration>
    <system.webServer>
    <rewrite>
    <rules>
    <rule name="React Routes" stopProcessing="true">
    <match url=".*" />
    <conditions logicalGrouping="MatchAll">
    <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
    <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
    <add input="{REQUEST_URI}" pattern="^/(api)" negate="true" />
    </conditions>
    <action type="Rewrite" url="/" />
    </rule>
    </rules>
    </rewrite>
    </system.webServer>
    </configuration>

Again build the application in production mode and browse. So now if you refresh the app you will not get an error and will be able to see the correct page. That's it -- so you have successfully created and deployed React application into the IIS server.

Conclusion
I hope that you have enjoyed this article, and please do not hesitate to send me your thoughts or comments about what could I have done better.

This is the problem you are having with Response.The way the path is being resolved in the IIS environment is probably the cause of Redirect's incorrect inclusion of the myApp root folder in the URL. Here's how to make it right:

1. 1. Use.Reroute
ResolveUrl ensures that the myApp folder is included in the URL by assisting in determining the right path based on the application root.

protected void Test_RedirectSSM(object sender, EventArgs e)
{
    string url = ResolveUrl("~/UserPages/TestareSSM.aspx");
    Response.Redirect(url);
}

2. Use Request.ApplicationPath
Another approach is to manually build the URL using Request.ApplicationPath, which will ensure that the application’s root folder (myApp) is correctly prefixed in the URL.
protected void Test_RedirectSSM(object sender, EventArgs e)
{
    string url = $"{Request.ApplicationPath}/UserPages/TestareSSM.aspx";
    Response.Redirect(url);
}

3. Absolute Path
If you are dealing with a situation where you must use an absolute path, ensure you correctly structure it, including the full application path:

protected void Test_RedirectSSM(object sender, EventArgs e)
{
    Response.Redirect("https://iis/myApp/UserPages/TestareSSM.aspx");
}

Summary
ResolveUrl("~/...") is often the most reliable and easiest way to ensure URLs are correctly resolved relative to the application root.
Request.ApplicationPath can be used to dynamically construct paths based on where your application is deployed.
Ensure that any absolute URLs used include the entire path, including the myApp portion.

These approaches should help ensure that the redirect URL correctly includes your application's root folder (myApp) when deploying on IIS.

Before data is transmitted over the internet, it is compressed using a widely used technique called GZip. Its primary goal is straightforward: reduce the size of web replies to speed up loading times.

Today, a vast quantity of text-based data, including HTML, JSON, CSS, JavaScript, XML, and more, is sent by web apps. All of this information is sent across the network each time a user accesses a webpage or API. Your program will immediately become slower and feel heavier if these files are huge.

This issue is resolved by GZip compression, which shrinks the answer before it leaves the server.

1. Faster Applications Through Smaller Responses

Most content sent from a server is text, and text compresses extremely well. With GZip, responses can shrink by 60–90%, often even more.

For example:

2. Lower Bandwidth and Hosting Costs
Every byte you send costs something, especially in cloud environments.

When responses are compressed:

• Servers send less data
• Cloud bandwidth usage drops
• API traffic becomes cheaper
• Users save mobile data
• Applications scale better with lower load

For high-traffic APIs, this becomes a huge cost-saving advantage.

3. Better SEO and Web Performance
Google cares deeply about speed. Faster websites rank better and deliver better Core Web Vitals, such as:

• LCP (Largest Contentful Paint)
• FCP (First Contentful Paint)
• Overall loading experience

GZip improves these metrics automatically because it reduces how much content must be downloaded.

In .NET Core, GZip Works Automatically When Hosted on IIS
When a .NET Core application runs behind IIS or IIS Express, you automatically get GZip compression without writing any code. This is because IIS applies compression through its built-in StaticCompressionModule and DynamicCompressionModule, which run before the request reaches your .NET Core application.

So:

• You do not need to add AddResponseCompression()
• You do not need to configure any middleware
• IIS provides GZip automatically for all .NET apps, including .NET Core and .NET 6/7/8
• Visual Studio also uses IIS Express → so compression appears automatically during development

GZip seems like a .NET Core feature, but it is actually IIS doing the work, not the .NET runtime.

GZip is one of the easiest and most impactful optimizations you can use in .NET applications—and understanding how IIS and .NET handle it helps ensure your application performs consistently across all environments. 

How to Set Up IIS Web Server in a Virtual Machine
Internet Information Services is referred to as IIS. It is a Microsoft web server. Websites and web apps are hosted on a Windows server using IIS. We will use Server Manager to install IIS on a virtual machine in this article.

First, launch Server Manager.
First, use an administrator account to access the virtual machine server.
From the Start menu, launch Server Manager. The Windows Server may be managed and various server roles and functionality installed using Server Manager.

Step 2: Add Roles and Features
In Server Manager, click Manage at the top.
Select Add Roles and Features from the menu.

The Add Roles and Features Wizard will open. Click Next to continue.

Step 3: Select Installation Type
On the Installation Type page, keep the default option Role-based or feature-based installation selected.
This option allows us to install a server role such as IIS.

Click Next.

Step 4: Select the Server
On the Server Selection page, select VM Server from the server list.

Step 5: Select Web Server (IIS)
On the Server Roles page, find Web Server (IIS).
Select the checkbox next to Web Server (IIS).

A small popup window will appear. This window shows the features needed for IIS.

Click Add Features.

Then click Next.

Keep default and Click Next to continue.

Click Next to continue.

Make sure all required Role service selected
Then Click Next to continue.

Step 6: Continue with the Installation
The wizard will show the Features and IIS configuration pages.
For a basic IIS installation, we can keep the default settings.
Click Next through the remaining pages until you reach the Confirmation page.

Step 7: Install IIS
On the Confirmation page, check the selected options.
Make sure Web Server (IIS) is selected.
Click Install to start the installation.
Wait for the installation to finish. The installation may take a few minutes.
When the installation is complete, click Close.

Step 8: Check IIS
After installing IIS, we can check if it is working correctly.
Open a web browser on VM Server

Enter the following address:
http://localhost

Press Enter.
If IIS is installed correctly, the IIS Welcome page will appear. This means the IIS web server is running successfully.

Step 9: Open IIS Manager

• We can use IIS Manager to manage the web server.
• Open Server Manager.
• Click Tools.
• Select Internet Information Services (IIS) Manager.
• IIS Manager will open.
• From IIS Manager, you can create and manage websites and web applications.

Do you want to utilize Application Insight to collect telemetry from your corporate application running in an on-premises or cloud environment? Configure your server and begin using Application Insights with a few easy steps.

Follow the below steps now:
Step 1: Open IIS manager by pressing “Windows + R” button, type in “Inetmgr” and click OK.

Step 2: In IIS Manager, click on “Default Web Site” and “Content View” at the bottom to verify the files

Step 3: To configure this server to use Application Insight, we would be installing the “Application Insights Status Monitor” on the server. Click on the link to download and install it.

You can also install it from “Web Platform Installer”. Open the WebPI from Windows search by pressing “windows” button and just type “Web platform Installer”.

Step 4: In the WebPI window, type “Application Insights” in the server option. Select “Application Insights Status Monitor Preview”, click on “Add” and “Install”.

You can also install it from the local path we saved already.
“C:\hfl\HOL-ApplicationInsight\ApplicationInsightsAgent.msi”
After installing, launch the “Application Insights Status Monitor” and “Sign In” with the Azure account provided to you:

Step 5: After signing in, the “Application Insights Status Monitor” will show the list of Application Insight Resources. Select the resource you created in Lab-1 and click the button “Add Application Insights”:

It will take a few seconds to configure the website to use “Application Insights” and will show a prompt in order to restart IIS:

After restarting IIS, the website status will turn to “Enabled” and it will start logging telemetry data to “Application Insights”.

The Application Insights Status Monitor agent places a “ApplicationInsights.config” configuration file under your website directory and adds some configuration settings in Web.config file:

Step 6: Now, browse the following URL in browse tabs to start logging some telemetry data:

http://localhost/default.aspx
http://localhost/pingtest.aspx
 
Now, switch to “Application Insight status monitor” and click on “Open in Microsoft Azure Portal”.

Step 7: Login to the portal and it will open the Application Insights resource in which we are logging the server’s telemetry data:

Summary
This Application Insight will help you to track the performance and usage of the Web Application that has been hosted on Microsoft Azure Service. You can also track adoption and usage with the pages, events, and metrics. We will be working with Application Insights and attaching it towards existing ASP.NET Web applications in future posts.

Basically this problem comes up when we work with Asp.Net Application With IIS Server. I got this error while working with Asp.Net MVC Application. When I run My MVC application suddenly I got this error:

“System.Data.SqlClient.SqlException was unhandled by user code: Login failed for user 'IIS APPPOOL\DefaultAppPool’” and database connection couldn't open.

There are some step for solving this problem.

Go to your Run Window and there you type “Inetmgr” and click oK ( Means Go to IIS Server).

Here you will IIS Server window , from this window you go to “Application pools” and then select “DefaultAppPool” Right click on it and select “Advance Settings” and click on that.

When you will click on Advance settings link it will open Advance setting window there you select “Identity” (In Process Modal) and Change the path from ApplicationPoolIdentity to LocalSystem.

When you click on this Path, three dotted buttons, a window will open from there “Built-in-Account “radio button contain a dropdown box , from this dropdown box you change this path and the click OK.

Let's start by getting a summary of both.

Physical route
This is the path that IIS actually finds the file.

The virtual route
When a file is pointed to from outside the IIS application folder, this is the logical route to access it.
Let's use a virtual directory in the IIS default website to display this image from the hard drive "E:."

Add Virtual Directory

Here, we need to provide an alias for the physical path.

Physical Path - E:\Files
Virtual Path - http://localhost/Files/
File Name - image_60140ec0-ce46-4dbf-a14f-4210eab7f42c.png
Full Path - http://localhost/Files/image_60140ec0-ce46-4dbf-a14f-4210eab7f42c.png

Let’s enable the Directory Browsing.

By default, this is disabled for security reasons.

Here, we can see the files of the folder that is in E Drive. Click on the file name. It will load the file which is in the outer part of IIS application folder. Thanks, hope this will help.

We can parse many kinds of logs with the aid of Log Parser Studio. The primary focus of this course will be on parsing IIS logs. There are two types of Log Parser software: one that just uses the command prompt and the other that supports a graphical user interface.

Installation
Kindly find the link for Log Parser Studio.
Below is the sample query for Log Parser with GUI to get the output from IIS logs for a URL and other data like [MAX, MIN, AVG] – Response Time in mili seconds and hits.
SELECT cs-uri-stem as URL,
MAX(time-taken) As Max,
MIN(time-taken) As Min,
Avg(time-taken) As Average,
Count(1) as Hits
FROM '[LOGFILEPATH]'
GROUP BY URL
ORDER BY Average DESC

Below is the sample query to run in Log Parser with the command prompt version.
Logparser -i: iisw3c “ SELECT cs-uri-stem as URL,
MAX(time-taken) As Max,
MIN(time-taken) As Min,
Avg(time-taken) As Average,
Count(1) as Hits from D:\test.log GROUP By URL ORDER BY Average DESC TO D:\result.csv” –o : csv

Usage details Log parser studio
The landing screen of Log Parser Studio is given below.

As we are interested in parsing IIS logs, so select IIS-Top25 slow URLs.

The query with all the details will be shown to the user.

Now, we need to choose the IIS logs file. Click the Choose log files icon.

The dialog box with the options will be shown, where we have to select the individual log files or the folder. Now, we need to click the icon to execute an active query.

Below is the screenshot of Log Parser Studio with the results. The data for Max, Min, and Average refers to Response Time in mili seconds. We can copy data or export the data, as required.

You may host and manage websites and web applications with the aid of Internet Information Services (IIS), a web server function in Windows Server. It is a solid option for handling and providing web content because it is compatible with several web technologies and offers features for growth, performance, and security.

Internet Information Services (IIS): What is it?
Microsoft's Internet Information Services (IIS) web server software is compatible with Windows Server. Websites, web apps, and other online services can be hosted and managed with its assistance. IIS is adaptable to diverse kinds of web content since it works with a variety of web technologies, including HTML, ASP.NET, and PHP. It provides security, speed, and growth capabilities to help you efficiently set up and manage your web environment. You can efficiently manage applications, provide web pages, and manage internet traffic with IIS.

Internet Information Services (IIS) deployment

Step 1. Open the Server Manager.
Step 2. Click on "Manage".
Step 3. Then select "Add Roles and Features".

Step 4. On the "Before you begin" screen, click "Next."

Step 5. Choose "Role-based or feature-based installation"
Step 6. And then click "Next."

Step 7. Choose the appropriate server from the server pool.
Step 8. And then click "Next".

Step 9. Select the server role "Web Server (IIS)."
Step 10. If a box appears asking to add required features, click "Add Features."
Step 11. And then click "Next."

Step 12. Select the features screen, you can choose extra features if you need them, and then Click "Next".

Step 13. Web Server Role (IIS)" screen, review the information about IIS and click "Next".

Step 14. Select role services, anything you want to install, and Make sure to select important services.

Step 15. Then Click "Next"

When setting up the IIS (Internet Information Services) web server role, there are some important services you need to choose to make sure the web server works properly.

Web Server: Common HTTP Features
    Static Content
    Default Document
    Directory Browsing
    HTTP Errors
    HTTP Redirection (if needed)
Application Development
    ASP.NET (for .NET applications)
    .NET Extensibility
    ISAPI Extensions
    ISAPI Filters
Management Tools
    IIS Management Console
    IIS Management Scripts and Tools
    Management Service (for remote management)
Performance
    Static Content Compression
    Dynamic Content Compression
Security
    Request Filtering
    Windows Authentication (if needed)
    Basic Authentication (if needed)
    URL Authorization

Step 16. Review and click "Install".

Step 17. After installation is finished, click "Close".

Verify the IIS server role Installation

• open a web browser and enter http://localhost.
• confirming that IIS is running.