Logo - tutorial.programming4.us
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
 
 
Windows Server

Planning the Installation : Installation Scenarios for IIS 7.0 (part 1)

12/23/2011 6:27:07 PM

Installation Scenarios for IIS 7.0

One concept introduced in Windows Server 2008 is workload-specific setups. Some common workload scenarios that can be used in Windows Server 2008 are

  • Static Content Web Server (Default installation)

  • ASP.NET

  • Classic ASP

  • FastCGI-based applications

  • IIS Managed Modules and .NET Extensibility

  • IIS Full Install

  • Server Core Web Edition

Static Content Web Server (Default Installation)

Web Server with the Static Content role service is the default installation and one of the most commonly used installation workload types. Other workloads and product installations use it. The preselected setup defaults of IIS 7.0 provide all the IIS modules required to support this configuration. This includes the ability to serve static HTML files, documents, and images. Additionally, it provides support for default documents, directory browsing, logging, and anonymous authentication. The IIS Manager Console is also installed.

Table 1 lists all the components that are selected by default when you install IIS 7.0. The table includes the appropriate update names. Update names are the names used to perform Package Manager installations.

Table 1. Default Server Install Components
Server ManagerUpdate Name
Static ContentIIS-StaticContent
Default DocumentIIS-DefaultDocument
Directory BrowsingIIS-DirectoryBrowsing
HTTP ErrorsIIS-HttpErrors
HTTP LoggingIIS-HttpLogging
Logging ToolsIIS-LoggingLibraries
Request MonitorIIS-RequestMonitor
Request FilteringIIS-RequestFiltering
Static Content CompressionIIS-HttpCompressionStatic
IIS Management ConsoleIIS-ManagementConsole

To install IIS features for a Static Content Web server via Package Manager, use the following command from a command prompt. (The command has been formatted to fit on the printed page.)

start /w pkgmgr.exe /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;
IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;
IIS-HttpErrors;IIS-HealthAndDiagnostics;IIS-HttpLogging;
IIS-LoggingLibraries;IIS-RequestMonitor;IIS-Security;
IIS-RequestFiltering;IIS-HttpCompressionStatic;
IIS-WebServerManagementTools;IIS-ManagementConsole;
WAS-WindowsActivationService;WAS-ProcessModel;
WAS-NetFxEnvironment;WAS-ConfigurationAPI


To install IIS features for Static Content Web Server via ServerManagerCMD, use the following command from a command prompt:

ServerManagerCMD.exe –install Web-Server

ASP.NET

The Microsoft ASP.NET Web server is probably the most commonly used server workload type. ASP.NET has proven to be very popular among developers. IIS 7.0 and ASP.NET are designed to work closely together, and ASP.NET is a first-class citizen in IIS 7.0. Developers can deploy managed code at the same level as native modules. The integrated pipeline option provides this functionality. The Static Content Web Server modules, along with specific ASP.NET options, make up the ASP.NET workload server.

Table 2 lists all components that are installed when you configure your server to use the ASP.NET workload server. The table includes the appropriate update names.

Table 2. ASP.NET Workload Server Options
Server ManagerUpdate Name
Static ContentIIS-StaticContent
Default DocumentIIS-DefaultDocument
Directory BrowsingIIS-DirectoryBrowsing
HTTP ErrorsIIS-HttpErrors
HTTP LoggingIIS-HttpLogging
Logging ToolsIIS-LoggingLibraries
Request MonitorIIS-RequestMonitor
Request FilteringIIS-RequestFiltering
Static Content CompressionIIS-HttpCompressionStatic
IIS Management ConsoleIIS-ManagementConsole
ASP.NETIIS-ASPNET
.NET ExtensibilityIIS-NetFxExtensibility
ISAPIIIS-ISAPIFilter
ISAPI ExtensionsIIS-ISAPIExtensions

To install IIS features for the ASP.NET server workload via Package Manager, use the following command from a command prompt:

