As Needed Tasks
Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2007-01-17
Perform the following tasks as necessary; however, they are frequently also covered by standard procedures:
- New and Departing Users New users typically require a user account, a mailbox, certain rights and group memberships, possibly an e-mail copy of the organization’s IT and security procedures, and so on. Document the exact requirements and a procedure to fulfill the requirements so that new users can be established quickly. People who leave the organization must have access to their mailbox and other systems revoked (often urgently). You may require a policy to define what should be done with e-mail destined for the user (for example, should it be re-routed or rejected). You will also need a procedure to explain what happens to a user’s Exchange data after they leave the organization.
- Public Folder Creation You can grant users permission to create some public folders, but other folders (especially top-level folders) should be created by administrators only. A procedure should define who can make requests and what permissions should be applied.
- Mailbox Recovery You can recover an entire mailbox from the deleted mailbox retention dumpster or from a database backup by using a recovery storage group. Create a procedure for mailbox recovery. For more information about mailbox recovery options, see: Single Mailbox Recovery.
- Full Security Audit You can perform this audit regularly, in response to an upgrade or redesign of the messaging system, or in response to an attempted (or successful) security breach. The procedure may involve port scans on servers and firewalls, audits of security fixes, and third-party penetration tests.
- Update Performance Baselines Update performance baselines after an upgrade or configuration change. You can use baselines to measure performance changes and to detect problems that affect system performance.
- Database Maintenance Exchange databases can become fragmented over time. Typically, online maintenance is sufficient to address this issue. However, in some cases manual defragmentation may be warranted, for example, after moving or deleting a large number of mailboxes. By defragmenting the databases, you can reduce the file size and create contiguous storage space. You can defragment Exchange databases by using Exchange Server Database Utilities (Eseutil.exe). For more information about Eseutil, see Eseutil.
- Other Database Maintenance Other database maintenance is usually reserved for times when you are performing system troubleshooting. You can resolve inconsistencies in Exchange databases by verifying and repairing the integrity of the database with the Information Store Integrity Checker (Isinteg.exe). For more information about Isinteg, see Isinteg. You can also use the Eseutil.exe tool to check database integrity. It is useful to include procedures using Isinteg.exe, Eseutil.exe, and other standard tools in your formal troubleshooting documentation.