h1

Creating an Unsecured Website in IIS 7.0

May 19, 2010

Users access unsecured Websites by using HTTP. You can create a Website that uses HTTP by completing the following steps:

1. If you’re creating the Website on a new server, ensure that the World Wide Web Publishing Service has been installed and started on the server.

2. If you want the Website to use a new IP address, you must configure the IP address on the server before installing the site.

3. In IIS Manager, double-click the icon for the computer you want to work with, and then right-click Sites. On the shortcut menu, choose Add Website. This displays the Add Website dialog box.

4. In the Website Name textbox, type a descriptive name for the Website, such as Corporate Sales. IIS Manager uses the name you provide to set the name of the new application pool to associate with the site. If you want to use an existing application pool instead of a new application pool, click Select. In the Select Application Pool dialog box, in the Application Pool drop-down list, select the application pool to associate with the site, and then click OK. Note that the .Net Framework version and pipeline mode of a selected application pool are listed on the Properties panel.

5. The Physical Path textbox specifies the physical directory that contains the site’s content. You can configure the physical path by using a local directory path or a shared folder. Keep the following in mind:

* To specify a local directory path for the site, click the Select button to the right of the Physical Path textbox. In the Browse For Folder dialog box, use the choices provided to select a directory for the Website. This folder must be created before you can select it. If necessary, click Make New Folder to create the directory.

* To specify a shared folder for the site, type the desired UNC path in the appropriate textbox, such as \\CentralStorage83\inetpub\sales_site. If you need to use alternate credentials to connect to the remote server specified in the UNC path, click Connect As. In the Connect As dialog box, choose Specific User, and then click Set. In the Set Credentials dialog box, type the name of the user account to use for authentication, type and confirm the account password, and then click OK.

Note: If you don’t specify a username and password, the user’s Windows credentials are authenticated before allowing access. For an anonymous access site, IIS authenticates the credentials  for the IUSR_ServerName account, so this account should have access to the shared folder. Otherwise, the network connection to the folder will fail.

6. The Binding settings identify the Website. To create an unsecured Website, select HTTP as the type and then use the IP Address drop-down list to select an available IP address. Choose (All Assigned) to allow HTTP to respond on all unassigned IP addresses that are configured on the server. Multiple Websites can use the same IP addresses so long as the sites are configured to use different port numbers or host headers.

7. The TCP port for an unsecured Website is assigned automatically as port 80. If necessary, type a new port number in the Port field. Multiple sites can use the same port as long as the sites are configured to use different IP addresses or host headers.

8. If you plan to use host headers for the site, type the host header name in the field provided. On a private network, the host header can be a computer name, such as EngIntranet. On a public network, the host header must be a DNS name, such as services.microsoft.com. The host header name must be unique within IIS.

9. By default, IIS starts the Website immediately so long as the bindings you’ve supplied are unique. If you don’t want to start the site immediately, clear the Start Website Immediately checkbox. In most cases, you’ll want to finish setting the site’s properties before you start the site and make it accessible to users.

By using the IIS Command Line Administration Tool, you can run the Add Site command to add an HTTP site to a server. I’ve added the syntax and usage below. Technically, bindings and physicalPath are optional, but a site won’t work until these parameters are provided. Adding the physical path is what allows IIS to create the root virtual directory and root application for the site.

Adding an HTTP Site Syntax and Usage

Syntax:

appcmd add site /name:Name /id:ID /bindings:http://UrlAndPort
/physicalpath:Path

Usage:

appcmd add site /name: ‘Sales Site’ /id:5 /bindings:http://sales.adatum.com:80

appcmd add site /name ‘Sales Site’ /id:5 /bindings:http://*:8080

appcmd add site /name ‘Sales Site’ /id:5 /bindings:http:/*:8080
/physicalPath: ‘c:\inetpub\mynewsite’

Advertisements
%d bloggers like this: