Aside from the Microsoft Outlook Forms Designer, there are a variety of ways to build client−based applications using Exchange Servers messaging capabilities:
Microsofts 95, 97, and 2000, 2002, and 2003 versions of applications (Word, Excel, and so on) include some nice collaborative tools and easy−to−use routing−slip capabilities based on Exchange messaging. Applications from other vendors also incorporate these capabilities.
•
You can turn an Exchange message into any Object Linking and Embedding (OLE)compliant application just by inserting an object from the app into the message.
•
You can write programs that use Simple and Extended MAPI hooks or the X.400−oriented Common Mail Call APIs supported by Exchange Server.
•
You can develop programs that use Exchange 2003s new file−based and Internet−based mailbox and public−folder access capabilities.
•
Summary
Exchange Server organizing components give hierarchical structure to your entire Exchange system. The Exchange hierarchy begins with your Exchange organization. Organizations contain administrative groups. Administrative groups contain Exchange servers. Recipients are the lowest rung of the Exchange 2003 hierarchy ladder. Four types of Exchange recipients exist: Exchange users, distribution groups, contacts, and public folders. All of these have a virtual presence in Windows 2003s Active Directory. The mailboxes of mailbox−enabled Exchange users and public folders reside physically on Exchange servers. Distribution groups and contacts are only Active Directory objects.
Core Exchange components include the Information Store, Routing Engine, and System Attendant. Each Exchange server sports one instance of each of these components. An Information Store can have one or more storage groups, depending on whether youre using the Standard or Enterprise edition of Exchange Server. Storage groups can contain one or more mailbox stores and/or one or more public folder stores. The Routing
SMTP services to perform these tasks. The Routing Engine also moves messages between Exchange servers and Exchange connectors. The System Attendant is responsible for a range of monitoring, security, and system maintenance tasks.
Exchange Server 2003 comes with a dizzying array of optional components, components that arent required to start up Exchange server but that significantly enhance the Exchange environment. There are optional
components for managing your Exchange organization and individual Exchange servers, keeping Exchange addresses in sync with foreign messaging system addresses, doing full−text indexing of Exchange server content, servicing a wide range of Internet protocols, and connecting Exchange servers to each other and to foreign messaging systems.
Exchange clients come in a wide variety of sizes and shapes. The Outlook client is most tightly integrated with the whole Exchange system; the Internet−based Outlook Web Access client comes in a close second. In addition, users can access messages on their Exchange servers using Internet standard POP3 or IMAP4 clients. Legacy Schedule+ calendaring information is available to Schedule+ and Outlook client users. Finally, Outlook electronic forms and custom applications can serve as clients for data stored on Exchange Server 2003.
The first four chapters of this book were designed to give you a firm grounding in Windows Server 2003 and Exchange Server 2003 architecture and concepts. With this information under your belt, youre now ready to move into the very important area of preinstallation planning, which is the topic of the next chapter. I strongly urge you not to skip Chapter 5, Designing a New Exchange 2003 System. It not only provides you with some key information on planning, but it also discusses technical issues that are discussed nowhere else in this book.
Chapter 5: Designing a New Exchange 2003 System
Overview
Whether your system will be based on a single Exchange server in a single physical location and an
Exchange 2003 administrative group or hundreds of Exchange servers spread out over multiple locations and administrative groups, you need to consider a number of design issues before implementation. This chapter presents a step−by−step planning model based loosely on a process developed by Microsoft. Tracking and retracking through these steps will help your organization decide where it wants to go with electronic messaging and how it can get there with Exchange. I can tell you from lots of experience that this process really works. Generally, Ive found that I can gather any required information and generate a fairly complex first−draft plan, complete with a most convincing executive summary, in a month or so.
This chapter isnt just about design, though. It also offers practical information about Exchange Server 2003 and how it works. For example, youll find detailed information about Exchanges network connection options: what they do and which networking topologies and protocols support them. Information such as this is central to designing and implementing an Exchange system, and its not found anywhere else in this book.
This is a long chapter covering a great deal of information in detail. Just as you wouldnt try to implement a complex Exchange system in one day, you shouldnt try to plow through this chapter in one hour.
Note Upgrading Exchange Server 5.5 systems to Windows Server 2003 and Exchange Server 2003 is covered in the next chapter. However, even if your immediate goal is an upgrade, I strongly suggest that you first carefully read this chapter.
Featured in this chapter:
Assigning accountabilities for planning, design, and management
•
Performing a needs assessment
•
Planning your network configuration
•
Rolling out the plan
•