Article ID: 240941 - View products that this article applies to.
This article was previously published under Q240941
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 7.0 running on Microsoft Windows Server 2008. IIS 7.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
http://www.microsoft.com/technet/security/prodtech/IIS.mspxFor more information about IIS 7.0, visit the following Microsoft Web site:
The metabase is a structure for storing Internet Information Server (IIS) configuration settings. It performs some of the same functions as the Windows system registry but is specific to Internet Information Server version 4.0. New keys and values have been added for finer and more flexible control of IIS.
When a system is upgraded from IIS 3.0 or earlier to IIS 4.0, the configuration parameters that were previously set in the registry are migrated to the metabase. When IIS starts, it loads the metabase into memory, where it is available until IIS shuts down. The metabase is stored in a special format file by default named Metabase.bin in the Inetsrv folder in which IIS is normally installed.
Like the registry, the metabase is organized in a hierarchical structure that mirrors the structure of your IIS installation. It is made up of nodes, keys, and subkeys. The main organization is by node, with each node in the metabase structure representing a site or directory. Beneath the nodes are keys that may contain one or more IIS configuration values called metabase properties. The metabase keys correspond to individual configuration elements of IIS; each key contains properties that affect the configuration of its associated directory or site.
The structure of the metabase facilitates different settings of a property for different nodes. For example, the MaxBandwidth property setting can be different for each virtual site. However, metabase properties are inherited. This means that those parameters that are configured at higher levels, such as the Web site level, will affect the lower levels. But if you set a specific property for an individual site, virtual site, or virtual directory, changes made at a higher level will not automatically override the lower-level individual setting. Note that when the metabase is searched for configuration information, it is enumerated from the bottom, or subkey, to top, or node.
Many of the metabase parameters can be configured from the Internet Service Manager snap-in for the Microsoft Management Console (MMC). Additional tools are also available for further tuning of the metabase.
CautionConfiguring properties in the metabase incorrectly can cause problems, including the failure of a Web site or FTP site. If you make mistakes, your Web site or FTP site's configuration could be damaged. You should edit metabase properties only for settings that you cannot adjust in the user interface. Be very careful whenever you edit the metabase directly.
There are two main ways to edit the metabase:
For more information on the structure of the metabase, please consult the IIS 4.0 product documentation.
(http://support.microsoft.com/kb/234429/EN-US/ )How to Manually Restore the Metabase When No Proper Backup Exists or the MMC Won't Start