[This is preliminary documentation and subject to change]

# Downlevel Site Administration

You can use the IIS snap-in that shipped with IIS version 4.0 to remotely administer IIS 5.1 on an intranet. To remotely administer IIS over the Internet or through a proxy server, you should use a Web-based server management appliance. In addition, you can designate one Web site that can be administered programatically by applications that use the IIS 3.0 administration interfaces.

Note In IIS 3.0, any virtual directory that did not have a specific IP address associated with it was accessible from all Web sites hosted on that computer. This behavior changed in IIS 4.0, 5.0, and 5.1; to make a virtual directory accessible from multiple Web sites that use multiple IP addresses, you must now also add that same virtual directory to each of those sites.

###### To specify a site available for IIS 3.0 administration

1. In the Internet Information Services snap-in, select the Computer icon, and open its property sheets.
2. Select WWW Service or FTP Service, and click the Edit button.
3. Click the Service tab.
4. Under IIS 3.0 Administration, select the site, and click OK.

Important The column entitled Verbs in the App Mappings property sheet lists the HTTP verbs that will be run by an application. In IIS 4.0, this column, entitled Exclusions, listed the HTTP verbs that are not run by an application. If you perform remote administration tasks between computers running IIS 4.0 and IIS 5.0 or 5.1, this column is incorrectly labeled.

For more information on application mappings, see Setting Application Mappings.

(The following words are used by Search; they are not intended to be displayed on the page.) W3SVC

© 1997-2001 Microsoft Corporation. All rights reserved.