Image 1 of 9
In IIS 6 and earlier, most web site properties were housed on a single management pane with multiple tabs. This is no longer the case in IIS 7.0 with various configuration parameters now scattered around various administrative modules and locations. The most commonly configured settings are available on the Basic Settings page available by selecting a site from the Connections pane and then, from the Actions pane, clicking Basic Settings. The Basic Settings page is shown here.
.NET Framework version
If you want to change the path that houses the content for the selected site, click the button to the right of the Physical Path field. You can also change the application pool used by this web site by clicking the Select button at the top right of the window. You’ll note that the Select Application Pool dialog box shows you the version of the .Net Framework used by the site as well as the pipeline mode. There are two pipeline modes available–Integrated and Classic (ISAPI). In Integrated mode, IIS uses a new integrated IIS/ASP.NET API to process requests in the application pool. In Classic mode, separate IIS and ASP.NET request-processing pipelines are used to process application pool requests.
Basic Application Pools
Separating applications into multiple application pools not only can improve performance but also improves server and site reliability. The first step is to create an application pool after which you can modify its settings. Open the IIS console and, from the Connections pane, choose the Application Pools option. From the Work pane, choose Add Application Pool to open the Add Application Pool dialog box.nEnter a name for the application pool to uniquely identify it. Choose the version, if any, of the .Net Framework that is to be used by this pool and choose your pipeline mode. Once a pool is creation, you can change its settings whenever necessary. From the Connections pane, choose Application Pools. Then, in the Work pane, choose the application pool you’d like to configure and, from the Actions pane, choose Basic Settings. With the exception of the dialog box title, the Basic Settings dialog box and the Add Application Pool dialog boxes look identical.
Edit Application Pool Recycling Settings
The Edit Application Pool Recycling Settings dialog box lets you configure how IIS handles worker process recycling for the application pool.
The second screen of the recycling settings options gives you a place to decide which recycling events should be logged.
Web site compression
To enable compression on a particular site, select the site and then, from the Work pane, select the Compression management tool. Choose whether you want to compress static content, dynamic content or both.
Global compression options
If you open the Compression tool when you have the server selected, there are additional options, including choosing the folder that is to contain the compressed files cache, which defaults to %SystemDrive%\inetpub\temp\IIS Temporary Compressed Files. On this page, also indicate the size (in bytes) at which files should be compressed. The default value is 256 bytes.
IIS 7.0 supports bandwidth throttling and connection limiting for individual Web sites, and you can also set global properties to limit bandwidth usage and connections. Limiting the number of connections and/or bandwidth used by the site helps you limit the site’s impact on the server, and limiting the server helps you manage the server’s impact on your network and available bandwidth. To limit these at the individual site level, open the IIS console, choose the site you want to configure, and, from the Actions pane, click Limits. Click the Performance tab and use the Bandwidth Throttling group of controls to set the maximum bandwidth in kbps for all sites on the server as a whole. You can choose to either allow an unlimited number of connections or limit the server to a total number of connections.
You can configure IIS to backup web site data.