Nathan winters mvp exchange server consultant dimension data l.jpg
This presentation is the property of its rightful owner.
Sponsored Links
1 / 47

Migrating from Exchange 2003 to Exchange 2007 PowerPoint PPT Presentation


  • 163 Views
  • Uploaded on
  • Presentation posted in: General

Nathan Winters – MVP – Exchange Server Consultant – Dimension Data. Migrating from Exchange 2003 to Exchange 2007. Agenda. Exchange 2007 – A Quick Intro Planning for Exchange 2007 Designing Exchange 2007 Migrating to Exchange 2007 Documentation Summary. Forest.

Download Presentation

Migrating from Exchange 2003 to Exchange 2007

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Nathan winters mvp exchange server consultant dimension data l.jpg

Nathan Winters – MVP – Exchange Server

Consultant – Dimension Data

Migrating from Exchange 2003 to Exchange 2007


Agenda l.jpg

Agenda

  • Exchange 2007 – A Quick Intro

  • Planning for Exchange 2007

  • Designing Exchange 2007

  • Migrating to Exchange 2007

  • Documentation

  • Summary


Server roles l.jpg

Forest

Hub Transport server role

Client Access server role

Edge Transport server role

Internet

Directory Server

Mailbox server role

Server Roles

UM Server


Agenda4 l.jpg

Agenda

  • Exchange 2007 – A quick intro

  • Planning for Exchange 2007

  • Designing Exchange 2007

  • Migrating to Exchange 2007

  • Documentation

  • Summary


Planning considerations l.jpg

Planning Considerations

  • Active Directory

    • Schema update

    • Permission changes (Split Permissions Model)

    • Some data exported/sync’d with Edge Transport server

    • Windows Server 2003 SP1 or later required for;

      • At least one DC in each Site containing Exchange

      • Schema Master

    • Windows 2000 Native or higher domain functional level

  • DNS

    • Edge Transport resolution of Hub Transport server

    • Autodiscover

    • Single, unified internal namespace

    • DNS Suffix for Edge Transport server


Planning considerations6 l.jpg

Planning Considerations

  • Hardware

    • 64 Bit

  • Mailbox server role

    • Standalone or clustered (CCR or SCC)

    • Replication (LCR, CCR, SCR, 3rd Party)

    • Storage (DAS, SAN, iSCSI)

    • Public Folders

  • Hub Transport server role

    • Using Active Directory Sites for routing

    • Exchange costs can override Site routing

    • Built-in resilience/failover with multiple servers in Site


Planning considerations7 l.jpg

Planning Considerations

  • Client Access server role

    • Protocols: EAS, HTTPS, POP3, IMAP4

    • Services: Availability, Autodiscover, Web Services

    • Very different from Front-End servers in earlier versions

      • Optimize performance for Mailbox server role

      • Never put in a perimeter network

      • Internal, well-connected network (100 Mbps – 1 Gbps)

  • Unified Messaging server role

    • Integrates telephony systems with Exchange

      • PBX, IP/PBX, VoIP

    • Many new terms and technologies to learn


Planning considerations8 l.jpg

Planning Considerations

  • Edge Transport server role

    • Designed for a perimeter network deployment

    • Not a member of internal Active Directory forest/domain

    • Can be a member of perimeter network forest/domain

      • Useful for management purposes (group policy, etc.)

      • MSIT does this

    • Stores configuration data in local file and Active Directory Application Mode (ADAM)

      • Uses EdgeSync for one-way transfer of data from Active Directory to ADAM

    • Minimal attack surface

      • TCP port 25, 50636, optional RDP port


Base software requirements for exchange 2007 l.jpg

Base Software Requirements for Exchange 2007

  • Windows Server 2003 x64 w/SP1 or R2, or SP2

    • Allows OWA users to browse the GAL

  • Microsoft .NET Framework 2.0

  • Windows PowerShell 1.0

  • Microsoft Management Console (MMC) 3.0

  • Hotfixes / Updates

    • 272618_intl_x64_zip.exe (Edge)

    • NDP20-KB926776-X64.exe (.NET update)

    • WindowsServerver2003.WindowsXP-KB918980-x64-ENU.exe (Windows Server Update)

    • Windowsmedia10-kb917312-x64-intl.exe (UM)

    • .NET Framework 2.0 Service Pack 1 or hotfix from 942027