start /w pkgmgr.exe /iu:IIS-WebServerRole;IIS-WebServer;
IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;
IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-ApplicationDevelopment;
IIS-ASPNET;IIS-NetFxExtensibility;IIS-ISAPIExtensions;
IIS-ISAPIFilter;IIS-HealthAndDiagnostics;IIS-HttpLogging;
IIS-LoggingLibraries;IIS-RequestMonitor;IIS-Security;
IIS-RequestFiltering;IIS-HttpCompressionStatic;
IIS-WebServerManagementTools;IIS-ManagementConsole;
WAS-WindowsActivationService;WAS-ProcessModel;
WAS-NetFxEnvironment;WAS-ConfigurationAPI

To install IIS features for the ASP.NET server workload via ServerManagerCMD, use the following command from a command prompt:

ServerManagerCmd.exe -install Web-Server
ServerManagerCmd.exe -install Web-ASP-NET
ServerManagerCmd.exe -install Web-NET-Ext
ServerManagerCmd.exe -install Web-Filtering
ServerManagerCmd.exe -install Web-ISAPI-Filter
ServerManagerCmd.exe -install Web-ISAPI-Ext

Classic ASP

Before Microsoft released ASP.NET, classic ASP was used as the main programming language on IIS. Many Web sites still use classic ASP today, and IIS 7.0 supports classic ASP. Your classic ASP applications will easily port to IIS 7.0. You can take advantage of the new benefits such as diagnostics, logging, and troubleshooting, while at the same time maintaining your existing applications, enabling you to have the best of both worlds. You will be able to keep your classic ASP around and have the benefits of IIS 7.0. The static file modules, along with specific classic ASP options, make up the ASP workload server.

Table 3 lists all components that are installed when you configure your server to use the classic ASP workload server. The table includes the appropriate update names.

Table 3. Classic ASP Workload Server Options
Server ManagerUpdate Name
Static ContentIIS-StaticContent
Default DocumentIIS-DefaultDocument
Directory BrowsingIIS-DirectoryBrowsing
HTTP ErrorsIIS-HttpErrors
HTTP LoggingIIS-HttpLogging
Logging ToolsIIS-LoggingLibraries
Request MonitorIIS-RequestMonitor
Request FilteringIIS-RequestFiltering
Static Content CompressionIIS-HttpCompressionStatic
IIS Management ConsoleIIS-ManagementConsole
ASPIIS-ASP
ISAPI ExtensionsIIS-ISAPI-Extensions

To install IIS features for the classic ASP server workload via Package Manager, use the following command from a command prompt:

start /w pkgmgr.exe /iu:IIS-WebServerRole;IIS-WebServer;
IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;
IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-ApplicationDevelopment;
IIS-ASP;IIS-ISAPIExtensions;IIS-HealthAndDiagnostics;
IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;
IIS-Security;IIS-RequestFiltering;IIS-HttpCompressionStatic;
IIS-WebServerManagementTools;IIS-ManagementConsole;
WAS-WindowsActivationService;WAS-ProcessModel;
WAS-NetFxEnvironment;WAS-ConfigurationAPI

To install IIS features for the classic ASP Web server workload via ServerManagerCMD, use the following command from a command prompt:

ServerManagerCmd.exe -install Web-Server
ServerManagerCmd.exe -install Web-ASP
ServerManagerCmd.exe -install Web-Filtering
ServerManagerCmd.exe -install Web-ISAPI-Ext

FastCGI Server Workload

FastCGI is an alternative to CGI (Common Gateway Interface). This is a language-independent extension to CGI that provides high performance without being tied to a specific server platform.

Note

For more information on the FastCGI module for IIS, please read Bill Staples’s blog at http://blogs.iis.net/bills/archive/2006/10/31/PHP-on-IIS.aspx. The blog discusses how to enhance your PHP applications with IIS 7.0 and FastCGI modules.


