nm-admin

It is a common situation when you get a call from a user who accidentally deleted a message or some other item from their mailbox (like calendar appointment or task item). You recommend straight away checking the deleted items folder and here you are informed that the user has just emptied the Deleted Items folder or has used “Hard delete” (the Shift+Del key combination).
Here comes the moment to use one of the extremely helpful exchange features – “Recover deleted items”. Normally Exchange does not actually delete items when the user empties the Deleted Items Container. It marks them with a special flag as purged so they do not display in MS Outlook or in OWA. The messages remain available for a period of time – the default is seven days.
Here you can see how to enable and use the “Recover Deleted Items” feature in MS Outlook.
We also demonstrate how to create and apply a Policy in Exchange System Manager which manages the Deleted Items Retention period for the Mailbox Stores in your Exchange organization.

There are cases when you have to change the location of Exchange database files.
You might be willing to improve the performance of your exchange server. Another serious reason
could be the Exchange database partition running out of
space.
Here you can see how this can be done.

There are cases when you need to reset the default virtual directories that are required to provide Outlook Web Access, Exchange ActiveSync, and Outlook Mobile Access services in Exchange Server 2003.
If you have messed up some of the virtual directories or OWA is hanging (working sporadically), resetting the directories the way it is demonstrated in the following video tutorial could resolve your problem.

There are two categories of Metabase corruption:
– Structural corruption
If you want to check your Metabase for structural corruption you can do this very quickly by trying to open it with Metaedit 2.2 for IIS5 or Metabase explorer for IIS6.
NOTE: If you have a Windows 2003 server in your domain you can install Metabase explorer on it and open remotely both IIS5 and IIS6 metabase. You can download Metaedit 2.2 from here and Metabase explorer from here.
– Logical corruption
Enabling Diagnostic logging for MSExchangeMU (Metabase Update) to maximum can give you more information about sync errors between AD and the Metabase.