Exchange Migrations don't have to be painfull - PowerPoint Presentation

Slide1
Slide2

Exchange Migrations don't have to be painfull

Nicolas BlankExchange MVPBlankmanblog.spaces.live.comSymbiotechUNC313

Michael Hutchinson

Quest

Product Manager

Blue Turtle TechnologiesSlide3

Session Objectives And Takeaways

Migration and Transition PlanningTransition Technical RoadmapMigration Technical RoadmapMigration Logistical Planning“Big Bang” MigrationsTool based migrationsSlide4

Why would a customer migrate?They have Exchange 5.5 or Exchange 2000/2003They have GroupWise or NotesComplex source organization

Incorrect configuration in the source organizationMerger or acquisitionCompany split or selloffSlide5

Migration PlanningTransition versus migration

TransitionIntra-org migrationSource: Exchange 2000, 2003, 2007Same Exchange OrganizationSame Active Directory ForestMigrationInter-org migrationSource: Any messaging platform

Different Exchange Organization

Active Directory Forest?Slide6

Transition Planning

Deploy Exchange 2007 into 2000/2003 orgOnly to “native mode” 2000/2003 orgsNo loss of functionality in 2007 while Exchange 2000/2003 presentOnce last 2000/2003 server is removed properly, cannot reintroduce 2000/20032000/2003 functionality not presentRUSGroupwise connectorX.400 connectorSlide7

Transition Planning

Run pre-req checksExBPA (Exchange 2007 Readiness test)DCs with Windows Server 2003 SP1 (or later) req’d forDomains containing Exchange 2007 serversDomains containing user objects to be mailbox enabled

Running Exchange SETUP for schema/domain prep

Can be run from a 32 or 64 bit DC with appropriate version of media

Same domain/same AD site as Schema MasterSlide8

Transition Planning

setup /PrepareLegacyExchangePermissionsAdds permissions back to the Exchange-Information property set to the EES groupNot required to run in same domain/site as Schema Master for the forestCan specify a single domain to execute in, if not, must be able to contact all domains in the forestSlide9

Transition PlanningSetup /PrepareSchema

, /PrepareAD, /PrepareDomainsetup /PrepareSchema

Not supported to use LDIFDE to import Schema

Can disable outbound replication to check for success after completing the schema upgrade

setup /

PrepareAD

Assigns permissions in the

config

partition

Creates Microsoft Exchange Security Groups OU

Creates USGs (Exchange Org

Admins

, etc…)

setup /

PrepareDomain

or /

PrepareAllDomains

Not required in single domain forest, /

PrepareAD

automatically prepares the domain it is executed inSlide10

Transition PlanningExchange 200x/2007 Routing

All Exchange 2007 servers are within a single routing group Routing Group Name: DWBGZMFD01QNBJRIntroduction of first Exchange 2007 Hub role results in creation of routing group connectors (single source/target bridgehead on each)Add source and target bridgehead servers for fault tolerance and load balancing between these two connected routing groupsExchange 2003 RGC bridgehead cannot be a cluster!Slide11

Transition PlanningDisabling Link State

Suppresses communication of minor link state changes (link up or down)Used when you have multiple routes to/from the Exchange 2007 Routing GroupMust be done to every Exchange 200x server in the organization to prevent loopsAll versions only use least cost routeControlled via registryHKLM\System\CurrentControlSet

\Services\

RESvc

\Parameters

DWORD:

SuppressStateChanges

Value: 1Slide12

Transition PlanningRouting and Connectors

RestrictionsExchange 2003: Content Restrictions, Priorities, System/Non-System Messages, Message Size RestrictionsExchange 2007: All E2003 Restriction, other than Size and PF Referrals, are ignored

 This may cause message loops

 Remove legacy E2003 restrictions

Routing

Messages are kept within the E2007 Routing Group as long as possible

Direct connections, smart bifurcation, back-off apply for legacy recipients as long as the next hop is Exchange 2007

