Restore iis metabase file

Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. General for IIS 7 and above. Sign in to vote. Once server restart you need to restore the IIS metabase file from the backup which you have taken manually: Once you click restore , you will be prompt for a message, read it and click Yes to continue It will prompt passcode to continue. I just finished the "Upgrade from Exchange to " Part I screencast and must tell you that it is extremely well done!

At the end of Part Bob Duffett, Priority Software Inc. Windows Server R2 Series. Exchange Server Series. Windows Server Series. SBS Screencasts Series. Leave this field empty. Home About. Related Reading.

June 7, May 11, Last, validate that the change has taken place. We know that by default that we should only see 10 directories at a time as defined by the IIS schema.

After we increase the maximum values kept by IIS, we need an easy method to trigger many directories to be created. To simulate this, we lower the default value for the period attribute to its default minimum of 10 seconds.

This increases the interval for checking for changes and hence potentially creates more copies of the files in a dynamic environment. Save this as ConfigHst. Run this VBS file by opening a command prompt, locating the file location where saved, and type the following:.

This script makes calls to modify the configuration of IIS every 15 seconds. This is enough time for the configuration history to check for changes and create a backup. After completing this, we see a multitude of configuration backups in our backup directory.

After running this script, notice how this feature pushes the oldest out when hitting the maximum i. Figure History Directory with maxistories value of In this task, we successfully modified the number of backups stored by IIS. The default setting of 10 is sufficient for many; yet, for dynamic environments such as shared hosting servers where customers are signing up for sites randomly and often, it is good practice to have a more thorough history.

In this task, we modified the maxHistories and period attributes for configHistory section and then produced multiple changes that would show that we stored more than 10 the default copies. The number of history directories and associated files stored by IIS is configurable to be flexible depending on the environment. For many cases, storing the history files on the system path i. Unlike history in IIS 6. We use in this task a method to modify the configuration--in this case, the IIS command-line interface.

The goal of this task is not only to learn about changing the path for configuration history directories, but also to become familiar with AppCmd. This step is required because no directory is automatically created if it does not exist.