Migrating to Exchange 2003 Rob Herman Sr. Technology Specialist Messaging and Collaboration Pac West District Microsoft Corporation.

Migrating to Exchange 2003 Rob Herman Sr. Technology Specialist Messaging and Collaboration Pac West District Microsoft Corporation

New and Upcoming Exchange Enhancements

Microsoft Exchange Intelligent Message Filter Leverages SmartScreen Technology Shipped in Outlook2003 Deployed at Hotmail Extension to Exchange2003 Server, deployed on Internet Bridgeheads Leverages the SCL infrastructure Coexistence with 3 rd party solutions Compliments but does not compete

Microsoft Exchange Intelligent Message Filter Supports per Message tagging Administration via Exchange System Manager Console extension Filter Updates http://www.microsoft.com/exchange/imf

Internet Port 25 Traffic E-mail Boundary Area SMTPRelay Filter Application Host E-mail Router (Logical or Physical)

The Edge Defined Exchange Mailbox Server Exchange Mailbox Server LOB Application User1 User2 Vendor X Messaging System The Physical Enterprise User3 Exchange Front-end Server Exchange Bridgehead Server Exchange System Internet Port 25 Traffic Perimeter Area SMTP Gateway Filter Application Host Email Router (Logical or Physical)

Exchange Server Roles Exchange Mailbox Server Exchange Mailbox Server LOB Application User1 User2 Vendor X Messaging System The Physical Enterprise User3 Exchange Front-end Server Exchange Bridgehead Server Exchange System Internet Port 25 Traffic Perimeter Area SMTP Gateway Filter Application Host Email Router (Logical or Physical) Edge Bridgehead Mailbox Front End

Exchange Edge Server Objectives  Re-factor SMTP Gateway Goal: Nail the basics Security Reliable, High Performance, Manageable Simple Deployment  Advance Extensibility Infrastructure Goal: Customer flexibility and partner value-add.NET Framework-based extensibility Rules system and editor interface Rich services API Enablement of community  Support Basic Customer Features Goal: Gain control of email flow in/out of the organization Anti-spam, anti-virus, attack management, content management, secure messaging

Migration Paths to Exchange 2003

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

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

 Understand and Cleanup 5.5 Environment  Fulfill Basic Network Requirements  Deploy and Prepare Active Directory  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