Once a message it is routed to a legacy RG, then E2003 rules applySlide13

Routing Logs RoutingView

Replaces Winroute in E200xAllows to read and compare Routing LogsSlide14

Transition PlanningAccepted Domains

Enabled SMTP proxies automatically added@test1.localDisabled SMTP proxies not added@test2.localSlide15

Transition PlanningActiveSync –

2003/2007During co-existence CAS publishes E2003 mailboxesExchange 2007 CAS uses integrated authentication when accessing EAS on E2003 server (NTLM)Changing the authentication method in the IIS manager may be overwritten by DS2MB: Do not change in IIS managerInstead: Install KB937031 hotfix

on each Exchange 2003 backend server

or:

Use ADSIEDIT and change:

CN=Microsoft-Server-

ActiveSync,CN

=1,CN=HTTP,CN=

Protocols,CN

=<server Name>,CN=

Servers,CN

=<AG name>,CN=Administrative

Groups,CN

=<Org Name>,CN=Microsoft

Exchange,CN

=

Services,CN

=

Configuration,DC

=

domain,DC

=com

msExchAuthenticationFlags

to 6Slide16

Transition PlanningOffline Address Book

Replicate OAB from 2003 PF to 2007 PFSpecify a 2007 MBX server to generate OABOnce moved, can no longer manage from 2003Set polling interval on CAS servers for OABDefault is every 8 hoursLong time for cached mode clientsReplicates via Exchange File Distribution ServiceSlide17

Transition PlanningOffline Address Book - Clustering

OAB on SCC and CCR on Windows 2008Generating the OAB causes an exceptionOAB fails to generate (error 9334 and 9109)OAB attempts recreate – cluster returns incorrect error codeFixWindows Hotfix: http://support.microsoft.com/?id=955733

Exchange Rollup Update 5 (or later)

Additional Details:

http://blogs.msdn.com/dgoldman/archive/2008/12/11/fix-for-oab-generation-failing-on-ccr-and-scc-clusters.aspxSlide18

Transition PlanningOffline Address Book

TransitionsNeed to move OAB to Exchange 2007Need to update it to v4Use OABInteghttp://code.msdn.microsoft.com/oabintegKB article describing

http://support.microsoft.com/kb/907792

Troubleshooting with

OABinteg

http://blogs.msdn.com/dgoldman/archive/2005/08/28/oabinteg-and-how-to-use-it-to-troubleshoot-oab-generation-issues.aspx

alue: 1Slide19

Transition PlanningPublic and System Folders

Replicate system folders from 2003 to 2007 PF servers:Offline Address BookSchedule+Free/BusyOrganizational Forms LibraryReplicate public folders from 2003 to 2007 PF servers Use PFDAVADMINSlide20

Transition PlanningMailbox Manager - 2003

Recipient Policies with Mailbox Manager onlyDelete and recreate functionality with MRMRecipient Policies with both Mailbox Mgr and Email AddressesRemove Mailbox Manager settingsUse ManagedDefaultFolders for MM settings in 2007

All recipient policies should be Email Addresses ONLY before converting LDAP to OPATH filtersSlide21

Transition PlanningUpgrade LDAP to OPATH

Need to migrateRecipient Policies (email addresses, not mailbox manager)Address ListsDynamic Distribution ListsYou cannot manage an Exchange 200x e-mail address policy by using EMC until:Update the object's version and change the recipient filter by using either the RecipientFilter

or the

IncludedRecipients

parameters.

Script to convert LDAP to OPATH

http://msexchangeteam.com/archive/2007/03/12/436983.aspx

Additional Information:

http://msexchangeteam.com/archive/2007/01/11/432158.aspx

http://technet.microsoft.com/en-us/library/cc164375(EXCHG.80).aspx?info=EXLINK

http://technet.microsoft.com/en-us/library/cc164351(EXCHG.80).aspx

