This document covers what to capture with Performance Monitor to troubleshoot Exchange performance problems.  Section 1 lists the Performance Objects & Counters used when analyzing a performance problem with an Exchange Server.  Section 2 explains what data is gathered by the counters and some values to look for.

If you mistakenly delete a mail-enabled user account, you can recreate that user object and then, by default, reconnect that mailbox for a period of 30 days. This is because when you delete a user, Exchange retains a users mailbox for a specified period.

You configure Exchange to retain a user’s mailbox in the way that you specify how many days Exchange retains mail that a user deletes. You configure a deleted-mailbox retention period at the mailbox store object level.

When restoring a mailbox to an Exchange 5.5 recovery server, install Exchange on the recovery server by using the same logical organization and site names. The server names and service accounts do not have to match, unless you are restoring the directory service database. Exchange 5.5 servers on a site become aware of each other during the installation process, specifically, when you join a new server to a site.

Recovering an Exchange 2000 mailbox is somewhat different from recovering an Exchange 5.5 mailbox. There is no dedicated Exchange directory database in Exchange 2000 because Exchange directory information is now stored in Active Directory. Therefore, install both Exchange 2000 and Active Directory on your recovery server.

To sufficiently isolate the recovery server from other Exchange servers in the production organization, you must install Active Directory as the root of a separate forest. It may also be necessary to configure the recovery server as a Domain Name System (DNS) server if the corporate DNS server’s permissions model denies you the rights to create necessary service records in it.

Overview
This document provides background and reference material for administrators who are deploying or have deployed Live Communications Server 2005. The following topics are featured:

•     Active Directory schema extensions
•     Archiving database structure and schema
•     Back end database maintenance
•     BENOTIFY request
•     Error messages
•     Flat file logging
•     Performance counters
•     Permissions
•     Proxy registration keys
•     Server certificate revocation
•     Message routing diagrams
•     Additional references

Download: Live Communications Server 2005 Document: Reference Guide

Abstract:  Even when retention policies are in place, companies often have only a matter of days to turn over requested documentation for government audits or litigation -- so the laborious and expensive process of sifting though backup tapes and email archives for specific phrases or keywords is not acceptable.

Learn how HP's new Reference Information Storage System (RISS) eliminates the need for this costly and time-consuming discovery process. RISS, an active archiving platform that transforms the tedious search for specific unstructured data into exploitable information that can be retrieved in seconds.

Abstract:  Enterprises are becoming increasingly interested in easy-to-use email encryption, as a wide variety of privacy and data protection regulations now apply to small, medium and large organizations across a wide variety of industries. Effective secure messaging technologies keep sensitive information private, prevent anyone from tampering with the contents of messages and authenticate the identity of both the sender and recipient. And all organizations, regardless of their size, require encryption to be both user- and IT-friendly.

Abstract:  Exchange systems have become mission critical systems. This is why almost every organization using Microsoft Exchange Server has implemented some form of high availability to ensure their systems are continuously up and running. This paper examines a number of solutions you can use to meet these high availability requirements outlining the benefits and drawbacks of each. Furthermore, it makes additional recommendations on how you should implement solutions for continued service resiliency. If high availability is what you need, this paper is a must.
Author(s):
Danielle Ruest
Nelson Ruest

Abstract:  This technical brief will provide a high-level overview of considerations for companies that are thinking of migrating from Novell GroupWise to Microsoft Exchange 2003. It is intended to assist messaging managers and directors grappling with the many complexities associated with a migration project and provide guidance before, during and after the migration.
Author(s):
Ron Robbins, Product Manager

Abstract:  For those still running Exchange 5.5, the end of Microsoft support on December 31, 2005, has the potential to leave these customers open to security vulnerabilities. In order to ensure a successful migration, it is integral that these security weaknesses be addressed while migrating to Exchange Server 2003.

This white paper, written by one of the industry's leading e-mail security authorities, Lee Benjamin, outlines solutions that can be implemented now that will protect Exchange 5.5 and continue to provide best-practice security during and after the migration to Exchange Server 2003. Read about Microsoft's Internet Security and Acceleration Server (ISA) 2004 that can be used to protect all versions of Exchange. A defense-in-depth architecture is suggested, with ISA positioned behind a perimeter firewall and in front of the Exchange Servers. In addition, NS Appliances are introduced as a cost-efficient way to implement ISA 2004.