Administering an ISP Installation

Components for Administration (Sample Setup)

The following registry configuration is necessary to make the next example work. All of the host menu documents have been placed on the Web site http://reskit1.microsoft.com. Registry values have been added to

HKEY_LOCAL_MACHINE
\System
\CurrentControlSet
\Services
\W3SVC
\Parameters

Caution Do not use a registry editor to edit the registry directly unless you have no alternative. The registry editors bypass the standard safeguards provided by administrative tools. These safeguards prevent you from entering conflicting settings or settings that are likely to degrade performance or damage your system. Editing the registry directly can have serious, unexpected consequences that can prevent the system from starting and require that you reinstall Windows 2000. To configure or customize Windows 2000, use the programs in Control Panel or Microsoft Management Console (MMC) whenever possible.

The registry values include:

DLCMenuString = /HostMenu (Data Type is REG_SZ): This parameter specifies the prefix of URLs that apply to the host menu. The server will check against this string on all requests from older browsers (in other words, requests without a host header).
DLCHostNameString = reskit1.microsoft.com: This parameter supplies the host name of the instance that contains the menu documents.
DLCMungeMenuDocumentString = /scripts/munge.asp: This host menu document will be sent to older browsers that don’t support cookies.
DLCCookieMenuDocumentString = /scripts/cookie.asp: This host menu document will be sent to older browsers that do support cookies.
DLCCookieNameString = PseudoHost: This parameter specifies the name of the special cookie that will act as a pseudo host header. This can be used with clients that support cookies.
DLCSupport = 1 (Data Type is REG_DWORD): This parameter enables support for older browsers.

The host menu documents include three files (Munge.asp, Cookie.asp, and Redirect.asp).

See the following: