msg211 marks & spencer exchange 2003 migration colin rogers gary christensen mike guerrini
TRANSCRIPT
MSG211MSG211
Marks & SpencerMarks & SpencerExchange 2003 Migration Exchange 2003 Migration
Colin RogersColin Rogers
Gary ChristensenGary Christensen
Mike GuerriniMike Guerrini
Who are we ?
• Speakers • Colin Rogers – Project Manager• Gary Christensen – Exchange Consultant• Mike Guerrini – Exchange Consultant
• Marks & Spencer• Marks & Spencer is one of the UK's leading retailers of
clothing, foods, homeware and financial services, serving 10 million customers a week in over 300 UK stores.
• The Company also trades in 30 countries worldwide.• Marks & Spencer has a Group turnover in excess of £8
billion.
Agenda
• Where we started from
• Why we chose to upgrade
• Where we wanted to get to
• How we got there and what it looks like
• What we learned along the way
• Questions and answers
Agenda
• Where we started from
• Why we chose to upgrade
• Where we wanted to get to
• How we got there and what it looks like
• What we learned along the way
• Questions and answers
Where did we start from ?• Windows NT4 (with a bit of AD)
M&SMoney
HO ResDomain
HO ResDomain
HO ResDomain
HO ResDomain
Stores NT4DomainsStores NT4
DomainsStores NT4DomainsStores NT4
Domains
SharedInfrastructure
Exchange 5.5Domain
User AccountsOnly
Machine AccountsOnly
Mixed - User &Machine Accounts
HO ADDomain
RootDomain
HongKong
Where did we start from ?
• Exchange 5.5
• 30 Exchange Servers
• 12,000 Mailboxes (used by 90,000 users)
• Stable Environment…
• …but rapidly running out of support
Exchange Topology
WW
Internet
SMTPGateway
SMTPGateway
Exchange5.5
Server
Exchange5.5
Server
CORP
Head OfficeExchange
5.5Servers
StoresExchange
5.5Servers
M&S MoneyExchange
5.5Servers
AP
INTERNET
Exchange5.5
Server
Exchange5.5
Server
Hong KongExchange
5.5Servers
LDAP FilterOrganisation
InternalOrganisation
Agenda
• Where we started from
• Why we chose to upgrade
• Where we wanted to get to
• How we got there and what it looks like
• What we learned along the way
• Questions and answers
Why did we choose to upgrade ?
• Driven by head office relocation
• Recognition that e-mail was business critical
• New architectural principles
• Out of support:• NT4 Server
• Exchange 5.5
• Legacy server hardware
Where did we want to get to ?
• Centralised service offering
• Clustering (started with 4 node…)
• Windows Server 2003
• Centralised storage (SAN)
• Improved backups (snapshots)
• Mobility features
• Native mode Exchange organisation
Agenda
• Where we started from
• Why we chose to upgrade
• Where we wanted to get to
• How we got there and what it looks like
• What we learned along the way
• Questions and answers
How did we get there ?
• One Team• Dedicated internal team
• Virtual supplier team
• Microsoft JDP
• Rapid Application Deployment approach
How did we get there ?
• Collapsing Exchange 5.5 sites
• New domain structure
• ADC design and deployment
• Exchange 2003 deployment
• Moving the mailboxes (finally)
New Exchange Domain
M&SMoney
HO ResDomain
HO ResDomain
HO ResDomain
HO ResDomain
Stores NT4DomainsStores NT4
DomainsStores NT4DomainsStores NT4
Domains
SharedInfrastructure
Exchange 5.5Domain
User AccountsOnly
Machine AccountsOnly
Mixed - User &Machine Accounts
HO ADDomain
RootDomain
HongKong
New Exchange Domain
M&SMoney
HO ResDomain
HO ResDomain
HO ResDomain
HO ResDomain
Stores NT4DomainsStores NT4
DomainsStores NT4DomainsStores NT4
Domains
SharedInfrastructure
Exchange 5.5Domain
User AccountsOnly
Machine AccountsOnly
Mixed - User &Machine Accounts
HO ADDomain
RootDomain
HongKong
MNSExchange
ADC Design Considerations
• 303181 – NTDSNOMATCH• We needed to set this value in Custom
Attribute 11 (this also breaks ADC tools)
• 269843 – ADC overwrites display name
• 243311 – Ambiguous Name Resolution• We use Custom Attribute 6 to resolve
mailbox names
Exchange Topology
WW
Internet
SMTPGateway
SMTPGateway
Exchange5.5
Server
Exchange5.5
Server
CORP
Head OfficeExchange
5.5Servers
StoresExchange
5.5Servers
M&S MoneyExchange
5.5Servers
AP
INTERNET
Exchange5.5
Server
Exchange5.5
Server
Hong KongExchange
5.5Servers
LDAP FilterOrganisation
InternalOrganisation
Exchange Topology
CORP
WW
Internet
SMTPGateway
(SP)
SMTPGateway
(SW)
Exchange5.5
Server
Exchange5.5
Server
Head OfficeExchange
5.5Servers
StoresExchange
5.5Servers
M&S MoneyExchange
5.5Servers
AP
INTERNET
Exchange5.5
Server
Exchange5.5
Server
Hong KongExchange
5.5Servers
InternalOrganisation
LDAP FilterOrganisation
E2K3 BECluster
(SP)
E2K3 BECluster(SW)
E2K3 FEServers
(SP)
E2K3 FEServers
(SW)
How did we get there ?
• Collapsing Exchange 5.5 sites
• New domain structure
• ADC design and deployment
• Exchange 2003 deployment
• Moving the mailboxes (finally)
• The importance of testing!
Where next ?
• Still a long way to go…
• Stores mailboxes
• Marks & Spencer Money mailboxes
• Application mailboxes
• Hong Kong site
• MOM
• Snapshot backups
Agenda
• Where we started from
• Why we chose to upgrade
• Where we wanted to get to
• How we got there and what it looks like
• What we learned along the way
• Questions and answers
Lessons Learned – The Good
• Windows 2003
• SAN technology
• Exchange 2003
• Multi-threaded mailbox migration tool
• JDP experience
Lessons Learned – The not so good
• 3rd Party vendor support for:• Windows 2003
• VSS requestor availability
• Gigabit Ethernet issues
• Migrating role based mailboxes
• Random loss of delegate permissions during mailbox move
To recap …
• Was it worth upgrading?
• Would we do it again?
• Would we do it differently?
evaluationsevaluations
© 2003 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.