http://technet.microsoft.com/en-us/library/bb124517(EXCHG.80).aspx?wt.svl=upgradingSlide22

Transition PlanningRemove Last Exchange 2003 Server

Move the PF hierarchy to Exchange Administrative Group (FYDIBOHF23SPDLT)Create a new PF container in 2007 AGDrag the PF tree to the 2007 AGRemove all RGCs to 2007 from 2003Remove all recipient policies in 2003Remove all recipient update servicesEnterprise RUS remove via ADSI

Uninstall the last Exchange 2003 server

Note: wait until all pre Outlook 2007 clients (no

autodiscover

) have been redirected after their mailbox movesSlide23

Transition PlanningRemove Last Exchange 2003 Server

After the last Exchange 200x server has been removed from the Exchange 2007 organizationRemove Write DACL inherit (group) right for the Exchange Servers group from the root of the domainRemove-ADPermission "dc=<Domain>" -user "<RootDomain>\Exchange Servers" -AccessRights

WriteDACL

-

InheritedObjectType

Group

Remove the legacy Exchange Domain Servers and Exchange Enterprise Servers security groups

Validate groups are empty before removing them

Technet

Link

http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspxSlide24

Migration PlanningLogistics and Project PlanningSlide25

Migration PlanningLogistics

“Big Bang” Migrations – How to Plan?Iterative Approach250 -> 500 -> 1000 -> 2500 -> 5000Have seen up to 20,000 per weekend possibleDepends on data rate, seen up to 10GB per hour under perfect conditions. Typical is between 3-5 GB per hour, good starting estimate is 1 GB per hour

Require extensive planning

Scale up slowly – pilot “Waves”

Understand bottlenecks

Level set expectations

LogisticsSlide26

Migration Planning"Big Bang" Scalability Factors

Target Server CapacityData Throughput

Data Scope

Transaction Log Volumes

User Training

Cached Mode!

Floor Support

Help Desk

Archiving Solution

Backup / OLM Window

Resource Mailboxes

Client Configuration

Valid Pilot

Network Layout/Throughput

RIM BlackBerry

VIP User Scenarios

LogisticsSlide27

Migration Planning"Big Bang" - Post Move

Free / BusyDefault – check permissionsClient version – different free/busy returned (PF

vs

EWS)

EWS is real-time/PF is replicated could be old

Cross Forest – configure remote domains

Out of Office

BES and legacy clients only change one OOF template

OLK/OWA provide two (internal/external)

Cross Forest Move

Move mailbox but not AD/machine acct = BAD

SIDhistory

/

LegacyExchangeDN

OLK clients pointing to GC in

Exch

forest

LogisticsSlide28

Migration PlanningData Migration

Data Approach – Native toolsTools average 1-10/GB hour throughputFactors that influence speed:Health of source servers and databasesNetwork links for source/mig/target Multiple migration consolesScope of data to be migrated (all, contacts/calendar, previous week of mail?)

Target clients

Cached mode? 10k clients sync on Monday?

Stage cached mode, use online mode

LogisticsSlide29

Migration PlanningWindows 2003 -> 2008

No in-place upgrades from 2003 -> 2008 for Exchange 2007 serversCannot use SCR between 2003 -> 2008 serversCannot have 2003/2008 mixed clustersRequiresMailbox movesDatabase portability

LogisticsSlide30

Migration PlanningCoexistence planning

Mail FlowSlide31

Migration PlanningMail flow

Plan carefully! Mistakes here will be visible to the outside worldNeed to determine inbound, outbound, and internal mail routing scenariosSome coexistence tools have limitations Notes and Groupwise both have technical limitations

Connector feature deprecation between 2003/2007

Requires planning for

Source System

Target System

Hygiene Systems

Internal Relay Systems

Mail FlowSlide32

Exchange 5.5 Migration to Exchange 2007...Slide33

Groupwise

Migration to Exchange 2007 and Beyond...Slide34

Notes Migration to SharePointSlide35

