Configure the IIS to host Sitefinity projects

If you are using Microsoft Internet Information Server (IIS) to host your Sitefinity CMS projects, you must configure the server in the following way, depending on your operating system:

Automatic configuration

1. Download the Windows Server 2008 PowerShell script and save it on your computer.
2. In the context menu of the downloaded file, click Run with PowerShell.
3. Restart the server.

NOTE: When running the PowerShell script, your system may become slower. Keep in mind that the script modifies Windows features that can affect other parts of the system.

Manual configuration 

1. Open the Server Manager by opening your Start Menu and clicking Administrative Tools » Server Manager.
2. Select and expand Roles.
3. If you do not see Web Server (IIS) role, you must add it using the Add Roles button.
4. Click Web Server (IIS) and in the right pane, expand Role Services.
5. Make sure you have installed the following services:
   • Common HTTP Features » Static Content.
   • Application Development » ASP.NET, .NET Extensibility, ISAPI Extensions, and ISAPI Filters.
   • Management Tools » IIS Management Console, IIS Management Scripts and Tools, and Management Service.
6. In the navigation tree on the left, click Features.
7. Make sure you have the following features installed:
   • Desktop Experience.
   • .NET Framework 3.5.1 Features » WCF Activation » HTTP Activation.
8. After you have Run projects on IIS, expand Web Server (IIS) node and click Internet Information Services (IIS) Manager.
   In the right pane, the Internet Information Services (IIS) Manager appears.
9. In the navigation of the IIS manager, expand your server node.
10. Expand Sites node and click your website.
11. In section IIS on the right, double-click Authentication.
12. Perform one of the following:
    • If you are using Forms authentication, make sure Anonymous Authentication and Forms Authentication are enabled and all other authentications are disabled.
    • If you are using Claims-based authentication, make sure only Anonymous Authentication is enabled and all other authentications are disabled.
13. Click your website again and in IIS section, double-click Handler Mappings.
14. Make sure you have enabled handler mappings for *.svc and *.xamlx with executable path set to one of the following:
    1. For 64-bit OS: %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
    2. For 32-bit OS: %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
15. Close the Server Manager.

Automatic configuration

1. Download the Windows Server 2008 R2 PowerShell script and save it on your computer.
2. In the context menu of the downloaded file, click Run with PowerShell.
3. Restart the server.

NOTE: When running the PowerShell script, your system may become slower. Keep in mind that the script modifies Windows features that can affect other parts of the system.

Manual configuration 

1. Open your Control Panel and click Programs and Features » Turn Windows features on or off.
2. Turn on Internet Information Services.
3. Under Internet Information Services, turn on the following features:
   • Web Management Tools » IIS 6 Management Compatibility » IIS Metabase and IIS 6 configuration compatibility.
   • Web Management Tools » IIS Management Console, IIS Management Scripts and Tools, and Management Service.
4. Under World Wide Web Services, turn on the following:
   • All features under Application Development features, except Server-Side Includes.
   • Common HTTP Features » Default Document, Directory Browsing, HTTP errors, Http Redirection, Static Content.
   • Security » Basic Authentication, Request Filtering, Windows Authentication.
5. Under Microsoft .NET Framework 3.5.1 » Windows Communication Foundation HTTP Activation.
   
6. After you have Run projects on IIS, open the Internet Information Services (IIS) Manager.
7. Expand your server node.
8. Expand Sites node and click your website.
9. In section IIS on the right, double-click Authentication.
10. Perform one of the following:
11. If you are using Forms authentication, make sure Anonymous Authentication and Forms Authentication are enabled and all other authentications are disabled.
12. If you are using Claims-based authentication, make sure only Anonymous Authentication is enabled and all other authentications are disabled.
13. Click your website again and in IIS section, double-click Handler Mappings.
14. Make sure you have enabled handler mappings for *.svc and *.xamlx with executable path set to one of the following:
15. For 64-bit OS: %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
16. For 32-bit OS: %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
17. Close the Internet Information Services (IIS) Manager.

Automatic configuration

1. Download the Windows Server 2012 PowerShell script and save it on your computer.
2. In the context menu of the downloaded file, click Run with PowerShell.

NOTE: When running the PowerShell script, your system may become slower. Keep in mind that the script modifies Windows features that can affect other parts of the system.

Manual configuration 

1.  Install ASP.NET 4.5.
2. Open your Control Panel and click Programs and Features » Turn Windows features on or off.
3. Turn on Internet Information Services.
4. Under Internet Information Services, turn on the following features:
   • Web Management Tools » IIS 6 Management Compatibility » IIS Metabase and IIS 6 configuration compatibility.
   • Web Management Tools » IIS Management Console, IIS Management Scripts and Tools, and Management Service.
5. Under World Wide Web Services, turn on the following:
   • All features under Application Development features, except Server-Side Includes.
   • Common HTTP Features » Default Document, Directory Browsing, HTTP errors, Http Redirection, Static Content.
   • Security » Basic Authentication, Request Filtering, Windows Authentication.
6. Turn on Windows Identity Foundation 3.5.
   
7. After you have Run projects on IIS, open the Internet Information Services (IIS) Manager.
8. Expand your server node.
9. Expand Sites node and click your website.
10. In section IIS on the right, double-click Authentication.
11. Perform one of the following:
    • If you are using Forms authentication, make sure Anonymous Authentication and Forms Authentication are enabled and all other authentications are disabled.
    • If you are using Claims-based authentication, make sure only Anonymous Authentication is enabled and all other authentications are disabled.
