Microsoft Exchange Server 2003

Installing Exchange is only the first step along a very long path. The server needs continued care and maintenance to deliver a reliable messaging service to users and to interact with other servers in the organization. At a conceptual level, Exchange is not particularly difficult to manage. The server is reasonably straightforward and the management interface is mature and meets the majority of administrative needs. However, Exchange does not function in a vacuum, and complexity mounts through its interaction with and dependency on the operating system, third-party products, other Microsoft servers and services, and so on. In addition, complexity increases further as the number of servers grows in the organization. In this chapter, we will look at the challenges involved in day-to-day Exchange operations, covering topics such as setting up and managing the user community, quotas, and so on.
Exchange divides basic administration into two areas: users and servers. On Exchange 2000 servers, you perform user management through Active Directory Users and Computers, and server management through the Exchange System Manager console (ESM). The logic here is that you are acting on quite different objects. Users, which include contacts and groups, are AD objects that may or may not be mail enabled. Users are stored in AD organizational units (OUs). Servers are also AD objects, but the AD holds server details in quite a different naming context or location. Along with other organizational data such as connectors, details of Exchange servers are stored within...