Prior to IIS 7, Microsoft 's Internet Information Services stores its information in an internal database called the MetaBase . The metabase is an inheritable, hierarchical database that allows for configuration of HTTP / HTTPS , FTP , SMTP , and NNTP at the server, the site, or the folder or file level. Different versions of IIS use different formats; prior to IIS version 6 this was always a proprietary format, whereas with 6.0 and later the data is stored in XML files. The metabase consists of two files, MetaBase.xml and MBSchema.xml, stored in the %SystemRoot%\system32\inetsrv\ directory. The metabase periodically gets backed up to the MetaBack subdirectory.
7-542: When Internet Information Service starts, it reads the two metabase files to create an in-memory cache of the web server's configuration, which is referred to as the in-memory metabase . Changes to the IIS configuration via the IIS Manager or programmatic changes get written to the in-memory metabase, then are persisted to the on-disk MetaBase.xml file after a number of changes. Internet Information Services' central metabase
14-498: Is eliminated in IIS version 7 in favor of a set of XML configuration files that are located centrally in the Machine.config and ApplicationHost.config files and within the web site's infrastructure using web.config files. This allows for synchronization of web sites across servers by including all configuration information within the web site's root directory. The IIS Manager interface, an MMC -based administration console,
21-669: Is the primary means of modifying the Metabase. IIS also optionally provides a web-based administration console. The XML files are human-readable, and when the Allow direct metabase edits feature is turned on (not recommended by Microsoft) it can be viewed and edited with simple text editing software like Notepad . The Metabase is also programmable through several APIs - Admin Base Objects (ABO), Active Directory Services Interface (ADSI), Windows Management Instrumentation (WMI), and
28-607: The .NET Framework 's System.DirectoryServices and Microsoft.Web.Administration. The Metabase can also be administered using the Metabase Explorer tool which is part of the Internet Information Services (IIS) 6.0 Resource Kit Tools Microsoft Management Console Microsoft Management Console ( MMC ) is a component of Microsoft Windows that provides system administrators and advanced users an interface for configuring and monitoring
35-526: The Microsoft Developer Network 's web site. Snap-ins are registered in the [HKEY_CLASSES_ROOT]\{ CLSID } and [HKEY_LOCAL_MACHINE\Software\Microsoft\MMC\Snapins] registry keys. A snap-in combined with MMC is called a management saved console , which is a file with .msc extension and can be launched using this syntax: mmc path \ filename.msc [/a] [/64] [/32] . The most prolific MMC component, Computer Management, appears in
42-805: The "Administrative Tools" folder in the Control Panel , under "System and Security" in Category View. Computer Management actually consists of a collection of MMC snap-ins, including the Device Manager , Disk Defragmenter , Internet Information Services (if installed), Disk Management , Event Viewer , Local Users and Groups (except in the home editions of Windows), Shared Folders , Services snap-in, for managing Windows services , Certificates and other tools. Computer Management can also be pointed at another Windows machine altogether, allowing for monitoring and configuration of other computers on
49-542: The system. It was first introduced in 1998 with the Option Pack for Windows NT 4.0 and later came pre-bundled with Windows 2000 and its successors. The management console can host Component Object Model components called snap-ins . Most of Microsoft's administration tools are implemented as MMC snap-ins. Third parties can also implement their own snap-ins using the MMC's application programming interfaces published on
#537462