Most configuration settings for IIS reside in a storage facility, similar to the Windows registry, called the metabase. You should become familiar with how the metabase operates, how the information contained within the metabase is organized, and how you can access that information.
The metabase is organized in a hierarchical structure that mirrors the structure of your IIS installation. Each node in the metabase structure is called a key, and each key can contain one or more IIS configuration values, called metabase properties. The IIS metabase keys correspond to the elements of IIS, and each key contains properties that affect the configuration of its associated element.
Most of the IIS configuration keys and values that were stored in the system registry for earlier versions of IIS are now stored as properties in the metabase. New keys and values have been added for finer and more flexible control of IIS. The metabase was designed to allow the same property to be set differently at different nodes. For example, the MaxBandWidth property setting can be a different value for each server.
The general structure of IIS is shown in the following figure, which is arranged by key types. The metabase structure of your IIS installation can consist of a varied number of elements, depending on your installation choices. Metabase keys associated with IIS elements are addressed by their paths within the metabase. See Key Names and Paths.
The top-level metabase key, named Computer, contains properties such as MaxBandWidth. These properties affect the overall execution of IIS on your computer. Two subkeys of the Computer key are associated with FTP services and Web services, respectively, and contain properties that affect all FTP and Web servers hosted on that computer.
Subkeys of the FTP service key are associated with individual FTP servers, and contain properties specific to each FTP server. A subkey of each FTP server key is associated with the root virtual directory for that server. Other subkeys are added to the root virtual directory key as you add virtual directories to your FTP servers. Each of these subkeys contains properties that affect the operation or configuration of the associated virtual directory. The Info key, directly subordinate to the FTP service key, also contains some properties associated with the FTP service.
Subkeys of the Web service key are associated with individual Web servers, their root virtual directories, subordinate virtual directories, disk directories, and files. A subkey of the Web service key affects the configuration of filters used by Web service operations. The Info key, directly subordinate to the Web service key, also contains some properties associated with the Web service.
Other keys directly subordinate to the top-level key contain properties that affect logging and MIME mappings. The IISADMIN key is used to record DCOM extensions to IIS.
Keys can also contain references to objects that can be used by the IIS Admin Objects. For example, the CertMapper key does not contain any metabase properties, but it does provide access to the IIsCertMapper object and its methods for mapping certificates.