page 1October, 7th, 2002 © 2002

Exchange 2000 Notes From The

Field

What We Have Learned

Kieran McCorryPrincipal Consultant

Technology Leadership Group

October 7, 2002

© 2002 page 2 October, 7th, 2002

Agenda?

Preparation for deployment

Selecting the Right Architecture

Migration Approaches

Third Party Products

Best Practices

page 3October, 7th, 2002 © 2002

•Many ways to access your mailbox– NT4 acc/E5.5 mailbox

– W2K acc/E5.5 mailbox

– NT4 acc/E2K mailbox

– WK acc/E2K mailbox

Preparing For Migration

Deploying Windows 2000

•Migrating all users to Windows 2000 first– Sometimes it’s a good

idea

•Deploying the basic infrastructure is enough

•Let the dir synch process take care of creating user objects

page 4October, 7th, 2002 © 2002

Building Windows 2000

Servers

Take a Standard Platform Approach

•Makes rollout and ongoing maintenance simpler

• Identify server types and appropriate builds

Automate as much as possible

•Use slipstream CDs

•Automated build tools, etc.

page 5October, 7th, 2002 © 2002

Selecting the ‘Right’

Exchange Architecture

•What are the Types of servers you need to deploy?

– Do you want to centralize as much as possible?

– Do you have the appropriate bandwidth?

– Should you use Datacenter clustering?

– Is clustering even appropriate?

– Are there alternatives?

– How many users should you place on a server?

page 6October, 7th, 2002 © 2002

Test Every Aspect Of Your Migration

Build a comprehensive test facility

Mimic your complete environment

Include multiple domains, multiple Exchange 5.5 sites, etc.

Characterize network connections, use WAN emulators

Test migration processes

Migration from NT4 and W2K interoperability

Migration from E5.5 and E2K interoperability

Test your fallback procedures too!

© 2002 page 7 October, 7th, 2002

Build A Strong Dedicated Team

•You’ll need a team of experts focused on the deployment and migration– Exchange experts

– Windows experts

– DNS/Networking

– Programmers maybe too

• In Compaq we had– 6 central engineering

staff

– Other staff at regional locations

•Expect to spend months in testing

page 8October, 7th, 2002 © 2002

Migration Techniques

•Plan directory synch carefully

– Clean up the Exchange 5.5 Directory

– Avoid using 1-way CAs and changing them later to 2-way CAs

– Almost always create disabled users

– Understand exactly how the ADC works

– Avoid using excessive CAs by some clever planning

page 9October, 7th, 2002 © 2002

An Example of ADC Behavior

Recipients

TemporaryObjects

FinalObjects

Two-WayConnection Agreement

Active Directory

Exchange 5.5 Site

From Exchange:Source: RecipientsTarget: Temporary Objects

From Windows:Source: Temporary ObjectsTarget: Recipients

Object Moved

Changes to the Exchange 5.5 ObjectContinue to be propagated to AD

One-WayConnection Agreement

page 10October, 7th, 2002 © 2002

Use Clever OU Designs to Minimize CAs

Exchange 5.5 EnvironmentOrg ACME

Tokyo

Site ContainerWindows 2000

Active Directory

AP.ACME.COM

ACCOUNTS TEMP

GroupsUsers Tokyo

Recipients

DLs

One-WayCAsBangkok

Site Container

Bangkok

Recipients

DLsTwo-Way CAs

© 2002 page 11 October, 7th, 2002

Standard Approaches For

Migration

Intra-Org Migrations are most common

•Works well with a single organization

•Good when PFs heavily used

•Larger orgs tend not to upgrade in-place

•Mailbox data is usually migrated

•New/replacement hardware is usually deployed

page 12October, 7th, 2002 © 2002

Migration Techniques

•Moving large numbers of users• AD Users and Computers is

cumbersome

• It’s easy and good to script bulk mailbox moves

•Mailbox moves can be automated

Private Function MoveMailbox (UserDN As String, TargetMBStore As String)

Dim objPerson As New CDO.Person

Dim objMailbox As CDOEXM.IMailboxStore

objPerson.DataSource.Open “LDAP://” & UserDN

Set objMailbox = objPerson

objMailbox.MoveMailbox “LDAP://” & TargetMBStore

objPerson.DataSource.Save

Set objPerson = Nothing

End Function

page 13October, 7th, 2002 © 2002

Inter-Org Migrations

Useful with multiple separate orgs

•Brand new start

•Good when you want to restructure your Admin model

•Not so good with PFs

Straightforward process

•Can use the ADC for inter-org synch– But consider a more

heavy duty synch tool in complex environments

– Use the Exchange Migration Wizard for mailbox moves

page 14October, 7th, 2002 © 2002

Partial Organization Migration

A single Exchange 5.5 organization can spin off for its migration

•Essentially you break the Exchange 5.5 org into two parts

•You’ll need to provide some sort of directory synch

• Just make sure PFs and users are segregated by Site

•Or, you can start in intra-org migration and split the new E2K org off later…

page 15October, 7th, 2002 © 2002

An Initial Approach For Partial Migration

Site A

Org ACME

5.5 Srv

Site B

5.5 Srv

DirectoryReplicationConnector

Site A

Org ACME

5.5 Srv

Site B

Org ACME

5.5 SrvDirectorySynchronization

page 16October, 7th, 2002 © 2002

Alternative Approaches For Partial Migration

Site A

Org ACME

5.5 Srv

Site B

5.5 Srv

E2K Srv

Recip CA

Config CA

DirectorySynch

DirectoryReplicationConnector

Site A

Org ACME

Site B

5.5 Srv

DirectorySynch

DirectoryReplicationConnector

E2K SrvE2K Srv

page 17October, 7th, 2002 © 2002

The Partial Migration Completed

Org ACME

Site B

5.5 Srv

Org ACME

E2K SrvE2K Srv

DirectorySynch

page 18October, 7th, 2002 © 2002

End State Third Party Products

Can you survive with just Windows and Exchange?Or do you need to evaluate options?• Anti-virus best practices

– Sybari– Trend Micro– Norton

• Monitoring and Management– HP OpenView– MOM– NetIQ tools

• Backup and Restore– Commvault Galaxy– Veritas

• Anti-SPAM tools– MAPS RBL+– Brightmail

• Data Archiving– KVS

page 19October, 7th, 2002 © 2002

What Migration Tools? When?

•Windows tools always useful for intra-org migrations• But you might

augment/script with the default tools to simplify mailbox moves

• Exchange migration tools VERY useful for inter-org migrations

•Understand the different types of tools available• Windows Migration Tools

• Exchange Migration Tools

•Tools available from • NetIQ

• Quest/Fastlane

• Bindview

• Aelita

page 20October, 7th, 2002 © 2002

Best Practices

Use Enhancements When Needed

Consider, develop, implement possible enhancements to base product

•SMTP Event Sinks for Logging

•Customized SMTP Filters (disclaimers, etc.)

•Event sinks that replace attachments with links

•Catch-all mail re-routing (even on same server)

page 21October, 7th, 2002 © 2002

Best Practices

Planning and Design

Summary

Communicate plans to all related teams AND to users

Understand your complete environment

• Especially the network and user patterns

Integrate testing of all components

Review your plans: get a QA check at least

Characterize migration tools

• Allow up to two weeks testing per migration product

• Stick with same vendor where possible

page 22October, 7th, 2002 © 2002

Best Practices

Implementation Summary

Make sure you load test any customizations before deployment

Market activities to users

Automate processes where possible

•Server builds

•Client deployments

© 2002 page 23 October, 7th, 2002

Questions?