12. Click your website again and in IIS section, double-click Handler Mappings.
13. In the right pane click Add Managed Handler… and register the following managed handlers:
    • *.svc
      1. In Request path, enter *.svc
      2. In Type input field, enter System.ServiceModel.Activation.ServiceHttpHandlerFactory, System.ServiceModel.Activation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, select All verbs.
      6. On Access tab, select Script.
    • *.xamlx
      1. In Request path, enter *.xamlx
      2. In Type input field, enter System.Xaml.Hosting.XamlHttpHandlerFactory, System.Xaml.Hosting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, enter GET,HEAD,POST,DEBUG.
      6. On Access tab, select Script.
14. In the right pane click Add Script Map… and register the following script maps:
    
    • *.svc
      1. In Request path, enter *.svc
      2. In Executable input field, enter C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, select All verbs.
      6. On Access tab, select Script.
    • *.svc
      1. In Request path, enter *.svc
      2. In Executable input field, enter C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, select All verbs.
      6. On Access tab, select Script.
    • *.xamlx
      1. In Request path, enter *.xamlx
      2. In Executable input field, enter C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, enter GET,HEAD,POST,DEBUG.
      6. On Access tab, select Script.
    • *.xamlx
      1. In Request path, enter *.xamlx
      2. In Executable input field, enter C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, enter GET,HEAD,POST,DEBUG.
      6. On Access tab, select Script.
15. Close the Internet Information Services (IIS) Manager.

Automatic configuration 

1. Download the Windows Server 2012 R2 PowerShell script and save it on your computer.
2. In the context menu of the downloaded file, click Run with PowerShell.

NOTE: When running the PowerShell script, your system may become slower. Keep in mind that the script modifies Windows features that can affect other parts of the system.

Manual configuration 

1. Install ASP.NET 4.5. 
2. Open your Control Panel and click Programs and Features » Turn Windows features on or off.
3. Turn on Internet Information Services.
4. Under Internet Information Services, turn on the following features:
   • Web Management Tools » IIS 6 Management Compatibility » IIS Metabase and IIS 6 configuration compatibility.
   • Web Management Tools » IIS Management Console, IIS Management Scripts and Tools, and Management Service.
5. Under World Wide Web Services, turn on the following:
   • Application Development features » .NET Extensibility 3.5, .NET Extensibility 4.5, Application initialization, ASP, ASP.NET 3.5, ASP.NET 4.5, CGI, ISAPI Extensions, ISAPI Filters, Server Side Includes.
   • Common HTTP Features » Default Document, Directory Browsing, HTTP errors, Http Redirection, Static Content.
   • Security » Basic Authentication, Request Filtering, Windows Authentication.
6. Turn on Windows Identity Foundation 3.5.
   
7. After you have Run projects on IIS, open the Internet Information Services (IIS) Manager.
8. Expand your server node.
9. Expand Sites node and click your website.
10. In section IIS on the right, double-click Authentication.
11. Perform one of the following:
    • If you are using Forms authentication, make sure Anonymous Authentication and Forms Authentication are enabled and all other authentications are disabled.
    • If you are using Claims-based authentication, make sure only Anonymous Authentication is enabled and all other authentications are disabled.
12. Click your website again and in IIS section, double-click Handler Mappings.
13. In the right pane click Add Managed Handler… and register the following managed handlers:
    • *.svc
      1. In Request path, enter *.svc
      2. In Type input field, enter System.ServiceModel.Activation.ServiceHttpHandlerFactory, System.ServiceModel.Activation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, select All verbs.
      6. On Access tab, select Script.
    • *.xamlx
      1. In Request path, enter *.xamlx
      2. In Type input field, enter System.Xaml.Hosting.XamlHttpHandlerFactory, System.Xaml.Hosting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, enter GET,HEAD,POST,DEBUG.
      6. On Access tab, select Script.
14. In the right pane click Add Script Map… and register the following script maps:
    
    • *.svc
      1. In Request path, enter *.svc
      2. In Executable input field, enter C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, select All verbs.
      6. On Access tab, select Script.
    • *.svc
      1. In Request path, enter *.svc
      2. In Executable input field, enter C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, select All verbs.
      6. On Access tab, select Script.
    • *.xamlx
      1. In Request path, enter *.xamlx
      2. In Executable input field, enter C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, enter GET,HEAD,POST,DEBUG.
      6. On Access tab, select Script.
    • *.xamlx
      1. In Request path, enter *.xamlx
      2. In Executable input field, enter C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
      3. Click Request Restrictions.
      4. On Mappings tab, deselect Invoke Handler if request is mapped to.
      5. On Verbs tab, enter GET,HEAD,POST,DEBUG.
      6. On Access tab, select Script.
15. Close the Internet Information Services (IIS) Manager.

NOTE: By default, all HTTP verbs are enabled on the IIS. We do not recommended restricting HTTP verbs on IIS level. If absolutely necessary, however, you can restrict verbs for a specific service instead.

You must provide the identity of the application pool, in which your website in running under IIS, with Read & execute permissions for the entire folder structure of your website.

Make sure the identity has Modify, Read & execute, Read, and Write permissions set for the App_Data folder and its subfolders.

You must set the following MIME types in the server configuration:

CAUTION: If you do not set the MIME types, error message are displayed to users browsing the backend.

For more information on how to set the MIME types, see Configuring IIS for Silverlight Applications.