Windows 2008 exchange support l.jpg

Windows 2008 Exchange Support

  • WS08 writeable DC’s are supported in environments that have the following Exchange Servers

    • Exchange 2003 SP2

    • Exchange 2007 RTM

    • Exchange 2007 SP1

  • WS08 RODC/ROGC's.

    • No Exchange servers are RO aware

  • Exchange 2007 RTM and previous versions of Exchange are not supported for installation on a Windows 2008 server.

  • Exchange 2007 SP1 can be installed on a Windows 2008 server.


Functional dependencies l.jpg

Functional Dependencies

  • Retain Exchange 2003 for:

    • X400 Connector

    • GroupWise Connector and Migration Tools

    • Event Service

    • NNTP

    • OWA

      • PF Access

      • Outlook Mobile Access

      • SMIME Control


Agenda12 l.jpg

Agenda

  • Exchange 2007 – A quick intro

  • Planning for Exchange 2007

  • Designing Exchange 2007

  • Migrating to Exchange 2007

  • Documentation

  • Summary


Starting off right l.jpg

Starting Off Right...

  • Getting real customer requirements is essential

  • Prioritise and validate those requirements

  • Write a Vision and Scope document – and get it agreed

  • Deal with changes through a change control process

  • If you don’t... It WILL creep


Architecture l.jpg

Architecture

  • Keep It Simple at all times

  • Forget empty forest roots

  • Carefully consider delegated admin models – they rarely work

  • Clustering is not the only answer

  • Make sure it is supportable!

  • Do some discovery - Measure existing systems – measure peak IOPS, mailflow, mailbox profile etc.

  • Know how to use Perfmon

  • Use ExBPA


Design considerations l.jpg

Design Considerations

  • Sizing

  • Compliance

  • Archiving

  • WAN – Cached mode etc (Optimisation)

  • Client access methods

  • Existing IPT and Unified Messaging

  • Management and Reporting

  • Disaster Recovery – High Availability


Server placement considerations l.jpg

Server Placement Considerations

  • Sites

  • CAS

  • Name space

  • Method of access

  • WAN links


Public folders l.jpg

Public Folders

  • Public Folders are widely used for sharing and DL archiving

  • SharePoint 2007 is another solution for sharing and DL archiving

    • http://www.tsunami.com

    • http://www.casahl.com

    • http://www.quest.com

  • All previous versions of Outlook and Exchange required Public Folders to be deployed.

  • Public Folders are required within an organization until:

    • All Outlook clients are upgraded to Outlook 2007

    • All mailboxes have been migrated to Exchange 2007

    • No Public Folder applications are still used

http://blogs.msdn.com/joelo/archive/2007/07/26/migration-tools-from-kimmo-forss.aspx


Key sizing elements l.jpg

Key Sizing Elements

  • Size for “peak average”

    not “peak peak”

    • Monday morning

    • Repeatable

    • Busiest servers

    • Not “average average”, either

  • Take a visual average

  • Know when to use percentiles

Peak average connections: ~2100

Average active connections: 1441


Sizing methodology l.jpg

Sizing Methodology


Sizing resources and testing tools l.jpg

Sizing Resources and Testing Tools

  • Sizing Tools

    • Microsoft’s Exchange Server 2007 Mailbox Server Role Storage Requirements Calculator

  • DiY

    • Load Generator

    • ESP

    • JetStress

  • Info on MSIT’s deployment IT Showcase

  • Blogs, TechNet

  • White papers

  • System Center Capacity Planner 2007


Mailbox server sizing l.jpg

Rules of Thumb

Mailbox Server Sizing

  • CPU

    • Up to 8 cores

    • ~500 – 1,000 mailboxes / core

    • All other roles have a

      ratio based on this number

  • Memory

    • 2 – 5MB/mailbox + 2GB

    • Also SG-dependent

    • 32GB cost effective at RTM but no real maximum

  • Network

    • Min Gbit

    • With CCR use separate NICs for public and private networks


Mailbox server sizing22 l.jpg

Rules of Thumb

