1. CONFIGURING A MICROSOFT EXCHANGE SERVER 2003 INFRASTRUCTURE
Chapter 3

2. OVERVIEW Postinstallation considerations
Administrative and routing groups
Mixed mode and native mode
Front-end and back-end servers

3. POSTINSTALLATION CONSIDERATIONS
Exchange Server 2003 services
Delegation of authority
Administration from client workstations
Adding and removing Exchange Server 2003 components

4. EXCHANGE SERVER 2003 SERVICES

5. EFFECT OF STOPPED OR FAILED SERVICE
Internet Message Access Protocol version 4 (IMAP4) or Post Office Protocol version 3 (POP3)
Information store
Exchange management
Message Transfer Agent (MTA) stacks
Exchange routing
Site replication
System attendant

6. SERVICE DEPENDENCIES System attendant Information store IMAP4 POP3
MTA stacks
Management
Routing engine
Event

7. DELEGATING AUTHORITY Exchange Full Administrator
Exchange Administrator
Exchange View Only Administrator

8. ADMINISTRATION FROM CLIENT WORKSTATIONS
Install Exchange System Management Tools from Exchange Server 2003 CD
Tools should be installed on a workstation
Workstation or server must be a member of the same forest and domain as the Exchange organization

9. ADDING AND REMOVING COMPONENTS
Run Exchange Server 2003 Setup
Access the Component Selection page
Specify components to be added or removed

10. ADMINISTRATIVE AND ROUTING GROUPS
Large Exchange organizations
Multilocation Exchange environments
Administrative and routing group plan detemines where you install Exchange Server 2003

11. ADMINISTRATIVE GROUPS
Logical grouping of Exchange resources
Administrative groups define administration topology
Administrative topology not tied to physical topology

12. WHAT ADMINISTRATIVE GROUPS CAN CONTAIN
Servers
Policies
Routing groups
Public folder trees

13. ENABLING ADMINISTRATIVE GROUPS

14. ADMINISTRATIVE MODELS
Centralized
Decentralized
Mixed

15. CENTRALIZED ADMINISTRATIVE MODEL
Small and medium-sized companies
Large companies with specialized system support groups
Small number of administrative groups

16. DECENTRALIZED ADMINISTRATIVE MODEL
Large organizations
Independently operating branch locations
Large number of administrative groups

17. MIXED ADMINISTRATIVE MODEL
Some aspects of Exchange organization centrally managed
Some aspects of Exchange organization locally managed

18. ROUTING GROUPS Related to physical layout
Similar concept to Active Directory sites
Multiple physical locations connected by wide area networks (WANs)
Typically one routing group for each location
Method of controlling message transfer

19. MOVING SERVERS BETWEEN ROUTING GROUPS
Restrictions apply to mixed-mode operation only
You can only move servers between routing groups within the same administrative group
To move a server to a routing group that is in a different administrative group:
Either move the server to the administrative group that contains the target routing group
Or move the entire routing group from one administrative group to another

20. CONNECTING ROUTING GROUPS
Routing group connectors
One way
Specify bridgehead servers
Reliable, persistent connections
SMTP connectors
X.400 connectors

21. MIXED MODE AND NATIVE MODE
Mixed mode and native mode concepts
Benefits of mixed mode
Limitations of mixed mode
Criteria for switching to native mode
Advantages of native mode

22. MIXED MODE AND NATIVE MODE CONCEPTS
Native mode offers full Exchange functionality
Mixed mode offers interoperability with Exchange Server 5.5
Exchange Server 2003 operates in mixed mode by default
Switching to native mode is irreversible

23. MIXED MODE
Provides interoperability between servers running Exchange Server 2003 and Exchange Server 5.5
Seamless routing between Exchange Server 2003 and Exchange Server 5.5
Exchange Server 2003 can use existing Exchange Server 5.5 connectors and gateways

24. CRITERIA FOR CONVERTING TO NATIVE MODE
No servers in the organization run Exchange Server 5.5
No plans exist to add servers running Exchange Server 5.5
The organization will never require interoperability with servers running Exchange Server 5.5
The organization does not use any connectors or gateway applications that run only on Exchange Server 5.5

25. ADVANTAGES OF NATIVE MODE
Routing group and administrative group flexibility
Moving mailboxes
Moving servers
Query-based distribution groups (QDGs)
8BITMIME data transfer

26. CONVERTING TO NATIVE MODE

27. FRONT-END AND BACK-END SERVERS
Front-end servers handle incoming client connections
Back-end servers run the mailbox and public folder stores
Front-end servers do not contain mailbox and public folder stores
Back-end servers do not directly access the outside world

28. BENEFITS OF FRONT-END AND BACK-END ARCHITECTURE
Unified namespace
Reduced Secure Sockets Layer (SSL) overhead
Firewall security

29. FRONT-END SERVER REQUIREMENTS
Fast CPU
Large amount of memory
Virus scanning software
Back up hard disks if SMTP enabled

30. STANDARD FRONT-END AND BACK-END TOPOLOGY

31. FRONT-END SERVER BEHIND THE CORPORATE FIREWALL

32. FRONT-END SERVER IN THE PERIPHERAL ZONE

33. LOAD BALANCING ON THE FRONT-END SERVER

34. SUMMARY Plan postimplementation configuration
Choose administrative model
Plan administrative groups
Plan operation mode—switch to native mode whenever possible
Plan configuration—decide whether to use front-end and back-end
Plan firewall configuration