Transcript Charlie Chung Principle Program Manager Lead Exchange Server Microsoft Corporation Session Objectives And Takeaways Migration and Transition Planning Transition Technical Roadmap Migration Technical Roadmap Migration Logistical Planning “Big.

Charlie Chung
Principle Program Manager Lead
Exchange Server
Microsoft Corporation
Session Objectives And Takeaways
Migration and Transition Planning
Transition Technical Roadmap
Migration Technical Roadmap
Migration Logistical Planning
“Big Bang” Migrations
Migration Planning
Transition versus migration
Transition
Intra-org migration
Source: Exchange 2000, 2003, 2007
Same Exchange Organization
Same Active Directory Forest
Migration
Inter-org migration
Source: Any messaging platform
Different Exchange Organization
Active Directory Forest?
Transition Planning
Deploy Exchange 2007 into 2000/2003 org
Only to “native mode” 2000/2003 orgs
No loss of functionality in 2007 while Exchange
2000/2003 present
Once last 2000/2003 server is removed properly,
cannot reintroduce 2000/2003
2000/2003 functionality not present
RUS
Groupwise connector
X.400 connector
Transition Planning
Run pre-req checks
ExBPA
DCs with Windows Server 2003 SP1 (or later) req’d for
Domains containing Exchange 2007 servers
Domains 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 Master
Transition Planning
setup /PrepareLegacyExchangePermissions
Adds permissions back to the Exchange-Information property set to the
EES group
Not required to run in same domain/site as Schema Master for the
forest
Can specify a single domain to execute in, if not, must be able to contact
all domains in the forest
Transition Planning
Setup /PrepareSchema, /PrepareAD, /PrepareDomain
setup /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 in
Transition Planning
Exchange 200x/2007 Routing
All Exchange 2007 servers are within a single routing
group
Routing Group Name: DWBGZMFD01QNBJR
Introduction 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
groups
Exchange 2003 RGC bridgehead cannot be a cluster!
Transition Planning
Disabling 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 Group
Must be done to every Exchange 200x server in
the organization to prevent loops
All versions only use least cost route
Controlled via registry
HKLM\System\CurrentControlSet\Services\RESvc\Parameters
DWORD: SuppressStateChanges
Value: 1
Transition Planning
Routing and Connectors
Restrictions
Exchange 2003: Content Restrictions, Priorities, System/Non-System
Messages, Message Size Restrictions
Exchange 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 apply
Routing Logs
RoutingView
Replaces Winroute in E200x
Allows to read and compare Routing Logs
Transition Planning
Accepted Domains
Enabled SMTP proxies automatically added
@test1.local
Disabled SMTP proxies not added
@test2.local
Transition Planning
ActiveSync – 2003/2007
During co-existence CAS publishes E2003 mailboxes
Exchange 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
manager
Instead: 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 6
Transition Planning
Offline Address Book
Replicate OAB from 2003 PF to 2007 PF
Specify a 2007 MBX server to generate OAB
Once moved, can no longer manage from 2003
Set polling interval on CAS servers for OAB
Default is every 8 hours
Long time for cached mode clients
Replicates via Exchange File Distribution Service
Transition Planning
Offline Address Book - Clustering
OAB on SCC and CCR on Windows 2008
Generating the OAB causes an exception
OAB fails to generate (error 9334 and 9109)
OAB attempts recreate – cluster returns incorrect error code
Fix
Windows 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-oabgeneration-failing-on-ccr-and-scc-clusters.aspx
Transition Planning
Offline Address Book
Transitions
Need to move OAB to Exchange 2007
Need to update it to v4
Use OABInteg
http://code.msdn.microsoft.com/oabinteg
KB 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-totroubleshoot-oab-generation-issues.aspxalue: 1
Transition Planning
Public and System Folders
Replicate system folders from 2003 to 2007 PF servers:
Offline Address Book
Schedule+Free/Busy
Organizational Forms Library
Replicate public folders from 2003 to 2007 PF servers
Use PFDAVADMIN
Transition Planning
Mailbox Manager - 2003
Recipient Policies with Mailbox Manager only
Delete and recreate functionality with MRM
Recipient Policies with both Mailbox Mgr and Email
Addresses
Remove Mailbox Manager settings
Use ManagedDefaultFolders for MM settings in 2007
All recipient policies should be Email Addresses ONLY
before converting LDAP to OPATH filters
Transition Planning
Upgrade LDAP to OPATH
Need to migrate
Recipient Policies (email addresses, not mailbox manager)
Address Lists
Dynamic Distribution Lists
You 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=upgrading
Transition Planning
Remove Last Exchange 2003 Server
Move the PF hierarchy to Exchange Administrative
Group (FYDIBOHF23SPDLT)
Create a new PF container in 2007 AG
Drag the PF tree to the 2007 AG
Remove all RGCs to 2007 from 2003
Remove all recipient policies in 2003
Remove all recipient update services
Enterprise RUS remove via ADSI
Uninstall the last Exchange 2003 server
Note: wait until all Outlook clients have been redirected
after their mailbox moves
Transition Planning
Remove Last Exchange 2003 Server
After the last Exchange 200x server has been removed from the
Exchange 2007 organization
Remove Write DACL inherit (group) right for the Exchange
Servers group from the root of the domain
Remove-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).aspx
Transition Planning
Remove Last Exchange 2003 Server
Keep an Exchange 2003 ESM interface to enable GUI
management of:
Public Folders
Details Templates
Address Templates
Do not delete Admin Groups that ever contained
mailboxes
Used for Free/Busy information for 2003 and prior clients
Used for delegate access for ALL OLK clients
Migration Planning
Logistics and Project Planning
Directory
Sync
Free/Busy
Mail Flow
Mailbox
Migration
Migration Planning
Logistics
“Big Bang” Migrations – How to Plan?
Iterative Approach
250 -> 500 -> 1000 -> 2500 -> 5000
Have seen up to 20,000 per weekend possible
(what is the largest one here)?
Require extensive planning
Scale up slowly – pilot “Waves”
Understand bottlenecks
Level set expectations
Logistics
Migration Planning
"Big Bang" Scalability Factors
Target Capacity
Data Throughput
Data Scope
Transaction Log Volumes
User Training
Cached Mode!
Floor Support
Help Desk
Archiving Solution
Logistics
Backup / OLM Window
Resource Mailboxes
Client Configuration
Valid Pilot
Network
Layout/Throughput
RIM BlackBerry
VIP User Scenarios
Migration Planning
"Big Bang" - Post Move
Logistics
Free / Busy
Default – check permissions
Client version – different free/busy returned (PF vs EWS)
Out of Office
BES changes 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
Migration Planning
Data Migration
Logistics
Data Approach
Tools average 1-10/GB hour throughput
Factors that influence speed:
Health of source servers and databases
Network links for source/mig/target
Multiple migration consoles
Scope 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
Migration Planning
Windows 2003 -> 2008
Logistics
No in-place upgrades from 2003 -> 2008 for
Exchange 2007 servers
Cannot use SCR between 2003 -> 2008 servers
Cannot have 2003/2008 mixed clusters
Requires
Mailbox moves
Database portability
Migration Planning
Coexistence planning
Directory
Sync
Free/Busy
Mail Flow
Mailbox
Migration
Mail Flow
Migration Planning
Mail flow
Plan carefully! Mistakes here will be visible to
the outside world
Need to determine inbound, outbound, and internal
mail routing scenarios
Some 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
Flow
Migration Planning
Mail flow
Mail
Flow
Scenario: Shared external namespace, separate
internal namespaces
Common Scenario for shared SMTP namespace
Use @source1.contoso.com / @target.contoso.com
Hint: Register the DNS zones for these on the Internet, and
create MX records for them
Need to setup forwarding for mailbox/contacts
on each messaging system
Need to have process to change contacts when mailbox is
migrated (must preserve legacyExchangeDN)
Migration Planning
Mail flow
Mail
Flow
Scenario: Shared external and internal namespace
Create send and receive connectors to allow
forwarding of messages not in the current Exchange
org
Create accepted domain, configure as internal relay
domain
Create Send Connector, configure to send to shared
address space
http://technet.microsoft.com/en-us/library/bb676395(EXCHG.80).aspx
Migration Planning
Mail flow issues
Mail
Flow
LegacyExchangeDN
Requires multiple instances in multiple
org deployments
Can lead to large directory size and/or user reply
failures
Message loops/mail routing issues
NDRs
Watch the postmaster mailbox
during migrations
Migration Planning
EDGE role/hygiene appliances
Mail
Flow
Look at address rewrite features
Can share external namespace, split internal
namespace at EDGE role
Multiple internal systems/namespaces
EDGE uses internal LDAP directory, updated via EDGEsync or
PS scripts
Hygiene 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
Migration Planning
Coexistence planning
Directory
Sync
Free/Busy
Mail Flow
Mailbox
Migration
Mailbox
Migration
Move Mailboxes to Exchange 2007
Three mailbox migration cmdlets:
Mailbox
Migration
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 PST
Needs to run on a 32 bit machine with OLK 2003/2007 and 32 bit
version of Exchange Management Tools
Restore-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
Migration Planning
Mailbox migration
Mailbox
Migration
Moving data from source mailbox to target mailbox
Need to determine requirements
Full mailbox/Partial mailbox
(last 30 days of calendar/e-mail)
Issues
Mailbox offline during move - large mailboxes slow
5000 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!
Migration Planning
Mailbox migration tricks
Mailbox
Migration
Use multiple migration consoles (desktops/servers)
One PS cmd per Exchange 2007 server
Move delegate/owner mailbox pairs together
Database portability (2007 <-> 2007)
Multithreaded mailbox moves in 2007
Have seen up to 16 threads in the field
Plan 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
Migration Planning
Mailbox migration tricks
Mailbox
Migration
Ensure database maintenance on source
databases is completing regularly
Minimum 1 full pass per week
MAJOR impact on speed of migration
Tuning mailbox move parameters
Number of processes source/target database
servers can handle
Disk performance on servers
Available network bandwidth
Database fragmentation
Public and System Folder Migration
Mailbox
Migration
Move Public Folder Replicas from the E2000/E2003 ESM
No GUI management of PF from Exchange 2007 EMC
Can also use PowerShell
Move the OAL Generation Server to E2007
EMC or Shell: move-OfflineAddressBook
Move the Public Folder Hierarchy to the Exchange 2007
Administrative Group
E2007 still needs local Mailbox Store for OAB Gen
Setup of Exchange 2007 creates new PDN
Causes PDN issue for OAB Version2 and OAB Version3
Causes OL2003 SP1 (and earlier) a full OAB download
Migration Planning
Coexistence planning
Directory
Sync
Free/Busy
Mail Flow
Mailbox
Migration
Free/Busy
Migration Planning
Free/Busy synchronization
Free/Busy
Required for users to see “Free/Busy” status
Complex to design and configure
Provided only by Microsoft tools
Exchange
• 2003: IOREPL
• 2007: Native via Availability Service cross-org
• 2010: Federation Services
Domino
• 2007 Transporter
• 2003 Connector
Groupwise
• 2003 Connector
Migration Planning
Free/Busy synchronization
Free/Busy
IOREPL (Inter-Org Replication Tool)
Used between legacy 2000/2003 and 2007
Separate Exchange organizations
Replicates the free/busy system folder between
organizations
Requires a directory synchronization process
(MIIS/ILM/etc…)
Uses stale/cached information, is not live/current
data
Key Takeaways
Exchange 2003 -> 2007 Transitions more than
moving mailboxes
Use 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
execution
Resources
www.microsoft.com/teched
www.microsoft.com/learning
Sessions On-Demand & Community
Microsoft Certification & Training Resources
http://microsoft.com/technet
http://microsoft.com/msdn
Resources for IT Professionals
Resources for Developers
www.microsoft.com/learning
Microsoft Certification and Training Resources
Related Content
UNC 307: Microsoft Exchange Server 2007 Sizing and Performance: Getting It Right with
64-Bit
UNC 315: Federation in Microsoft Exchange Server 2010
UNC 318: Microsoft Exchange Server 2010 Transition and Deployment
UNC 310: Migration to Microsoft Online Services from Non-Microsoft Platforms
UNC14-HOL: Microsoft Exchange Server 2010 Setup and Deployment
Complete an
evaluation on
CommNet and
enter to win!
© 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.