Title: Exchange Server 2003 Deployment Methodologies Upgrade, Migration, and Coexistence Charlie Chung Prog
1Exchange Server 2003 Deployment Methodologies
(Upgrade, Migration, and Coexistence)Charlie
ChungProgram ManagerExchange ServerMicrosoft
Corporation
2Agenda
- Interoperability with Microsoft Windows
- Microsoft Exchange and Windows support matrix
- Core deployment scenarios
- Exchange deployment tools
- Multiforest deployments
- System topologies
- Requirements
- Functionality
3Exchange Deployment VisionAffordable Solution
for Better Deployment and ROI/TCO
- Improve customer satisfaction with deployment
- Provide prescriptive deployment guidance for
customers - Give customers the ability to validate their
setup and have confidence to continue - Remove deployment blockers
4Compatibility MatrixInteroperability with
Windows Server
- Exchange Server fully supports Windows Server
2003 Active Directory environments. Customers
can use Exchange 5.5 SP3, Exchange 2000 SP2 and
SP3, and Exchange 2003 with Windows 2003 GCs and
DCs. - Exchange 2003 Server is the only version of
Exchange supported to be run on Windows Server
2003.
5Exchange and Windows 2003 Server
All these servers can coexist in the same topology
Windows 2003 GC/DC
Windows 2000 SP3 GC/DC
Exchange 2003 Windows 2003
Exchange 5.5 Windows NT 4
Exchange 5.5 Windows 2000
Exchange 2000 Windows 2000
Exchange 2003 Windows 2000
6Permissions Requirements
- Lower permissions (Full Administrator Group only)
to - Install / reinstall
- Upgrade
- /DisasterRecovery
- including cluster nodes!
- Still need org permissions for
- First server in the org
- First server in the domain
- First server in the Administrator Group
- Servers with an SRS
7Deploying Exchange Servers
- Exchange 5.5 to Exchange 2003
- The recommended route for customers with Exchange
5.5 servers to get to Exchange 2003 is to install
an Exchange 2003 server into the site and move
mailboxes
Windows 2003 GC/DC
Exchange 5.5 Windows 2000
Exchange 2003 Windows 2003
8Deploying Exchange Servers (2)
- Exchange 2000 to Exchange 2003
- The Exchange 2000 Server must be upgraded to
Exchange 2003 first. Then the operating system
can be upgraded.
- Must uninstall these features before upgrading
- Mobile Information Server (MIS)
- Instant Messaging
- Chat
9Upgrading Exchange 2000
- Must already have Exchange 2000 SP3
- Must already have Windows 2000 SP3
- After the upgrade to Exchange 2003, you can
upgrade to Windows 2003 if you want to - You do not have to reinstall anything
- MAD makes changes at startup
- IIS 6.0 Dedicated Application Mode
- Metabase modifications
- Remove any MIS components from the server
- MIS can still point at Exchange 2000 and Exchange
2003 servers for co-existence - EIM and ECS upgrade considerations
10Exchange Deployment ToolsCore Exchange
Deployment Scenarios
- Structured guidance
- Prescriptive guide to walk a customer through the
whole Exchange deployment process - Preparation tools
- Tools to scan topology and give recommendations
- Validation tools
- Tools to help the customer proactively identify
issues that will prevent the setup of Exchange
from completing - NetDiag/DCDiag linked through the Web
- Customers can now have confidence that Exchange
is set up correctly, and they can avoid issues
that would have required them to call PSS.
11Exchange Deployment Tools
12Tools Can Be Run From
- Active documentation
- Start the tools with the right parameters
- Step-by-step documentation
- Command-line tools
- ExDeploy /slt5.5 servergt /gcltgcgt /tltTest(s)gt
- Example
- Exdeploy /sExch55 /gcMyGC /tDSScopeScan
- Exdeploy /?
- Setup
- Runs a subset of tools
- Titanium Setup will not run if the tools have
never been run
13Command Line
- Individual tests and test groups
14ADC Dependencies
- Must verify the following
- Exchange 2000 post-SP3 ADC hotfix is required if
you want existing ADCs to run after Exchange 2003
ADC is installed (post-Beta 2) - All ADCs must be upgraded to the Exchange 2003
version before the first Exchange 2003 Server can
be installed - ADC and core schema files are exactly the same
15Post Installation EnhancementsHelping Customers
Enable Services
- Internet Mail Wizard
- Guides the user to connect Exchange to the
Internet - Provides checks to validate DNS
- Helps configure SMTP addresses
- Different fromthe SBS version
16Mailbox-Server MigrationsMove Mailbox
Improvements
- More reliable and robust
- Mailbox will not fail to move because of
corrupted messages - Increased performance
- The move is now multithreaded to move more
mailboxes at one time - Easier to schedule
- Cutoff time can be specified so that moves can be
scheduled off hours - It is now easier for customers to plan mailbox
migrations from Exchange 5.5 during off hours and
without an Administrator present
17Multiforest Deployment
- System topology
- Requirements
- Functionality
- Directory synchronization
- Mail flow
- Administration
- Additional Exchange features
18Multiforest System Architecture
Forest 1
Forest 2
MMS Server
Exchange Server
Exchange Server
19Multiforest System Topology
Hub/Spoke
Mesh
20Multiforest Server Requirements
- Microsoft Metadirectory Services (MMS) 3.0
- Configured by GAL Sync Tool
- Windows .NET Server
- Microsoft SQL Server or MSDE
- MSDE has a 4 GB limit
- Exchange
- Titanium schema in source and target forests
- Mail route to all target forests
- Active Directory
- Bridge of DNS namespace across forests
21Multiforest Functionality
- Directory synchronization
- Mail flow
- Administration
- Additional Exchange features
22Multiforest Functionality (2)
Forest 2 Exchange
Forest 1 Exchange
Worksheet
Worksheet
Forest 3 Exchange
Worksheet
Set up an MMS server in one of the forests
Get forest information from individual forest
administrators
MMS admin runs GAL Sync Tool and enters forest
data
Tool performs validation and generates MMS
config. files
Configuration files are imported into MMS
gtGALSync
Run synchronization with MMS
MMS Server
23Multiforest Functionality (3)
Forest 1 Exchange
Forest 2 Exchange
Worksheet
Worksheet
MMS Server
MMS Server
- Set up an MMS server in one or more of the
forests - Get forest information from forests containing
the GAL data that you are interested in - MMS administrator in your forest runs GAL Sync
Tool and enters forest data - Tool performs validation and generates MMS
configuration files - Configuration files are imported into MMS and
synchronization is started
24MMS 3.0 - GALSync
25Multiforest FunctionalityDirectory
Synchronization
- Contacts are synchronized on a per organization
unit basis - Group Membership is not synchronized
- Group Ownership cannot span forests
- Owner must be a mailbox in the same forest
- Group Management occurs on a per forest level
26Multiforest FunctionalityMail Flow
- Mail routing is configured on per forest level
- Foreign connector contacts will be routed through
the source forest - Forest can control routing of regular contacts
- Contacts are synchronized on a per organizational
unit basis
27Multiforest FunctionalityAdministration
- Exchange systems are managed on a per org level
- Policies must be created for each forest
- Move mailbox
- Completed through the Migration Wizard
- Reply ability maintained
- Investing how to reduce touch to client
- OST
- Profile
- Rules
28Multiforest FunctionalityAdditional Exchange
Features
- Free/busy
- Clients will be able to look up free/busy
information across forests with InterOrg Public
Folder Tool - Calendar details will not be available across
forests
29- Thank you for joining todays Microsoft Support
- WebCast.
- For information about all upcoming Support
WebCasts, - and access to the archived content (streaming
media - files, PowerPoint slides, and transcripts),
visit - http//support.microsoft.com/webcasts/
- Your feedback is sincerely appreciated. Please
send any - comments or suggestions about the Support
- WebCasts to supweb_at_microsoft.com.