Mailbox Server Sizing

  • Disk

    • Balance I/O and Capacity

    • Content Indexing (online mode, OWA users)

      • +5% capacity onto database LUN size

    • Overhead / white space

      • Target database size + 10%

    • SLA factored into sizing

      • Max database size

      • Recovery Storage Group

      • Backup to Disk

      • Delete items retention default is 14 days (15 – 30% increase)

    • CCR Considerations

    • Cold State / Cache Warming impact


Cas server sizing l.jpg

Rules of Thumb

CAS Server Sizing

Processor

Memory Usage

  • CPU

    • Up to 4 cores

    • 1:4 CAS:Mailbox cores

  • Memory

    • 2GB/core new!

    • Heavy Outlook Anywhere access: 2GB+/core (16GB max new!)

  • Disk – sure, why not

  • Network

    • Gbit recommended

  • 64k connection limit


Hub transport server sizing l.jpg

Rules of Thumb

Hub Transport Server Sizing

  • CPU

  • Memory

    • 1GB/core; 16GB max

    • Large queue scenarios

      • Per message overhead: 3K, per recipient overhead: 1K

    • Edgesync (enterprise deployments)

      • 4K per mail-enabled object

  • Disk

    • Separate mail.que and logs from system disks (RAID 10)

    • Transport dumpster impact

    • 4GB minimum free space or Back Pressure kicks in…. VM testing - beware

  • Network

    • Gbit recommended


Um server sizing l.jpg

Rules of Thumb

UM Server Sizing

Tests were conducted on a system with 4 GB RAM and 2 x 2-core, 4 Ghz processors

  • CPU

    • Up to 4 cores

    • Multiple cores recommended if converting from .wav to .wma

  • Memory

    • 1GB/core (2GB minimum)

    • 4GB maximum

  • Disk

    • Based on codec

  • Network

    • Gbit recommended

  • Concurrency

    • 60 users (WMA)

    • 75 users (GSM)

    • Equates to 2K – 10K user population per server


Agenda26 l.jpg

Agenda

  • Exchange 2007 – A quick intro

  • Planning for Exchange 2007

  • Designing Exchange 2007

  • Migrating to Exchange 2007

  • Documentation

  • Summary


Exchange migration methods l.jpg

Exchange Migration Methods

a. Intra Organisational

b. Inter Organisational

Org A

Org B

Org A


Preparation l.jpg

Preparation

  • Base build server and install prerequisites

  • Patch server

  • Create OUs for server objects in AD

  • Move server machine accounts in to correct OUs

  • Create Exchange Full Administrator Service Account

  • Grant Domain, Ent and Schema Admins and Make Exchange 2003 Full admin

  • Copy the install files to each server - c:\software\Exchange2007

  • Create updates dir on each server - c:\software\Exchange2007Patches

  • Copy rollup 1 to updates dir (Note Error - currently manual)

  • Create binaries install location (New-Item -Type directory -Path "D:\Program Files\Microsoft\Exchange Server")

  • If not already in existence create Certificate Authority

  • Implement Link State suppression

  • Clean up accepted domains and recipient policies before deployment

  • Verify Server Build: Network config, Patching, IE version, Prerequisites


Exchange 2007 setup prepare ad overview l.jpg

Exchange 2007 Setup Prepare AD Overview

  • /PrepareLegacyExchangePermissions

    • For every Ex 200x ‘domainpreped’ domain

    • For a specified domain

  • /PrepareSchema

    • Apply legacy permissions if required

    • Extend schema

  • /PrepareAD

    • Apply legacy permissions if required

    • Extend schema if required

    • Create Exchange global objects

    • Prepare local domain

  • /PrepareDomain

    • For local domain

    • For all domains

    • For a specified domain


Verify the schema has been extended l.jpg

Verify the Schema Has Been Extended

Exchange 2007 Service Pack 1 Schema Version 11116


Verify prepare ad exchange 2007 security groups l.jpg

Verify Prepare ADExchange 2007 Security Groups

  • Setup creates five Exchange USG in the root domain

  • Exchange Administrative Group (FYDIBOHF23SPDLT)

  • Exchange Routing Group (DWBGZMFD01QNBJR)


Order of deployment l.jpg