35

Quest Solutions for Migrating to BPOSOverview

Migrate from Notes and GroupWise to Exchange Online Standard

Migrate from Notes, SharePoint 03/07, file shares and Exchange public folders to SharePoint Online Dedicated

Migrate from Lotus Sametime to Office Communications Online (Coming, but TBD)Slide36

Migration PlanningMail flow

Scenario: Shared external namespace, separate internal namespacesCommon Scenario for shared SMTP namespaceUse @source1.contoso.com / @target.contoso.comHint: Register the DNS zones for these on the Internet, and create MX records for themNeed to setup forwarding for mailbox/contacts

on each messaging system

Need to have process to change contacts when mailbox is migrated (must preserve

legacyExchangeDN

)

Mail FlowSlide37

Migration PlanningMail flow

Scenario: Shared external and internal namespaceCreate send and receive connectors to allow forwarding of messages not in the current Exchange orgCreate accepted domain, configure as internal relay domainCreate Send Connector, configure to send to shared address spacehttp://technet.microsoft.com/en-us/library/bb676395(EXCHG.80).aspx

Mail FlowSlide38

Migration PlanningMail flow issues

LegacyExchangeDNRequires multiple instances in multiple org deploymentsCan lead to large directory size and/or user reply failuresMessage loops/mail routing issuesNDRsWatch the postmaster mailbox during migrations

Mail FlowSlide39

Migration PlanningEDGE role/hygiene appliances

Look at address rewrite featuresCan share external namespace, split internal namespace at EDGE role/perimeter server – full list of recip on perimeterMultiple internal systems/namespacesEDGE uses internal LDAP directory, updated via EDGEsync or PS scriptsHygiene appliances offer similar functionality

Ability to leverage LDAP infrastructure (AD/ADAM/AD-LDS)

No updates to appliance required during mailbox move

Ensure LDAP directory is updated

Mail FlowSlide40

Migration PlanningCoexistence planning

Mailbox MigrationSlide41

Move Mailboxes to Exchange 2007

Three mailbox migration cmdlets: Move-mailbox: Copies or moves an active mailbox (a mailbox

which

is

associated

with

an AD

account

; not in an RSG or

disconnected

)

from

one Exchange

Database

to

another

Execute

Move-

Mailbox

from

Exchange 2007

If use ADUC/ESM,

mailbox

will

be

LegacyMailbox

on 2007

Export-

Mailbox

:

Copies or moves content

from

an active

mailbox

to a

folder

inside

another

active

mailbox

SP1 –

ExportMailbox to PSTNeeds to run on a 32 bit machine with OLK 2003/2007 and 32 bit version of Exchange Management ToolsRestore-Mailbox: Recovers content from a RSG mailbox to an active mailbox or copies content from a RSG mailbox to a folder inside an active

mailbox

Mailbox MigrationSlide42

Migration PlanningMailbox migration

Moving data from source mailbox to target mailboxNeed to determine requirementsFull mailbox/Partial mailbox(last 30 days of calendar/e-mail)IssuesMailbox offline during move - large mailboxes slow5000 item performance limit in Outlook 2003/2007 SP1 and Exchange 2007 RTM

Resolution – create folders and keep items count under 4500 per folder – including calendar

Upgrade to Office 2007 SP2 or use Online Mode

Don’t move mailboxes during backup window!

Mailbox MigrationSlide43

Migration PlanningMailbox migration tricks

Use multiple migration consoles (desktops/servers)One PS cmd per Exchange 2007 serverMove delegate/owner mailbox pairs togetherDatabase portability (2007 <-> 2007)Multithreaded mailbox moves in 2007Have seen up to 16 threads in the fieldPlan out source/target DB pairs, still limited by target database

Increase threads slowly, and watch

perfmon

counters

on servers for bottlenecks

1gb to 10gb / hour - your rate will vary. 3gb is typical

Mailbox MigrationSlide44