One of the design goals of Windows Server 2008 is to provide a common Web server platform for all types of applications. This includes applications based on Microsoft technology such as ASP.NET and classic ASP, as well as non-Microsoft technology such as PHP.

Table 4 lists all components that are installed when you configure your server to use the FastCGI workload server. The table includes the appropriate update names.

Table 4. FastCGI Workload Server Options
Server ManagerUpdate Name
Static ContentIIS-StaticContent
Default DocumentIIS-DefaultDocument
Directory BrowsingIIS-DirectoryBrowsing
HTTP ErrorsIIS-HttpErrors
HTTP LoggingIIS-HttpLogging
Logging ToolsIIS-LoggingLibraries
Request MonitorIIS-RequestMonitor
Request FilteringIIS-RequestFiltering
Static Content CompressionIIS-HttpCompressionStatic
IIS Management ConsoleIIS-ManagementConsole
CGIIIS-CGI

To install IIS features for the FastCGI server workload via Package Manager, use the following command from a command prompt:

start /w pkgmgr.exe /iu:IIS-WebServerRole;IIS-WebServer;
IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;
IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-ApplicationDevelopment;
IIS-CGI;IIS-HealthAndDiagnostics;IIS-HttpLogging;
IIS-LoggingLibraries;IIS-RequestMonitor;IIS-Security;
IIS-RequestFiltering;IIS-HttpCompressionStatic;
IIS-WebServerManagementTools;IIS-ManagementConsole;
WAS-WindowsActivationService;WAS-ProcessModel;
WAS-NetFxEnvironment;WAS-ConfigurationAPI

To install IIS features for the FastCGI server workload via ServerManagerCMD, use the following command line:

ServerManagerCmd.exe -install Web-Server
ServerManagerCmd.exe -install Web-CGI
 
Other -----------------
- Sharepoint 2010 : Configuring Crawls (part 3) - Using Server Name Mappings & Controlling Host Distribution
- Sharepoint 2010 : Configuring Crawls (part 2) - Creating and Managing Crawl Rules
- Sharepoint 2010 : Configuring Crawls (part 1) - Creating and Managing Content Sources
- Windows Server 2003 : Creating and Enforcing Security Policies (part 3) - Microsoft Baseline Security Analyzer
- Windows Server 2003 : Creating and Enforcing Security Policies (part 2) - Security Configuration and Analysis
- Windows Server 2003 : Creating and Enforcing Security Policies (part 1) - Using Security Policy Templates
- Microsoft Dynamic CRM 4.0 : MapPoint Integration (part 2) - MapPoint Web Services
- Microsoft Dynamic CRM 4.0 : MapPoint Integration (part 1) - MapPoint 2009
- Microsoft Dynamic CRM 4.0 : Microsoft Live Search Maps
- Configuring Email Settings in Windows Small Business Server 2011 (part 2) - Setting Mailbox Quotas & Moving Exchange Server Data
 
 
Top 10
- Microsoft Lync Server 2013 : Windows Client - Navigating in the Client - Useful Lync Client Shortcuts
- Microsoft Lync Server 2013 : Windows Client - Navigating in the Client - Managing Contacts, Managing Groups, Status View
- Microsoft Lync Server 2013 : Windows Client - Navigating in the Client - Configuring Basic Options
- Microsoft Lync Server 2013 : Windows Client - Installing the Client
- Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 4) - Setting storage restrictions on mailbox and archives
- Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 3) - Permitting others to access a mailbox
- Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 2) - Setting message send and receive restrictions on individual mailboxes
- Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 1) - Setting message size restrictions on delivery to and from individual mailboxes
- Microsoft Exchange Server 2013: Moving mailboxes (part 3) - Performing on-premises mailbox moves
- Microsoft Exchange Server 2013: Moving mailboxes (part 2) - Performing on-premises mailbox moves and migrations
 
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone