MSG302 Deploying Exchange Server Overview Sasa Juratovic Consultant Microsoft Ltd

Exchange Deployment Vision “Affordable Solution for Better Deployment and ROI/TCO” Improve customer satisfaction with deployment Provide prescriptive deployment guidance for customers Give customers ability to validate their setup and have confidence to continue Remove deployment blockers

The Paths To Exchange 2003 Path 1 – Standard Deployment from Exchange 5.5 Deploy Exchange 2003 INTO an existing Exchange 5.5 environment Path 2 – Exchange 5.5 as an External Migration Deploy Exchange 2003 as separate and external system from Exchange 5.5 Path 3 – Exchange 2000 Upgrades High Level Overview of Process and Tools

The Different Topologies Single Forest – Single Exchange 2003 Standard topology, and deployment case Central IT provides Exchange AND Network services Deployment through upgrade/migration of 5.5, or from consolidations of organizations Multiple Forests – Single Exchange 2003 (Exchange Resource Forest) Good for un-trusted or distributed organizations where Central IT only provides Exchange services Deployment through upgrade, migration, or consolidations but network accounts remain in a different forest Multiple Forests – Multiple Exchange 2003 Good for highly autonomous distributed business units Central IT only provides a shared directory service

External Forest -w- E2k SMTP - Mail MMS – Directory PF Repl – F/B XYZ.comForest External Forest or NT4 Domain External Accounts -w/o- E2k Domain Trusts

Recommended Tech-Ed Sessions MSG307 Exploring Topologies for Exchange Server Detailed description of Exchange topologies Different Topologies Additional Information

Path 1 – Standard Exchange 5.5 Deployment Path

Exchange 2003 is Deployed INTO existing Exchange 5.5 Org Exchange 2003 coexists natively with Exchange 5.5 System Configuration is inherited by Exchange 2003 servers Mailboxes are moved to new Exchange 2003 servers Who: Most Exchange 5.5 environments Exchange 5.5 customers with working/stable structure Mixed Mode Exchange 5.5 and Exchange 2000 customers Benefits: Does not require/need a major re-structure Core path = Core tools Lowest administrative and client deployment costs Preserve 100% of 5.5 organization and data Standard Deployment Path Deploy Exchange 2003 Into Exchange 5.5 Org

Standard Deployment Path The path 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 Deploy Exchange 2003 Into Exchange 5.5 Org Exchange 2003 Windows 2003 Exchange 5.5 Windows 2000 Exchange Org

1. Understand and Cleanup 5.5 Environment 2. Fulfill Basic Network Requirements 3. Deploy and Prepare Active Directory 4. Fulfill Basic Server Requirements Tools to help prepare for Exchange 2003 Deployment Tools ** NEW ** Active Directory Connector (ADC) ADC Tools ** NEW ** Exchange Technical Library ** NEW ** Standard Deployment Path Preparing for Exchange 2003

1. Understand and Cleanup 5.5 Environment 2. Fulfill Basic Network Requirements 3. Deploy and Prepare Active Directory 4. Fulfill Basic Server Requirements Tools to help prepare for Exchange 2003 Deployment Tools ** NEW ** Active Directory Connector (ADC) ADC Tools ** NEW ** Exchange Technical Library ** NEW ** Standard Deployment Path Preparing for Exchange 2003

Basic Active Directory Deployment is Required Must have Windows 2000 SP3 Domain Controllers and Global Catalogs (OR) Windows 2003 Active Directory Deploying Exchange 2003 With Accounts in NT4 Domains or External Forests Exchange 2003 will work with accounts in a Windows NT 4 domains or external forests Exchange uses “Placeholder Accounts” in the Active Directory that reference external accounts “Placeholder Accounts” are automatically created during deployment process Standard Deployment Path Deploy the Active Directory

Extend Active Directory for Exchange Forest Prep – To prepare forest for Exchange Domain Prep – To prepare each domain for Exchange Integrate Exchange 5.5 Into Active Directory Deploy the Active Directory Connector Replicates 5.5 information with Active Directory ADC Tools (New with Exchange 2003) Data Collection and Validation Resource Mailbox Wizard Connection Agreement Wizard Standard Deployment Path Prepare the Active Directory for Exchange

Extend Active Directory for Exchange Forest Prep – To prepare forest for Exchange Domain Prep – To prepare each domain for Exchange Integrate Exchange 5.5 Into Active Directory Deploy the Active Directory Connector Replicates 5.5 information with Active Directory ADC Tools (New with Exchange 2003) Data Collection and Validation Resource Mailbox Wizard Connection Agreement Wizard Standard Deployment Path Prepare the Active Directory for Exchange

Install Initial Exchange 2003 Server into a 5.5 Site Initial Exchange services are created with first server to support deployments Exchange 2003 will now inherit the same organization as 5.5 at this point Move Content to Exchange 2003 servers Move mailboxes with Exchange Admin NEW – Schedule moves NEW – Better performance and reliability Replicate public folder content NEW – PF-migrate tool Reconfigure any connectors or special server rolls Deploy New Features Front end servers (For OWA, and OMA) Standard Deployment Path Deploying Exchange 2003

Install Initial Exchange 2003 Server into a 5.5 Site Initial Exchange services are created with first server to support deployments Exchange 2003 will now inherit the same organization as 5.5 at this point Move Content to Exchange 2003 servers Move mailboxes with Exchange Admin NEW – Schedule moves NEW – Better performance and reliability Replicate public folder content NEW – PF-migrate tool Reconfigure any connectors or special server rolls Deploy New Features Front end servers (For OWA, and OMA) Standard Deployment Path Deploying Exchange 2003

Path 2 – Exchange 5.5 as an External Migration

Exchange 2003 is Deployed as NEW and External Organization No configuration is preserved from Exchange 5.5 Mailboxes are selectively migrated between old and new system Coexistence is optional but requires additional steps to setup May require third party tools for migration of additional data Who: Some Exchange 5.5 Environments Multiple Exchange 5.5 Organizations Major topology change needed Why Not? Higher cost for migration by both administration and clients Need to preserve 100% of Exchange 5.5 Environment External Migration Path Deploy Exchange 2003 as an External Organization

Windows 2003 GC/DC Exchange 2003 Windows 2003 Exchange 2003 Org External Migration Path Deploy Exchange 2003 as an External Organization An External Migration is where Exchange 2003 is installed in a NEW/External Exchange organization. Selective mailboxes are migrated to Exchange. Exchange 5.5 Windows 2000 Exchange 5.5 Org

1. Understand and Cleanup 5.5 Environment 2. Fulfill Basic Network Requirements 3. Deploy and Prepare Active Directory Extend Active Directory for Exchange Integrate 5.5 Directory and Active Directory 4. Fulfill Basic Server Requirements Tools to help prepare for Exchange 2003 Deployment Tools ** NEW ** Exchange Technical Library ** NEW ** External Migration Path Preparing for Exchange 2003

Deploy Exchange 2003 Org Use Deployment Tools to start Setup DO NOT join a 5.5 organization Setup Connectors, Front-Ends, Etc. Setup Coexistence (Optional Extra Steps) Directory Coexistence Use ADC Inter-Org Mode to create contacts in an Active Directory DO NOT use ADC Tools Messaging/Calendaring Coexistence Setup SMTP Connectors between orgs Free/Busy and Public Folder Coexistence Deploy Inter-Org Public Folder Replication Tool External Migration Path Deploy Exchange 2003 and Setup Coexistence

Mailbox Migration Exchange 2003 Migration Wizard, Installed with Exchange General migration tool for migration of mailboxes from external systems (Exchange, Notes, GroupWise, etc.) Migrates mailbox content and mailbox directory information If directory co-existence is in place, reply-ability will be preserved Additional Manual Tasks for Migration Cleanup of mailboxes after migration Client tasks to reset outlook profile, fix rules and reset delegates External Migration Path External Migration of Data

Public Folder Migration Content can be replicated during coexistence Specific Public Folder Permissions need to be re- created Additional Directory Content Migration Contacts: Can be replicated during coexistence Distribution Lists: Need to be manually exported/imported into Active Directory External Migration Path External Migration of Data

NetIQ’s Exchange Migrator ( ) Exchange 5.5 Migrations Includes Mailbox Data, Public Folder Data, Access Control, Distribution Lists, Manager/Reports links Combined domain and mailbox migration solution Aelita Controlled Migration Suite ( ) Exchange 5.5 Migration and Coexistence tools Service based migration (For off-hour migrations) Mailbox Data, Public Folder Data, Directory Migration Combined domain and mailbox solution Wingra ( ) Consulting and Migration tools for Exchange, Notes and GroupWise migrations GroupWise tools support GroupWise 6 Exchange tools migrates mailbox, Access Control, Distribution Lists, and Public Folders Compusven ( ) Migration tools for Exchange, Notes and GroupWise migrations GroupWise tools supports GroupWise 6 Shuttle can be scheduled for automatic migrations Discus Data Solutions ( Wizard based migration of Mailbox Data, Directory, Access Control, Distribution Lists, External Migration Path Some Third Party Tools

Path 3 – Upgrade from Exchange 2000

Exchange 2003 is deployed into an organization where Exchange 2000 has already exists Exchange 2003, Exchange 2000 and Exchange 5.5 can coexist in the same organization Configuration will be shared same as a standard deployment Exchange 2000 servers can be directly upgraded to Exchange 2003 Mailboxes on 5.5 can be moved to Exchange 2003, same as standard deployment May consider consolidation during deployment Who: All Exchange 2000 Environments Mixed Exchange 2000 and 5.5 Organizations Pure Exchange 2000 organizations Benefits Start taking advantage of Exchange 2003 features OWA, OMA, Consolidation, Admin Features, etc. Exchange 2000 Upgrades Deploy Exchange 2003 after an Exchange 2000 deployment has started

Deploy Exchange 2003 an Exchange 2000 org Deploy Exchange 2003 into an organization where Exchange 2000 is installed OR upgrade an Exchange 2000 server Exchange 2000 Upgrades Windows 2003 GC/DC Exchange 2000 Windows 2000 Exchange 5.5 Windows 2000 Exchange Org Exchange 2003 Windows 2003

Deploy Exchange 2003 an Exchange 2000 org Deploy Exchange 2003 into an organization where Exchange 2000 is installed OR upgrade an Exchange 2000 server Exchange 2000 Upgrades Windows 2003 GC/DC Exchange 2003 Windows 2000 Exchange 5.5 Windows 2000 Exchange Org Exchange 2003 Windows 2003

Compatibility Matrix Interoperability with Windows Server Exchange Server fully supports Windows Server 2003 AD environments. Customers can use Exchange 5.5 SP3, Exchange 2000 SP2/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 Exchange can be installed and run on Supported Active Directory Environments Exchange Version Windows Server 2000 Windows Server 2003 Windows Server 2000 Windows Server 2003 Exchange 5.5 SP3 YesNoYes Exchange 2000 SP2 YesNoYes Exchange 2000 SP3 YesNoYes Exchange 2003 Yes (W2K SP3)YesYes (W2K SP3)Yes

Exchange And Windows 2003 Server Exchange 5.5 Windows 2000 Exchange 2000 Windows 2000 Windows 2003 GC/DC Windows 2000 SP3 GC/DC Exchange 2003 Windows 2000 SP3 Exchange 2003 Windows 2003 Exchange 5.5 NT4 All of these servers can coexist in the same topology.

Prepare Active Directory for Upgrade Upgrade all ADCs to Exchange 2003 Upgrade Active Directory to have at least one Windows 2000 SP3 DC, or Windows 2003 DC in each site Prepare Forest with Forest Prep Extends Schema Prepare each domain with Domain Prep Updates domain permissions for Exchange 2003 Prepare servers for Upgrade New software requirements Windows 2000 SP3 or Windows 2003.Net Framework and ASP.NET Exchange 2000 Upgrades Preparing for Exchange 2003

Consider Legacy Components Features that are no part of default Exchange 2003 Instant Messaging and Chat Service  Microsoft RTC Key Management Service (KMS)  Windows Certs Consider New Security Features (Secure by Default) Services not installed by default, and permissions on Exchange servers Exchange Server 2003 Security Enhancements Exchange 2000 Upgrades Preparing for Exchange 2003

Installing New Servers Run Setup and join existing organization Can be new front end or back-end servers Upgrade Front End Servers Use Deployment Tools to Upgrade Must upgrade front-end servers first AND must upgrade back-end servers before new OWA and OMA features are exposed Upgrading Exchange 2000 and back-end servers Use Deployment Tools to upgrade Consolidating on Exchange 2003 Move mailboxes using NEW Exchange 2003 admin Move mailbox within same Admin group if 5.5 servers exist or between admin groups if in native mode Exchange 2000 Upgrades Deploying Exchange 2003

The Paths To Exchange 2003 Path 1 – Standard Deployment from Exchange 5.5 Deploy Exchange 2003 INTO an existing Exchange 5.5 environment Path 2 – Exchange 5.5 as an External Migration Deploy Exchange 2003 as separate and external system from Exchange 5.5 Path 3 – Exchange 2000 Upgrades High Level Overview of Process and Tools

Questions…

Ask The Experts Get Your Questions Answered I will be available in Ask the Experts area tomorrow at 11:15 for 2 hours

Community Resources Most Valuable Professional (MVP) Newsgroups Converse online with Microsoft Newsgroups, including Worldwide User Groups Meet and learn with your peers

Suggested Reading And Resources The tools you need to put technology to work! TITLE Available Microsoft® Exchange Server 2003 Administrator's Companion: /24/03 Active Directory® for Microsoft® Windows® Server 2003 Technical Reference: Today Microsoft Press books are 20% off at the TechEd Bookstore Also buy any TWO Microsoft Press books and get a FREE T-Shirt

evaluations evaluations

© 2003 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.