Order of Deployment

  • Install server roles in this order:

    • Client Access server role

    • Hub Transport server role

    • Mailbox server role

    • Unified Messaging server role

    • Edge Transport server role can be introduced at any time

      • Full functionality requires Hub Transport server and EdgeSync


Unattended setup l.jpg

Unattended Setup

  • Setup.com /r:”c,m,u,h”

    • /roles:<roles to install>

      • Hub Transport (H); Client Access (C); Edge (E); Mailbox (M); Unified Messaging (U); Management Tools (T)

    • /mode:<setup mode>

      • Install, Uninstall, Upgrade, RecoverServer

    • /TargetDir:<folder>

    • /DomainController

    • /prepareAD

    • /prepareSchema

    • /prepareLegacyExchangePermissions

    • /NewProvisionedServer

    • /OrganizationName

    • /EnableLegacyOutlook

    • /LegacyRoutingServer


Check straight after setup l.jpg

Check Straight After Setup

  • Check the Application Event Log

  • Run the Get-ExchangeServercmdlet

  • Parse through setup logs

    • Get-SetupLog c:\exchangesetuplogs\exchangesetup.log -error –tree

  • Enter Product Key

  • Run ExBPA


Exchange setup log locations l.jpg

Exchange Setup Log Locations


Understanding success or failure learning to trust setup l.jpg

Understanding success or failureLearning to trust setup

  • Simple return codes

    • 0 for success

    • 1 for failure

  • The right data in the log

    • ExchangeSetup.log, found in the ExchangeSetupLogs directory of your system drive

    • Errors and Warnings are uniformly annotated

    • Success/Failure messages are unambiguous

      [5/25/2006 3:32:05 PM] [0] The Microsoft Exchange Server setup operation completed successfully.

      [5/25/2006 3:32:05 PM] [0] End of Setup

  • get-setuplog.msh used to parse log


Role specific post setup tasks l.jpg

Role Specific Post Setup Tasks


Non role specific tasks l.jpg

Non Role Specific Tasks

  • Baseline Performance

  • Security – SCW

  • Create and Test your DR plan

  • Ensure DNS Reverse lookup and Sender ID records are setup correctly

  • Monitor the Basics

  • Permission/Role Delegation

  • Training

  • Documentation!

    • Regularly perform documentation updates

  • Regularly run ExBPA

  • Administration delegation

  • Deploy Outlook 2007


Move mailbox preparation l.jpg

Move Mailbox Preparation

  • Required permissions

    • Exchange Recipient Administrator

    • Exchange Server Administrator

    • Member of Local Administrators group

  • Transaction logs increase

  • Single instance storage loss (potential)

  • User mailbox cleanup


Bulk migration options l.jpg

Bulk Migration Options

Move-mailbox –identity bond –targetdatabase “007E2K7\first storage group\mailbox database”

  • User

  • Database

  • Server

Get-mailbox –database “009E2K3dc1\First Storage Group\Mailbox Store (009E2K3dc1)” | move-mailbox –targetdatabase “007E2K7\first storage group\mailbox database”

Get-mailbox –server “009E2K3dc1” | move-mailbox –targetdatabase “007E2K7\first storage group\mailbox database”


Post mailbox migration confirmation event viewer l.jpg

Post-Mailbox Migration Confirmation: Event Viewer

  • Event IDs

    • 1006

    • 9354

    • 1007


Decommissioning l.jpg

Decommissioning

Things to consider…

  • Reroute mail to target environment

  • Ensure all mail has been moved

  • Ensure all public folders have been re-homed.


Agenda43 l.jpg

Agenda

  • Exchange 2007 – A quick intro

  • Planning for Exchange 2007

  • Designing Exchange 2007

  • Migrating to Exchange 2007

  • Documentation

  • Summary


Script it l.jpg

Script It!

  • Let’s take a look at some scripts…….


Agenda45 l.jpg

Agenda

  • Exchange 2007 – A quick intro

  • Planning for Exchange 2007

  • Designing Exchange 2007

  • Migrating to Exchange 2007

  • Documentation

  • Summary


Summary l.jpg

Summary

  • Prepare!

  • Planning

  • Discovery

  • Requirements

  • Testing

  • Sizing

  • Server Placement

  • Communication


Any questions l.jpg

Any Questions???


  • Login