CERTguide 70-225 Study Guide
What is 70-225 all about?
Exam 70-225: Designing and deploying a Messaging Infrastructure with Microsoft Exchange 2000 Server
When you pass this exam, you achieve Microsoft Certified Professional status. You also earn credit toward the following certifications:
n Elective credit toward Microsoft Certified Systems Engineer on Microsoft Windows 2000 certification
According to Microsoft,
“
This certification exam measures your ability to implement, administer, and troubleshoot information systems that incorporate Microsoft Exchange 2000 Server.
”
Testing objectives include:
n Analyzing Business Requirements
n Analyzing Existing and Planned Resources
n Designing an Exchange 2000 Server Messaging Solution
n Designing for Fault Tolerance and Data Recovery
n Deploying an Exchange 2000 Server Messaging Solution
The scale of the Exchange 2000 environment we are talking about in this exam are:
n Multiple physical locations
n Mixed client connection protocols, such as POP3, IMAP4, MAPI, NNTP, and HTTP mail
n Internet messaging connectivity
n Connectivity to foreign mail systems
n Multiple or complex name resolution systems.
It is recommended that you first start by studying the Active Directory topics. Remember, Exchange 200 closely integrate with Active Directory!
You should make yourself completely familiar with the technical side of Exchange Server 2000 before attempting this exam. This exam involves technical questions, but focus is more on the “Strategy” of design and deployment.
This exam is CASE STUDY BASED. You should download and try the Case Study-Based Test Demo available at http://download.microsoft.com/download/vb50pro/Update/2.0/W9X2K/EN-US/IIT_Demo.EXE to become familiar with these new types of questions before taking the exam.
Your focus on this exam is on the Exchange infrastructure options as well as Active Directory integration.
Remember, the answers, from our point of view, could appear highly subjective. You need to choose the BEST answer that fits your case.
Upgrade VS Migrate VS Consolidate
Main routes suggested by Microsoft to implementing Exchange 2000:
n Migrate from a foreign e-mail system
n Migrate from Microsoft Exchange Server 5.0 or 4.0
n Install new servers running Exchange 2000 and then migrate from Exchange 5.5
n Perform an in-place upgrade from Exchange 5.5 Service Pack 3
n Consolidate servers running Exchange 5.x/4.x into fewer servers running Exchange 2000
Upgrade
According to MS Technet:
"Upgrading is when the existing Exchange 5.5 organization is promoted to Exchange 2000. In an upgrade, you do not create a new organization."
MS suggested reasons to upgrade to Exchange 2000:
n Implementing specific features in Exchange 2000.
n Requiring increased scalability or availability options.
n Upgrading to Windows 2000 and want to unify the directory structure.
n Implementing Exchange Conference Server and want a single vendor solution.
In-Place Upgrade features:
n minimal new hardware
n simplest
n quick implementation
n fewer options for mitigating risk.
n server restoration is the only rollback option.
n unmanageable with a large number of connector servers.
Build New Upgrade features:
n easier to mitigate risk
n simple rollback
n allows you to pick-and-choose individual connectors to migrate.
n needs new or recycled hardware.
n human errors are possible
n takes longer to complete.
For single-server deployments, use in-place upgrade
For larger enterprises with many servers to upgrade, use in-place upgrade as an interim step. Also, deploy a test server in advance
*****************
Consolidate
According to MS Technet:
"Consolidation is the process of replacing two or more servers (usually running an earlier version of Exchange) with one computer running Exchange 2000. Hence consolidation can be either a migration or an upgrade, depending on whether you create a new organization or not.”
MS suggested reasons to consolidate:
n Reduced cost
n Increased quality of service
n Reduced complexity
n Reduced network traffic
*****************
Migration
According to MS Technet:
"Migration is moving from a previous version of Exchange or from a non-Exchange messaging system to Exchange 2000. With migrating, you are creating a new Exchange 2000 organization separate from your existing Exchange environment."
You should migrate your Mailbox and Public Folder servers first so that your users and administrators can immediately make use of Exchange 2000 specific features.
Note that the reasons for migrating are normally similar to those for upgrading.
*****************
BEST PRACTICE suggested by Microsoft - Upgrade or migrate options:
|
Current System |
Upgrade Or Migrate? |
|
Exchange 5.5 SP3 |
Upgrade or Migrate |
|
Exchange 5.5 pre-SP3 |
Upgrade or Migrate |
|
Exchange 5.0 |
Upgrade or Migrate |
|
Exchange 4.0 |
Upgrade or Migrate |
|
Microsoft Mail |
Migrate |
|
Lotus Notes |
Migrate |
|
Lotus cc:Mail |
Migrate |
|
Novell GroupWise |
Migrate |
|
Calibra Share |
Migrate |
Organization Types
The organization types you will encounter in the case study:
The table below is extracted from Microsoft Technet:
|
Centralized Network |
Distributed Network |
|
|
Centralized Administration |
Global
Headquarters (GHQ) |
Medium
National Organization (MNO) |
|
Distributed Administration |
Small
Branch Office (SBO) |
Large
International Conglomerate (LIC) |
The table below is extracted from Microsoft Technet on deployment time:
|
Number of Users |
Typical Organization Type |
Time for Planning and Deployment Process |
|
Less than 500 |
SNO, RBO, LBO, MBO |
2-5 months |
|
500 to 5000 |
MNO, RBO, SMO |
3-6 months |
|
5000 to 50,000 |
MNO, LNO, LMO |
6-12 months |
|
50,000+ |
LNO, LMO, LIC |
9-18 months |
The table below is extracted from Microsoft Technet on security model:
|
Organization Type |
Security Model |
|
Large International Conglomerate (LIC) |
Partly
Distributed |
|
Large Multinational Organization (LMO) |
Fully
Centralized |
|
Large National Organization (LNO) |
Fully
Centralized |
|
Medium National Organization (MNO) |
Fully Centralized |
|
Single Location Organization (SLO) |
Fully Centralized |
Large International Conglomerate
n geographically dispersed
n composed from the amalgamation or disbanding of several smaller but individually identifiable companies
n each company is administratively separate
n each company maintains its own network of Regional Offices and Branch Offices usually has a total combined workforce in excess of 20,000
n each component company is connected to its own branch offices by a network of various WAN links
Large Multinational Organization
n consists of a central organization with significant worldwide presence
n have a large headquarters with international regional offices and national branch offices
n administratively more centralized than the LIC
n larger branch offices have their own dedicated IT staff
n usually with a workforce of 10,000 or more
n regional and branch offices are connected to the headquarters by a network of various WAN links
Smaller Multinational Organization
n can have offices in more than one country
n often has a high level of technical awareness
n messaging options can range from a single server in the headquarters to each office maintaining an Exchange server but administered separately
Large National Organization
n consists of a central headquarters with a network of branch offices throughout a country
n without any significant overseas presence
n consists of a headquarters with a network of small, medium-size and large branch offices
n with a couple of larger regional offices
n usually with a workforce of 5,000 or more
Medium National Organization
n has a countrywide or regional operational scope
n usually has a network of small to medium-sized branch offices
n administrative control is moderately to heavily centralized
n branch offices are not large enough to have any dedicated IT staff
n typically with a workforce of 1,000 or more
Smaller National Organization
n a single country or regional company
n any branch offices are likely to be small to medium in size with no local IT staff.
n headquarters provides administrative control and support of the branch offices
n employee numbers could be from 500 upwards
n WAN links typically up to 64 kilobytes per second
n dial-on-demand or dial-up access more commonly used
Single Location Organization
n does not have any branch offices
n admin control is completely centralized or outsourced
n only WAN links are likely to be to the Internet
n company itself could be almost any size
Collaborating Organizations
n created when two or more organizations come together for some reasons, such as merger
n compatibility issues may arise
n there may be at least two Active Directory forests
n the companies are totally separate and autonomous administratively
n one variant occurs with companies that are merging or planning to take over other companies in the near future
Security Sensitive
n want to guard what they send
n need signing or sealing of communications
n can include
u encryption of message contents
u verification of a sender's identity
u SSL security on Outlook Web Access
Telecommuter-Friendly
n has a significant number of workers accessing information over RAS or dial-up networking
n company can be of any size and constitution
n normally security sensitive as well
MSF Project Framework
According to Microsoft Technet:
“To ensure that your Exchange 2000 upgrade project flows smoothly, you must create a structured project plan that covers every phase of the implementation. To do that, you can use any structure or methodology that you find suitable.”
The Microsoft Solutions Framework (MSF) format:
n Vision/Scope Phase
n Planning Phase
n Development Phase
n Proof of Concept Phase
n Pilot Phase
n Deployment Phase
n Post Implementation Review Phase
The MSF Team Roles:
n Program Management
n Product Management
n Development
n Testing
n User Education
n Logistics Management
MSF definitions:
n Envisioning – Identify the project goal.
n Planning – Develop functional specifications.
n Development – Create a test lab.
n Deployment – Implement the project.
Exchange and Active Directory
Simultaneous Deployment of Exchange and Active Directory – WHY? As said by Microsoft:
“Deploying Windows 2000 and Exchange 2000 at the same time saves time, simplifies the planning and deployment process, and provides important hands-on experience with Active Directory while still running Microsoft Windows NT® 4.0 and the Exchange Server 5.5 infrastructure. In addition, users can be upgraded to Exchange 2000 and Windows 2000 at the discretion of the administrator.”
Dependencies between Exchange 2000 and Windows 2000:
n Global Address List
n Global Catalog Servers
n Universal Groups
n Native Mode Considerations
n Client Connectivity
n Active Directory Forest Dependencies
n Active Directory Domain Dependencies
n Windows 2000 Site Relationships
n Active Directory Connector (ADC) Placement
n Public Folders
Limitations of Exchange 2000 in mixed mode as mentioned in Microsoft Technet:
n Exchange Server 5.0 and 5.5 sites map directly to administrative groups.
n Administrative groups map directly to Exchange Server 5.0 and 5.5 sites.
n You cannot move mailboxes between administrative groups.
n Routing group membership consists only of servers installed in the administrative groups.
You can change an Exchange 2000 organization to native mode after all of the servers are upgraded to Exchange 2000.
Features of Exchange 2000 running in native mode as mentioned in Microsoft Technet:
n Support for multiple routing groups.
n Routing groups can consist of servers from multiple administrative groups.
n Ability to move servers between routing groups.
n Ability to move mailboxes between administrative groups.
n Simple Mail Transfer Protocol (SMTP) is the default routing protocol.
If you are not planning to purchase new hardware to consolidate their servers running Exchange 5.5, perform the following steps as part of the upgrade:
n Upgrade the existing servers running Exchange to Exchange 5.5 with Service Pack 3 or later
n Upgrade the existing servers running Exchange from Windows NT 4.0 to Windows 2000 Server with Service Pack 1 or later.
* You must have at least one server running Exchange 5.5 with SP3 or later in every Exchange site to be upgraded.
The main upgrade steps when Active Directory is involved:
1. Populate Active Directory with user account information using Active Directory Connector.
2. Deploy global catalog servers to support Exchange 2000 and Microsoft Outlook® 2000 address lookups against Active Directory.
3. < Optional > Upgrade Windows NT 4.0 user accounts to Windows 2000 Active Directory accounts.
4. Deploy servers running Exchange to store mail data.
Exchange and DNS
DNS services used by Exchange 2000:
n Address Records.
n MX Records.
n SRV Records.
n Virtual namespace.
Exchange and ADC
n ADC – short for Active Directory Connector
n when upgrading existing servers running Exchange 5.5 to Exchange 2000, you must back up and verify the servers first
n Exchange 5.5 server running the ADC must be running Exchange 5.5 Service Pack 3 or later.
n You must install the ADC on Exchange 5.5 for bi-directional directory replication with Active Directory.
n note that the version of ADC that ships with Windows 2000 cannot replicate the Exchange names from the Exchange 5.5 directory to Active Directory.
Reference Books:
Exchange Server 2000 24seven -- by Jim McBee; Paperback
Mastering Microsoft Exchange Server 2000 -- by Barry Gerber; Paperback
Microsoft Exchange Server for Windows 2000: Planning, Design and Implementation
by Tony Redmond (Paperback)
Mastering Microsoft Exchange Server 2000
by Barry Gerber (Paperback)
MCSE Training Kit: Microsoft Exchange 2000 Server Design and Deployment
by Kay Unkroth, Microsoft Corporation (Editor) (Hardcover)
This study guide is developed by Michael Yu Chak Tin. He can be reached at Michael@examreview.net.