|
This preparation guide includes information
about:
|
Exam News
Exam 70-285 became available March 26, 2004.
Audience Profile
The Microsoft Certified Systems Administrator (MCSA) and
Microsoft Certified Systems Engineer (MCSE) on Microsoft Windows
Server™ 2003 credentials are designed for IT professionals who
work in the typically complex computing environment of medium to
large companies.
A candidate for this exam should have at least one year of
experience implementing and managing an Exchange messaging
system in environments that have the following characteristics:
- 250 to 5,000 or more users
- Three or more physical locations
- Network services and resources such as multiple versions
of Exchange Server, Active Directory, proxy server, firewall,
other messaging systems, DNS, Internet, intranet, and mobile
client computers
- Three or more domain controllers
- Two or more Exchange Server computers
- Connectivity requirements such as connecting branch
offices and individual users in remote locations to the
corporate network and connecting corporate networks to the
Internet
Skills Being Measured
This certification exam measures your ability to analyze business requirements for a Microsoft Exchange Server 2003 organization and design an appropriate messaging infrastructure based on these requirements. Before taking the exam, you should be proficient in the job skills listed in the following matrix. The matrix shows which Official Microsoft Learning Products may help you reach competency in the skills being tested in the exam.
|
Designing an Upgrade or Migration and Coexistence Strategy |
Design an upgrade strategy from previous versions of Exchange. Considerations include upgrading from Exchange 2000 Server or Exchange Server 5.5, whether to upgrade the existing organization or create a new organizational structure, and designing connection agreements.
- Upgrade from Exchange Server 5.5.
- Upgrade from Exchange 2000 Server.
|
Design coexistence and migration of Exchange Server 2003 with other messaging systems. Considerations include cc:Mail, MSMail, previous versions of Exchange, Lotus Notes, X.400 messaging systems, PROFS, SNADS, and Groupwise.
- Plan for coexistence/migration with foreign mail systems, such as Notes, cc:Mail, GroupWise, MS Mail, PROFS, TAO, and SNADS.
- Plan for coexistence with Exchange Server 5.5.
- Plan for coexistence with Exchange 2000 Server.
|
Design the integration with the existing or planned Active Directory. Considerations include potential changes to the current or planned Active irectory structure, and inter-organizational connectivity and synchronization.
- Identify any changes needed to the Active Directory.
- Design inter-organizational connectivity and synchronization.
|
|
Designing the Exchange Server 2003 Infrastructure |
| Design an Exchange Server 2003 administrative model. Considerations include business factors, existing and planned administrative model, organizational unit (OU) structure, policies, administrative group placement and boundaries, and permissions.
|
Designate and design servers. Server configurations include server placement, connectors, client computer access, and multiple protocols.
- Design server placement.
- Design Server Specialization.
|
Design Exchange Server 2003 Public Folder Infrastructure. Considerations include company structure, geographical structure, maintenance policies, permissions, replication and indexing.
- Determining Public Folder Referrals.
- Design Public Folder Security.
|
|
Design the storage strategy. Considerations include optimal database sizing, logging strategy, stores and storage group configurations. |
Design servers to achieve fault tolerance and increased performance. Considerations include server scalability, storage fault tolerance, front-end back-end topology, and clustering.
- Determine approach for scalability.
- Hardware fault tolerance (RAID).
- Design the front-end/back-end servers.
- Microsoft Cluster Server (MSCS) Clustering.
|
|
Design a backup and recovery solution. Considerations include planning backup scope, defining the backup schedule, media storage and rotation, backup type, recovering the entire messaging system, individual databases, and servers; re-associating user mailboxes with accounts; and designing mailbox stores to support recovery. |
|
Designing Connectivity for Exchange Server 2003 |
Design an Exchange Server 2003 routing group topology.
- Plan traffic flow. Considerations include ADC computer and bridgeheads, routing group boundaries, bandwidth, public folder replication, and existing network connections.
|
|
Design Exchange 2003 Connectors. |
|
Design Exchange 2003 Virtual (protocol) Server Strategy. |
|
Design a fault-tolerant DNS solution. |
Design Client strategy for Exchange Server 2003. Considerations include hardware, operating system, access method, existing message store requirements, and existing message clients.
- Design a strategy for mail access. Messaging clients include MAPI, IMAP4, POP3, RPC over HTTP, and HTTP mail.
- Plan deployments of messaging clients. Considerations include policies and profiles.
|
|
Designing the Security Strategy |
Design an authentication and encryption strategy. Considerations include user authentication and encryption requirements, such as S/MIME, IPSec, NTLM, Digest authentication, and SSL.
- Outlook Web Access (OWA)
- Outlook Mobile Access (OMA)
- Secure/Multipurpose Internet Mail Extensions (S/MIME)
|
Design protection from external threats. Considerations include protection from unsolicited commercial e-mail, viruses, spoofing, and firewalls.
- Block SMTP Relay
- Virus protection
- Protect from unsolicited commercial e-mail (spam)
- Protect from spoofing
- Firewall configuration
- Content filtering
- Blacklists
|
Protect the Exchange Server 2003 infrastructure against internal attacks.
- Physical security of the computer
- Virus protection
- Permissions
- Internal firewall
|
|