Exchange Deployment Tools Structured Guidance Prescriptive guide to walk a customer through the entire Exchange deployment. 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 the Exchange from completing. NetDiag/DCDiag linked through web Customers can now have confidence that Exchange is setup correctly and avoid issues which would have required them to call PSS. Core Exchange Deployment Scenarios

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

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

 Understand and Cleanup 5.5 Environment  Fulfill Basic Network Requirements  Deploy and Prepare Active Directory Extend Active Directory for Exchange Integrate 5.5 Directory and Active Directory  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 ( http://www.netiq.com ) http://www.netiq.com 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 ( http://www.aelita.com ) ** NOW QUEST ** http://www.aelita.com 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 Discus Data Solutions ( http://www.discusdata.com) ** NOW QUEST ** http://www.discusdata.com Wizard based migration of Mailbox Data, Directory, Access Control, Distribution Lists, Wingra ( http://www.wingra.com ) http://www.wingra.com 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 ( http://www.compusven.com ) http://www.compusven.com Migration tools for Exchange, Notes and GroupWise migrations GroupWise tools supports GroupWise 6 Email Shuttle can be scheduled for automatic migrations 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 YesNoYesYes Exchange 2000 SP2 YesNoYesYes Exchange 2000 SP3 YesNoYesYes Exchange 2003 Yes (W2K SP3) Yes 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 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 or 2000 SP3 – Post Fix 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

OWA – New Features It is not sufficient to simply upgrade front- end servers to Exchange 2003 for users to get the new interface You must upgrade back-end servers to Exchange 2003 as well Interface matrix Ex2000 FE + Ex2000 BE = Ex2000 OWA Ex2003 FE + Ex2000 BE = Ex2000 OWA Ex2000 FE + Ex2003 BE = Not supported (AG protected) Ex2003 FE + Ex2003 BE = Ex2003 OWA

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 2000 Upgrades Preparing for Exchange 2003

Outlook 2003 – RPC/HTTP Client-side Outlook 2003 Windows XP with Service Pack 1 + Q331320 (at RTM, this might change to Windows XP with SP2) Server-side Exchange 2003 on Windows 2003 for FE (if FE is deployed) Exchange 2003 on Windows 2003 for BE Exchange 2003 on Windows 2003 for Public Folders Exchange 2003 on Windows 2003 for System Folders Windows 2003 for Global Catalog server

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

New Deployment Paths

Site Consolidation Tools Site Consolidation Initially consolidating content from a remote site into a central site Moving Mailboxes, Public Folders, Distribution Lists, and Custom Recipients Then removing remote servers and 5.5 Sites (or) Admin Groups Why? Reduce TCO by having fewer servers and sites to manage Leverages Exchange/Outlook 2003 cached mode Scenario Goals #1 - Consolidate Remote Exchange 5.5 Sites Single Server as Primary Scenario #2 Mixed Exchange 5.5/Exchange 2000/2003 sites Non Goals Exchange 2000 Native Mode Already supported in native mode E2k Central Office Remote Office Exchange Site A Exchange Site B Remote Office Exchange Site C Site Consolidation Move Content Central Office Remote Office Exchange Site A Remote Office Exchange 2003 Outlook 2003

New SP1 Features Features: Step-by-Step Guide, Using the Deployment Tools Exchange Deployment Tools (Exdeploy.hta) Tools to move Mailboxes (And fix client experience) ESM for Moving mailboxes Exprofre.exe to update client profiles after move and preserve OST Core store update to fix rules after a move Tools to Move DLs/and Contacts: Exdeploy tool to update DLs/Contacts with new LEGDN of a new site Tools to Consolidate Public Folders: PFMigrate to move PFs to a central site. Non-Features: Tools to automate removal of servers/sites Tools to move or remove additional features at remote sites. (Foreign Connectors, KMS, OAB Generator, Conf Servers etc.)

Major Pre-Reqs for Site-Con Central Site Requirements E2k3 SP1 for all mailbox servers that will be used for moves (Required) E2k3 SP1 on at lease 1 PF server (Required) ADC All ADCs upgraded to E2k3 Sp1 and 2 Way CAs to every site (Required) 5.5 Requirements 5.5 DS/IS Patch on ALL 5.5 PF servers (Required) Outlook 2003 Remote sites with slow response will need OL2003 –w- cached mode installed BEFORE consolidation Bandwidth Recommended that Customers should have enough bandwidth to support full download for all outlook 2003 cached mode clients.

Areas to Be Aware 5.5 PF/Mailbox ACL Need to run Patched 5.5 DS/IS after moves to update 5.5 ACLs NDR after migration for Period of Time 5.5 users who reply to mail from a moved 5.5 user will NDR for 12 to 24 hours Workaround: Force ADC/5.5 replication/cleanup or reconfigure 5.5 routing to remote site to be through E2k BH to redirect mail Bandwidth for Outlook 2003 OAB Download at remote sites Need to ensure enough bandwidth for periodic full OAB downloads to remote clients Public Folder Migrations: PF Content should be in central site before mailbox moves to ensure mailboxes can continue to access PFs Remote Domain Consolidation Clients will be directed to by DSProxy to DCs/GCs in Exchange sites. User accounts should be in same domain to ensure that Delegate Access, Cert publishing can work

Other Areas worth mentioning General Outlook Issues: There are a number of minor known mailbox issues related to a mailbox move that will be documented Need to run Client Profile script after move (ExprofRe.exe) Other minor areas, V1 KMS Cert loss, etc. SRS: Can not remove a site that is the SRS for another Pure E2k/E2k3 Admin Group Network Bandwidth: Mailbox moves will be slow when performed across slow links Areas to Be Aware

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

Resources Exchange Server 2003 Deployment Guide www.microsoft.com/technet/prodtechnol/exchange/2003/library /depguide.mspx Exchange Intelligent Messaging Filter Overview: www.microsoft.com/exchange/techinfo/security/imfoverview.asp Exchange Edge Server Overview Exchange Edge Server Overview www.microsoft.com/exchange/techinfo/security/edgeservices.asp

Exchange 2003 MTAF: Features, Deployment Process, & Partner Experience Steve Bunda TECTURA Corporation

Agenda Management Features Client Features Mobility Features Deployment Process Guidelines Partner Experience

Exchange 2003 Management Compatibility Matrix Exchange Server fully supports Windows Server 2003 AD environments Exchange 5.5 SP3, Exchange 2000 SP2/SP3, and Exchange 2003 work with Windows 2003 Global Catalogs and Domain Controllers Exchange 2003 Server is the only version of Exchange supported on Windows Server 2003 Exchange 2000 Enterprise cannot be upgraded to Exchange 2003 Standard 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 2003 Management Standard vs. Enterprise Edition Feature Storage groups supported Databases per storage group Individual database size Clustering X.400 Connector Standard 1 2 16 GB No Not included Enterprise 4 5 16 terabytes Yes Included Both editions feature Network compression Exchange 2003 Management Pack Integrated support for mobile devices Volume Shadow Copy service Flexible configuration Recovery Storage Group

Exchange 2003 Management New Manageability Features Exchange System Manager Multiple Mailbox Move Mailbox Recovery Center improved Improved Error Reporting Public Folder Management Dynamic (Query-Based) Distribution Lists Volume Shadow Copy Service Recovery Storage Group (RSG) Anti-SPAM Improvements

Exchange 2003 Security Features Spam vs. Viruses VirusesJunk E-Mail Exploits Specific vulnerabilities (e.g. buffer overruns) General openness of of mail system Effects DestructiveNuisance, offensive Identification Signatures, deterministicVarious, often subjective Cost Data loss Productivity loss Helpdesk Administration System resources Bandwidth Productivity loss Helpdesk Administration System resources Bandwidth Exchange Solution Exchange infrastructure Anti-Virus plug-ins Exchange infrastructure Exchange features Anti-Spam plug-ins

Exchange 2003 Security Features Enterprise Requirements for Anti-Spam False positives are the #1 enterprise concern Valid mail in the junk folder is as good as lost Block at the gateway whenever possible User never sees it Reduces impact Administration End-to-end solutions Easy to manage Balance corporate and end-user control

Exchange 2003 Security Features Exchange 2003 Anti-Spam Connecting Filtering IP-based Global Allow and Deny lists Sender Filtering Messages from specific user or domain Messages with blank sender Verification of anonymous senders Recipient Filtering Messages sent to nonexistent recipients Allow only authenticated users to send to a DL

Exchange 2003 Security Features Exchange 2003 Antivirus New AV API 2.5 Antivirus can run on Exchange Servers that do not have resident mailboxes New support for antivirus features Delete messages Send messages back to sender

Exchange 2003 and Outlook 2003 Outlook 2003 Design Goals Arrangements Date, subject, conversation, etc. Keep track of important messages Easier interface for beginning users Provides quick access to information Ability to work offline

Exchange 2003 and Outlook 2003 Quick Flags Manage and prioritize messages Six different flag colors You decide what the colors represent You can assign reminders if you like Does not interrupt reading/triage process Flagged messages appear in “For Follow Up” folder

Exchange 2003 and Outlook 2003 Outlook 2003 Interface Right-hand view pane Quick flags Favorite folders Arrange by conversation Search Folders Quick navigation pane

Exchange 2003 and Outlook 2003 Search Folders Provides flexibility in organizing e-mail Live search that acts as a folder Scales to different levels of expertise Beginner: Out-of-the-box folders Intermediate: Search Folder templates Advanced: Any query you can imagine

Exchange 2003 and Outlook 2003 Outlook and Network Connectivity Prior versions of Outlook Assumes a perfect network Default mode is Online Offline mode helps but not enough Outlook remote synchronization CumbersomeSolutions: Cached Exchange Mode RPC over HTTP

Exchange 2003 Security Features Outlook 2003 Security and Privacy

Mobile Client Options

Mobile Client

Exchange 2003 and Outlook 2003 Cached Exchange Mode Improved Synchronization Handles connectivity changes Bandwidth-conscious Handles Power State Transitions Conflict resolution

Exchange 2003 and Outlook 2003 PST / OST Enhancements Unicode support has been added to the stores Outlook will use Unicode if the server supports it OST – offline or cached mode PST – auto-archive Existing OST/PSTs will not be upgraded New size limit on OST/PST (>100 GB) Default size is 10 GB and can be controlled by the admin via policy See PSS 830336

Mobile Client

Outlook Web and Mobile Access Outlook Web Access HTML version of Outlook 2003! Features requested from Outlook 2002 Spell check, tasks, rules, mark read/unread New features from Outlook 2003 Quick flag support, reading pane, etc.

Outlook Web and Mobile Access Outlook Mobile Access (OMA) Outlook Web Access for mobile devices The ‘device reach’ solution in Exchange’s mobile strategy Generates different markup for different devices Updates through.Net Framework ‘Device Update’ Complete rewrite from Mobile Information Server 2002 Built on.Net Framework Mobile Controls Any device with a browser can use the application

Outlook Web and Mobile Access OMA Features Triage E-Mail Send, reply, forward, etc. Find People Search GAL, establish calls, send e-mail, etc. Calendar Manage meetings and appointments Tasks Update, mark as complete, etc. Contacts Add to Contacts from GAL

Outlook Web and Mobile Access Exchange Up-to-Date Notifications Control message designed to “wake-up” an Exchange ActiveSync capable device Always-On, Always-Up-To-Date End user value: Better utilization of device resources User experience consistent with device expectations Background operation

Exchange 2003 Security Features OWA Security and Privacy Supports Secure MIME (S/MIME) Allows encryption and digital signature Junk e-mail and sender filters Similar to Outlook 2003 Automatic logoff Inactivity time-out automatically closes session Attachment Blocking

Exchange 2003 and Outlook 2003 Outlook 2003 Feature Requirements Outlook 2003 FeatureExchange 2003Exchange 2000Exchange 5.5 Cached Mode with Full Item SyncYes Cached Mode with Drizzle SyncYesNo Cached Mode with Header SyncYesNo Send/Receive Header SyncYesNo Send/Receive Conditional Full Item SyncYesNo Improved Sync ProgressYesNo Partial Item UploadYesNo Automatic Conflict ResolutionYes ISC Check PointingYesNo Skip Bad ItemYes No Best Body SupportYesNo RPC CompressionYesNo Buffer PackingYesNo RPC/HTTPYesNo Kerberos AuthenticationYesNo Performance TrackingYesNo LIFOYesNo Connection ThrottlingYesNo Unicode SupportYesNo Integration with VS API 2.5YesNo

Mobile Client - RPC/HTTP 2003 Required: Windows Server 2003, Exchange 2003 & Outlook 2003

Exchange 2003 and Outlook 2003 RPC/HTTP Topologies Internet RPC over HTTP ISA Server Exchange 2003 RPC Proxy Server Domain Controllers Global Catalog Server Exchange 2003 Server

Internet Exchange 2003 and Outlook 2003 RPC/HTTP Topologies RPC over HTTP Front-end Proxy Server Exchange 2003 Server Domain Controllers Global Catalog Server

Feature Summary New Exchange 2003 management features Outlook 2003 features Outlook Web Access and Outlook Mobile Access Exchange anti-spam and antivirus RPC/HTTP Outlook 2003 and Exchange 2003 are better together

Agenda Management Features Client Features Mobility Features BREAK 10 Minutes Deployment Process Guidelines Partner Experience

Deployment Considerations NT4.0 Domain Model vs. Active Directory AD Win2k vs. AD Windows Server 2003 Forest & Domain Design Exchange 5.5 Outlook Web Access Bridgehead Server(s) Firewall, DMZ Mail Client Administrative Model Identify desired features of Exchange 2003

Domain Model What is the current domain model? AD Forest? AD domains? NT domain(s) Native or Mixed? Windows Server 2003 Active Directory? If Yes, are you native mode? If No, what is preventing the migration? Determine best path

Assess Current Mail Environment How important is email to your organization? Are you running Exchange now? What stores are in use? (Pub, Priv) Is there a bridgehead? Do you use OWA now? Define the relationship between users and mailboxes Define Exchange Management Practices within the organization Identify current anti-spam tactics Identify current anti-virus Are there any pre-existing mail-related issues?

Assess Network Infrastructure Define the network routing strategy Is a firewall in place? What functions are performed by the firewall? Is there a DMZ? How might OWA fit into this strategy?

Plan The Migration Process Diagram the Exchange environment (mailbox stores, public folder stores, bridgeheads, OWA, GC’s, DC’s) Involve an Active Directory engineer Map out the alternative paths Will new hardware be deployed? Is an “upgrade” acceptable? Estimate hardware, software and services required to complete each alternative Associate risks with each alternative Determine the best path for your organization

Preview Exchange 2003 Process Understand forestprep & domainprep Use Support Tools to perform a health check on the environment Cross-domain limitations Deployment logs PFMigrate Utility Identify quantities of Standard and Enterprise required for your deployment Determine which servers get migrated first

Deployment Example Exchange 5.5 -> Exchange 2003 WS03 Native Mode Active Directory OWA on dedicated Windows 2000 Server Single Exchange 5.5 Server Mailboxes Public Folders Outlook 2003 is NOT deployed

Example Migration Join the 5.5 Org and Site

Example Migration Set as a Front-end Server Remove Win2K OWA Server Set HTTP Redirect or change IP address Open Firewall

Example Migration Migrate - Public Folders - Mailboxes - System Objects - Connectors REMOVE 5.5

Example Migration Migration Complete

Example Migration

Deployment Scenarios Migrations from 5.5 Backend Server Only Front End (OWA) and Back End Server DMZ with Watchguard, PIX, MS ISA SMTP connector to FE or BE Fax Connectors Small Business Server Migration from NT4/E5.5 20- to 30- day migration plans NT4-to-WS03 and E5.5-to-ES03 in 3 days New hardware Leap Frog hardware WS03 and Win2K domains WS03 and Win2K servers

Real Issues Determining the ports to open between the Front-end and the Internal network is complex. NTDS NoMatch can be difficult to manage in some environments Pre-existing network and Exchange issues will cause problems during migration Large mail queues NDR SPAM DNS problems Poorly placed GC’s Public Folders don’t always replicate immediately Outlook 2003 will break 5.5 OWA A well-thought, detailed migration plan is critical Firewall management knowledge is helpful Mailbox size limits should be set AFTER migration Migrate bridgehead servers first Web-based mail-generation can be affected Every technician has a different recommendation Exchange Training is often overlooked

Recommendations Identify your short- and long-term goals Migrate to Windows Server 2003 & AD Plan the Exchange Migration in detail Workshop Obtain new hardware Enterprise Exchange on the Back End Standard Exchange on the Front End Research your firewall Review the Exchange 2003 Tools Schedule Exchange Administration Training (e.g. Netdesk)

TECTURA Corporation Integration MS BizTalk Business Intelligence MS SQL Workflow Infrastructure Active Directory, Exchange.NET Architecture

Contact Information Steve Bunda TECTURA Corporation Bellevue, WA 425-957-4258 sbunda@tectura.com

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

Preparing for Exchange 2003 Preparing the Windows Active Directory - Extend the Schema for Exchange 2003 - Get forest ready for Exchange - Get each domain ready

ForestPrep Allows delegation of installation tasks that require Enterprise and Schema Admin permissions Extends the Active Directory Schema Creates the Org container and the global containers underneath it Only needs to be run once per Forest Creates the Exchange Organization Placeholder Org until first server install Nominates the first full Exchange 2003 Administrator

ForestPrep Requirements Must be run in the same domain as the Schema Master Required Permissions Enterprise Admin Schema Admin If joining a 5.5 Org this account must also have Admin perms in the 5.5 site Run from the Deployment Tools!!!

DomainPrep Allows delegation of installation tasks that require DomainAdmin perms Needs to be run once in each domain where Exchange 2003 will be installed Exchange 2003 recipients exist users / contacts / groups / public folders Setup /domainprep

DomainPrep Requirements Installing account must have Domain Admin perms for the domain being DomainPrep’d ForestPrep was run and information is replicated to the domain Domain admin does not need to know anything about the current Exchange environment Run from the Deployment Tools!!!

Validating Exchange Updates to AD OrgPrepCheckOrgCheck Validates schema extensions Proper Domain groups created and populated Ensures correct permissions applied Validates Exchange container is created Checks GC PolCheck Checks Manage auditing and security logs permission on all DCs in domain

Migrating to Exchange 2003 Rob Herman Sr. Technology Specialist Messaging and Collaboration Pac West District Microsoft Corporation.

Similar presentations

Presentation on theme: "Migrating to Exchange 2003 Rob Herman Sr. Technology Specialist Messaging and Collaboration Pac West District Microsoft Corporation."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Migrating to Exchange 2003 Rob Herman Sr. Technology Specialist Messaging and Collaboration Pac West District Microsoft Corporation.

Similar presentations

Presentation on theme: "Migrating to Exchange 2003 Rob Herman Sr. Technology Specialist Messaging and Collaboration Pac West District Microsoft Corporation."— Presentation transcript:

Similar presentations

About project

Feedback