Reset Virtual Directory In Exchange 2010 SP1 Beta…

One of the common questions in forums after Exchange 2007 was released was "how can I recreate/reset my virtual directory". The need for recreating comes in when the directory files gets damaged or corrupted. In both 2007 & 2010 RTM, this can only be achieved by running shell cmdlets.

This option has now been exposed in the 2010 SP1 Beta Console. Navigate to Server Configuration -> Client Access. From the right hand action pane, select "Reset Virtual Directory". You click the same button irrespective of which directory needs to be reset.

Reset VDir

The "Reset Client Access Virtual Directory" wizard brings the "Browse" button to select the directory to be reset. It clearly says in the wizard that the directory will be deleted and re-created with the default settings.

Select VirD to reset

Click on the "Browse" button to get a list of all virtual directories and select the required one. I have selected OWA. You can select multiple directories if needed.

Browse VirD

The current settings of the virtual directory will be stored in a text file and you can change the location, if the default one is not good enough.

Store current VirD settings in a text file

Click the "Reset" button to proceed.

Confirm reset of VirD

The completion wizard highlights the need to run iisreset /noforce for the changes to take effect.

Run iisreset

Click Finish and your directory will be reset with the default settings.

2 thoughts on “Reset Virtual Directory In Exchange 2010 SP1 Beta…”

  1. EMC won’t even open to get this far. The situation is this: I installed Exchange 2010 but fat-fingered the server name when I created the server. So I uninstalled Exchange via add/remove used the Wizard,etc. Fist fought with getting rid of the Arbitrated mailboxes, etc but got all that done Exchange uninstalled properly via Wizard.

    Removed the server from the Domain, changed the server name, readded it to Domain.

    Reinstalled Exchange 2010 all went well until I tried to open the EMC. It is not connecting and the issue is it is still looking at the old server name “The attempt to connect to “Http’oldservername’ using Kerberos…..”. So any ideas on how to fix this?


Leave a Comment