Partager via

Configuring the Metabase History Feature in IIS 6.0

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1

By default, the metabase history feature is enabled and the number of history file pairs (MetaBase.xml and MBSchema.xml) that are saved within the history folder is defined by the default value of the MaxHistoryFiles Metabase Property. If the EnableHistory Metabase Property is not written in the MetaBase.xml file, then IIS interprets the absence of the property to mean that the history feature is enabled and the MaxHistoryFiles Metabase Property is set to the default value. For information about the default values of properties, see the Metabase Property Reference.

Procedures

The procedure title

  1. Open the MetaBase.xml file by using a text editor (MetaBase.xml is located in the systemroot\system32\inetsrv directory), and then navigate to the /LM level.

  2. If the EnableHistory Metabase Property and MaxHistoryFiles Metabase Propertyare not in the metabase, add them at the /LM level.

  3. Set the value of the EnableHistory property to 0 (zero).

  4. Save the MetaBase.xml file.

To enable the metabase history feature

  1. Open the MetaBase.xml file by using a text editor (MetaBase.xml is located in the systemroot\system32\inetsrv directory), and then navigate to the /LM level.

  2. Set the value of the EnableHistory Metabase Property property to 1 or remove the EnableHistory property from MetaBase.xml.

  3. Save the MetaBase.xml file.

To change the number of history files that are stored in the history folder

  1. Open the MetaBase.xml file by using a text editor (MetaBase.xml is located in the systemroot\system32\inetsrv directory), and then navigate to the /LM level.

  2. Change the value of the MaxHistoryFiles Metabase Property.

  3. Save the MetaBase.xml file.

Warning

Disabling history files can have serious consequences. Without history files, you might have to reconfigure the IIS server from an empty state. Also, you should ensure that the history files are protected by access control lists (ACLs). By default, only members of the Administrators group can view the history files. For information about configuring ACLs, see "Access control" in Help and Support Center for Windows Server 2003.