Managing Exchange Server 2003

Managing Exchange Server 2003 in this context is not about how to perform necessarily common tasks such as using the interface to add a database. Instead, managing Exchange Server 2003 includes identifying and working with the server's functional roles in the network environment, auditing network activity and usage, and monitoring the environment.

Similarly with Windows Server 2003, Microsoft has come a long way with how servers can be managed. Exchange Server 2003 management can be done locally or remotely. Although local and remote management could be done in previous Exchange versions, Exchange Server 2003 supercedes that functionality with new and improved processes and tools that assist administrators in their management.

Managing by Server Roles and Responsibilities

Exchange Server 2003 systems can participate in various responsibilities in the messaging environment. Some of these responsibilities may be intertwined due to budget constraints, business requirements, or technical justifications. No matter how the roles and responsibilities play out in the environment, it's important to manage them appropriately based on the roles of the server. The management aspects for some of the roles that Exchange Server 2003 can undertake are listed in the following sections.

Mailbox Store Server

An Exchange Server 2003 mailbox store server, also known as a back-end server, is primarily responsible for safely storing a mail-enabled user's messages, attachments, files, folders, and other files. Messages sent to a user are stored in the user 's mailbox, which is contained within a mailbox store.

For this reason, the mailbox store databases require attention using the Exchange System Manager (ESM) and frequent maintenance routines. Refer to "Best Practices for Performing Database Maintenance" for more information. Equally important, however, is managing user accounts.

Public Folder Server

Similar to the mailbox store server role, the public folder server role stores message postings and other messages in a hierarchical fashion. Although there isn't a user object specifically associated with a public folder, an entire public folder database is dedicated to a single public folder hierarchy. When the system has multiple public folders, there will be multiple databases to manage and maintain.

Front-end Server

Front-end (FE) servers are Exchange Server 2003 servers that do not contain mailbox or public folder stores. In fact, FE servers typically serve as proxy servers to back-end (mailbox or public folder) servers. FE servers are possible because Internet Information Server (IIS) manages messaging- related protocols, such as Internet Message Access Protocol version 4 (IMAP4), Post Office Protocol version 3 (POP3), Network News Transfer Protocol (NNTP), and Messaging Application Programming Interface (MAPI). One of the most common roles of an FE server is to provide Web access to back-end mailbox or public folder stores using Outlook Web Access (OWA).

Although there aren't any databases to manage or maintain on an FE server, keep the following important considerations in mind:

• Connections Users connect to FE servers using HTTP. They may also connect via Secure Sockets Layer (SSL) for encrypted communications if the server is configured for increased protection. These connections are important to monitor, especially when the FE server is on the perimeter network (also known as the DMZ) or otherwise facing the Internet. Another management and maintenance aspect to keep in mind is authentication and access controls. Periodically review the event logs to review security issues.

• IIS Metabase Because IIS is one of the driving forces behind an FE server, it is critical to manage the IIS metabase to maximize the server's health. This can involve keeping the metabase backed up, reviewing IIS logs, and reviewing security.

Bridgehead Server

An Exchange Server 2003 bridgehead server is a connection point among other Exchange servers either inside or outside the organization. It connects other servers that use the same communications protocols. The most notable examples are bridgehead servers connecting routing groups and connecting dissimilar mail systems. These systems require special attention to their specific functionality and often require an administrator to keep closer watch on the server for a given period of time. For instance, a bridgehead server hosting connectors to foreign messaging systems requires an administrator to monitor connections to the server, the specific connectors, and other messaging systems with which it interacts .

SMTP Relay Server

SMTP relay servers are similar to bridgehead servers in that they both can route messages from one system to another. They serve as mail gateways that relay mail. Mail systems facing the Internet can route mail to internal mail systems or to other external systems. It is not recommended however to allow your SMTP relay server to route messages between two external hosts on the Internet, because your system can then be used for spamming . When managing SMTP relay servers, keep track of how the system is being used and periodically check whether it is routing between external hosts on the Internet.