Migration PlanningMailbox migration tricks

Ensure database maintenance on source databases is completing regularlyMinimum 1 full pass per weekMAJOR impact on speed of migration Tuning mailbox move parametersNumber of processes source/target database servers can handleDisk performance on serversAvailable network bandwidthDatabase fragmentation

Mailbox MigrationSlide45

Public and System Folder MigrationMove Public Folder Replicas from the E2000/E2003 ESM

No GUI management of PF from Exchange 2007 EMCCan also use PowerShellMove the OAL Generation Server to E2007EMC or Shell: move-OfflineAddressBook Move the Public Folder Hierarchy to the Exchange 2007 Administrative GroupE2007 still needs local Mailbox Store for OAB GenSetup of Exchange 2007 creates new PDN

Causes PDN issue for OAB Version2 and OAB Version3

Causes OL2003 SP1 (and earlier) a full OAB download

Mailbox MigrationSlide46

Migration PlanningCoexistence planning

Free/BusySlide47

Migration PlanningFree/Busy synchronization

Required for users to see “Free/Busy” statusComplex to design and configureProvided only by Microsoft tools?

Free/BusySlide48

Migration PlanningFree/Busy synchronization

IOREPL (Inter-Org Replication Tool)Used between legacy 2000/2003 and 2007Separate Exchange organizationsReplicates the free/busy system folder between organizations Requires a directory synchronization process (MIIS/ILM/etc…)Uses stale/cached information, is not live/current data

Free/BusySlide49

Key TakeawaysExchange 2003 -> 2007 Transitions more than moving mailboxesUse the transition content provided here as a checklist of items for a smooth transition

“Big Bang” transition/migrations and large sets of data require detailed planning for smooth executionSlide50

Win!

LifeCam Show

Ultra-Thin Mobile Design

World-Class

High Definition

Optics

Question:

What are the supported migration paths from Exchange 5.5, 2000, 2003, 2007 ?

Please attend other business productivity sessions

Office and SharePoint track (OFC)

Unified Communications (UNC)Slide51

Exchange Deployment Planning Serviceshttp://www.microsoft.com/licensing/software-assurance/packaged-services.aspx

announcingSlide52

Take Advantage of EDPS to get your Deployment Going Microsoft Software Assurance Benefit

Structured engagement to help guide your organization through the deployment planning Review new Microsoft Exchange product featuresBest Practice SharingHelp to create comprehensive deployment and implementation plans3, 5, 10, or 15—as determined by your Software Assurance coverageSlide53

question & answerSlide54

www.microsoft.com/teched

International Content & Community

http://microsoft.com/technet

Resources for IT Professionals

http://microsoft.com/msdn

Resources for Developers

www.microsoft.com/learning

Microsoft Certification & Training Resources

Resources

Required Slide

Speakers,

TechEd 2009 is not producing

a DVD. Please announce that

attendees can

access session

recordings from Tech-Ed website. These will only be available after the event.

Tech

·Ed

Africa 2009 sessions will be made available for download the week after the event from:

www.tech-ed.co.zaSlide55

Related ContentMicrosoft Exchange Server 2010 Transition and Deployment (UNC310) High Availability in Microsoft Exchange Server 2010 (UNC301)Unified Messaging in Microsoft Exchange Server 2010 (UNC311)

Microsoft Exchange Server 2010 Management Tools (UNC309)Storage in Microsoft Exchange Server 2010 (UNC312) Microsoft Hyper-V: Dos and Don'ts for Microsoft Exchange Server 2007 SP1 and 2010 (VIR308) Archiving and Retention in Microsoft Exchange Server 2010 (UNC307)

Required Slide

Speakers,

please list the Breakout Sessions,

TLC Interactive Theaters and Labs

that are related to your session.Slide56

Required Slide

Complete a session evaluation and enter to win!

10 pairs of MP3

sunglasses

to be

wonSlide57

©

2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.

MICROSOFT

MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.