Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

10/18/2014 Deploying a Classic ASP Server (IIS 7)

Deploying a Classic ASP Server (IIS 7)


18 out of 45 rated this helpful

Updated: May 24, 2010

Applies To: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista

A Classic ASP Web server is the common configuration used for serving server-side scripted ASP pages. The Classic ASP server configuration adds IIS modules for
ASP, Request Filtering, and ISAPI extensions to the default IIS 7 Web server installation. This topic describes how to install the IIS modules that are required to
deploy a Classic ASP Web server.

Note

You must be logged on as a member of the Administrators group to perform this task.

The following table describes the IIS modules that are added to the default installation for a Classic ASP Web server.

IIS module name Description

ASP Enables your Web server to host Classic ASP applications.

Request Filtering Performs UrlScan tasks such as configuring allowed verbs and file name extensions, setting limits, and scanning for bad character sequences.

ISAPI Extensions Supports dynamic Web content development using ISAPI extensions.

Note

You can also run ASP.NET on the same server, but this scenario specifically covers only the modules required for Classic ASP. For more information about the
ASP.NET scenario, see Deploying an ASP.NET Server (IIS 7).

To deploy a Classic ASP server


You can use the Web Platform Installer (Web PI) to easily install IIS, and applications that run on IIS. Because the Web PI installs the latest versions of available
Web Platform offerings, with just a few simple clicks you can download and install any new tools or updates. To learn more about the Web PI, see Learn more and
install the Web PI.

You can also perform this procedure by using the Windows user interface (UI) or from a command line.

To use the UI on Windows Server 2008 or Server 2008 R2


1. Click Start, point to Administrative Tools, and then click Server Manager.

2. In Roles Summary, click Add Roles.

3. Use the Add Roles Wizard to add the Web Server (IIS) role.

For detailed instructions about how to install a default IIS 7 Web server, see Deploying a Static Content Server (IIS 7).

4. On the Select Role Services page, note the preselected role services that are installed by default, and then select the following additional role services:

ASP

Request Filtering

ISAPI Extensions

5. On the Summary of Features to Install page, confirm your selections, and then click Install.

6. On the Installation Results page, confirm that your installation of the Web Server (IIS) role and required role services completed successfully, and then
click Close.

http://technet.microsoft.com/en-us/library/cc753918(v=ws.10).aspx 1/3
10/18/2014 Deploying a Classic ASP Server (IIS 7)
7. To verify that IIS installed successfully, type the following into a Web browser:

http://localhost

You should see the default IIS 7 Welcome page.

To use the UI on Windows Vista or Windows 7


1. Click Start, and then click Control Panel.

2. In Control Panel, click Programs, and then click Turn Windows features on or off.

3. In the Windows Features dialog box, click Internet Information Services to install the default features, and then select the following additional
features:

ASP

Request Filtering

ISAPI Extensions

4. Click OK to close the Windows Features dialog box.

5. To verify that IIS installed successfully, type the following into a Web browser:

http://localhost

You should see the default IIS Welcome page.

To use the command line


Type the following command into a script:

Start /w pkgmgr /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

Was this page helpful? Yes No

Community Additions

Using the command line:


Windows Package Manager responds with "Operation failed with 0x80070057. The parameter is incorrect."

Thomas Lee
7/12/2010

Solution : Using command Line


Please remove the space after semicolumn (;).

OR

You can copy below command :

Start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-

http://technet.microsoft.com/en-us/library/cc753918(v=ws.10).aspx 2/3
10/18/2014 Deploying a Classic ASP Server (IIS 7)
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

[[Thanks for identifying the error in this topic. The topic has been corrected, and the updated version will be published by
05/27]]

rdubois (MSFT)
5/20/2010

© 2014 Microsoft

http://technet.microsoft.com/en-us/library/cc753918(v=ws.10).aspx 3/3

You might also like