The legacy system handles applications differently: they are simply virtual directories with a special property to mark them as applications (AppIsolated, or AppRoot). For example, the new system has a concept of applications, under each site and above all virtual directories. Mapping is done to translate back and forth between the ABO view back and the new system view. Web server configuration is typically under LM/W3SVC, including custom properties, with some few additions like Mime Maps. The mapping decision is based on the Metabase node in question. Note that even custom properties that are under the web server configuration are mapped to (and persisted in) the new system. If it is related to FTP, or SMTP, or NNTP configuration, then it follows the regular logic of the Metabase system and ends up in the Metabase file. If the information in the method call is related to the web server configuration, it is mapped to the new system. The Metabase Compatibility feature runs inside the Metabase service (IISADMIN). When all of the legacy scripts and applications are ported to the new interfaces, it is recommended to uninstall the Metabase Compatibility feature. It is also recommended that new scripts and applications be developed using the new interfaces, so they work ideally with the new system, and can have access to the new properties, concepts and structure of the configuration system.

more and more web.config files with IIS settings in them are present on the system), customers will consider porting legacy scripts and applications over to the new system and its interfaces. The legacy interfaces have some limitations and are not ideal for working with distributed configuration files (see Limitations section below) therefore it is recommended that over time, and especially when opening up the configuration system for more and more delegation (i.e.

This component is not installed by default because IIS is not initially set up to use it. You can find this component in setup under Internet Information Services->Web Management Tools -> IIS 6.0 Management Capability Feature.

Installing Metabase Compatibility Support By default, this component is not installed.

Metabase database support