Browse
Tools
Categories

Preparing IIS for the Reporting Web Site

Reference Number: AA-00513 Views: 6018 Last Updated: 09-13-2016 07:39 AM 0 Rating/ Voters
Preparing IIS for the Reporting Web Site

This document describes how to prepare Microsoft Internet Information Services for installation of the Netaphor SiteAudit™ Reporting Web Site (RWS).

Before you prepare Microsoft Internet Information Services (IIS) for the Reporting Web Site, you should do the following:

Contents

Important Next Steps

After you prepare IIS, you must:

Supported Platforms


The Reporting Web site is an ASPX site that runs on IIS version 7 or later. Your version of IIS depends on your operating system.

Note: Windows XP and 2003 are not supported.

The supported browser for viewing the Reporting Web Site is Internet Explorer version 9 or above. However, it is possible to use other browsers.

Windows 7 and IIS 7

  1. Click Start, type "Windows features" into the search box, and click Turn Windows features on or off.



  2. Make sure that the following check boxes are selected:

    • Internet Information Services > Web Management Tools > IIS 6 Management Compatibility >  IIS Metabase and IIS 6 configuration compatibility
    • World Wide Web Services > Application Development Features > ASP.NET
    • World Wide Web Services > Security > Windows Authentication



  3. Click OK.



  4. If prompted to do so, restart the computer.



  5. If Windows Firewall is enabled, allow HTTP through the firewall:

    • Click Start, type Windows Firewall into the search box, and click Allow a program through Windows Firewall.



    • Click Change Settings.



    • Select the World Wide Web Services (HTTP) check box, and click OK.


Windows Server 2008 Standard and IIS 7

  1. Click Start, type programs and features into the search box, and click Programs and Features.



  2. Click Turn Windows features on or off.



  3. In the left pane, under Server Manager, click Roles, and in the right pane, click Add Roles.



  4. Click Next.



  5. Select the check box for Web Server (IIS).



  6. Click Add Required Features.



  7. Click Role Services.



  8. Make sure that the following check boxes are selected:

    • Web Server > Common HTTP Features > Static Content
    • Web Server > Common HTTP Features > Default Document
    • Web Server > Common HTTP Features > Directory Browsing
    • Web Server > Common HTTP Features > HTTP Errors
    • Web Server > Application Development > ASP.NET
      Note: When you select the check box for ASP.NET, Windows prompts you to add these too:
      • ISAPI Extensions
      • ISAPI Filters
      • .NET Extensibility
      Click Add Required Role Services to do so.
    • Health and Diagnostics > HTTP Logging
    • Health and Diagnostics > Request Monitor
    • Web Server > Security > Windows Authentication
    • Web Server > Security > Request Filtering
    • Web Server > Performance > Static Content Compression
    • Management Tools > IIS Management Console
    • Management Tools > IIS 6  Management Compatibility > IIS 6 Metabase Compatibility



  9. Click Next.

  10. Click Install.



  11. When the installation is complete, click Close.



  12. If Windows Firewall is enabled, allow HTTP through the firewall:

    • Click Start, type Windows Firewall into the search box, and click Windows Firewall with Advanced Security.



    • Click Inbound Rules.



    • Scroll to World Wide Web Services (HTTPS Traffic-In), and if it is disabled, right-click it and click Enable Rule.



  13. Enable the ASP.NET v2.0.50727 service extension: 

    • Click Start, type "IIS" into the search box, and click Internet Information Services (IIS) Manager.



    • Click the Web Service Extensions node.

    • If ASP.NET v2.0.50727 does not exist or is not set to Allowed:



      1. Click Start and click Run.
      2. Run the appropriate command:
        On a 32-bit system: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i

        On a 64-bit system: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis -i

    Securing Reporting Web Site Folders

    By default, all users who have access to the Reporting Web Site can see all folders and reports that exist. It is possible to limit access to RWS folders to specific users. Folders are invisible to users who are denied access to them. This folder security is handled in the web.config file in the root folder of the RWS.

    A section in the web.config is called “location.” Here you can define the path (the folder) that requires special access privileges. A common technique is to create groups, assign users to them, and allow or deny folder access to groups. You can allow or deny folder access to individuals as well.

    In the example below, only users in the RWSInventoryUsers group will see the Inventory folder in the RWS. Again, you can define specific users in the group who can access the folder. An example user is: domain/username

    <location path="MyReports/Inventory">
        <system.web>
            <authorization>
                <allow roles="RWSInventoryUsers" />
            </authorization>
        </system.web>
    </location>

    The RWSInventoryUsers group contains the list of users who are permitted to view reports in the MyReports/Inventory folder.  

    This Microsoft knowledge base article provides additional details: http://support.microsoft.com/kb/316871