EXC16 - Migrating to Exchange Server 2010

Document Sample
EXC16 - Migrating to Exchange Server 2010 Powered By Docstoc
					        Migrating to
    Exchange Server 2010

         Michael B. Smith
      The Essential Exchange
michael@TheEssentialExchange.com
Agenda

• Change in Session Title due to lack of
  surety in Exchange RTM/GA – in
  February!
• Prerequisites
  Preparation
• P        ti
• Process
• Deployment Assistant
Who am I?

            B.
• Michael B Smith – remember the B!
• Six year Exchange MVP
  Consultant i E h
• C                         Active Directory,
          lt t in Exchange, A ti Di t
  and Operational Best Practices
• http://TheEssentialExchange.com/
• Author, blogger, speaker
          ,    gg , p
Prerequisites – Permissions #1

• Schema Update requires:
  ●   Enterprise Admins
  ●   Schema Admins
  ●   (May have been applied by Exch 2007 sp2)
  After h         d t       h    Ed
• Aft schema update, each non-Edge
  server requires Organization Management
       i i
  permissions (USG)
• Edge server requires local administrator
Prerequisites – Permissions #2

• Configuring the initial servers requires:
  ●   Local administrator (Certificates, local DNS)
  ●   DNS Admin (domain DNS)
  ●   Server Management (virtual directories)
  ●                                 (OAB,
      Organizational Management (OAB Send
      Connectors, Move Mailbox, etc.)
Prerequisites – Directory Servers

• Schema Master - 2003 sp1 or higher
• Global catalog
  ●   Each      it   h       install   Exchange
      E h AD site where you i t ll an E h
      2010 server must have at least one GC at
      2003 sp1 or higher
• Forest Functional Level – Server 2003
  Domain F
• D            ti   l Level – S
       i Functional L     l Server 2003
Prerequisites - Hardware

                   64 bit
• Exchange 2010 is 64-bit ONLY
  ●   No 32-bit management tools
  ●      32 bit
      No 32-bit test version
• Must use NTFS on all disks
• Memory between 4 GB and 64 GB
  ●   2-10 MB per mailbox increase
• As always, the fastest processor you can
  afford
Prerequisites – Software #1

• Windows Server 2008 service pack 2 x64
• Windows Server 2008 R2 x64
  ●   The i t ll is   i      Server 2008 R2
      Th install i easier on S
• Microsoft Office FilterPack x64
  ●   Client Access Server and Mailbox Server
      g
• Management tool workstations:
  ●   Vista x64
  ●   Windows 7 x64
Prerequisites – Software #2

• Typical install (HT + CAS + MB)
    ●   Servermanagercmd –ip Exchange-Typical.xml
• CAS only
    ●   ServerManagerCmd -ip Exchange-CAS.xml
• Hub only
    ●   ServerManagerCmd -ip Exchange-HUB.xml
•
Prerequisites – Software #3

• Mailbox only
  ●   ServerManagerCmd -ip Exchange-MBX.xml
• UM and Edge
  ●   Exchange-UM.xml and Exchange-Edge.xml
• Restart when SMC is complete
• On CAS (and Typical) configurations:
           (    yp )        g
  ●   sc config NetTcpPortSharing start= auto
Prerequisites – Software #4

                 (non R2):
• On Server 2008 (non-R2):
  ●   BITS 4.0 upgrade
  ●              20
      PowerShell 2.0 upgrade
  ●   .NET Framework 3.5 SP1 installation
       f the b    is   t f Server 2008 R2
• All of th above i part of S          R2,
  which is why “R2 is easier”
Prerequisites – Exchange 2003

• IF you are going to run 2003 and 2010 at
  the same time
• AND you want a single namespace for
  OWA and RPC/HTTP during coexistence
• THEN you must h            Exchange 2003
                   t have an E h
  front-end server
• If you don’t currently have one, then you
  must add one
Prerequisites - Decisions

• Decide on the external name for all
  Exchange services, e.g.:
  ●   mail.example.com
      mail example com
  ●   exchange.example.com
  ●   owa example com
      owa.example.com
• Note that all Exchange services, except
  A t di           ill be    id d through thi
  Autodiscover, will b provided th      h this
  single name (via virtual directories)
Prerequisites

  Done.
• Done

  Whew.
• Wh

• Note: we have not discussed design.
      y    g          just what has to be
  Everything above is j
  done to prepare the infrastructure.
First Server - Installation

                                roles,
• If you are separating server roles then the
  first server should be the CAS.
                                    roles,
• If you are not separating server roles then
  the first server should contain the CAS
  role
• If you are going to provision CAS arrays,
  then       t th                    th fi t
  th create the array as soon as the first
  server is installed
First Server – SSL Certificates

• Obtain a certificate that contains:
  ●   mail.example.com (or whatever you picked)
  ●   autodiscover.example.com
      autodiscover example com
  ●   legacy.example.com (will be used to access
      the Exchange 2003 environment)
• Install it and assign services to it
  Note:       ild   d    tifi t      k fine,
• N t a wild-card certificate works fi
  except with POP and IMAP.
First Server – Outlook Anywhere

• Enable Outlook Anywhere on the server

               i      ild d      tifi t
• If you are using a wildcard certificate,
  update the CertPrincipalName on the
          Outlook
  EXPR O tl k providerid
  (msstd:*.example.com) – use the Set-
  OutlookProvider PowerShell cmdlet
  O tl kP id P            Sh ll     dl t
First Server – Virtual Directories

• For each virtual directory exposed by the
  CAS, configure that virtual directory within
                 EMC.
  either EMS or EMC Especially note the
  ExternalURL (mail.example.com) and the
                       (legacy.example.com)
  Exchange2003URL (legacy example com)
• OAB and EWS Vdirs use only EMS
  Test    h      i b       i
• T t each service by using:
  ●   http://TestExchangeConnectivity.com
Next role – Hub Transport

            standalone,
• If HT is standalone install role on
  dedicated server
          co exist      CAS,
• If will co-exist with CAS then add role to
  existing server
          d ’t h         Ed
• If you don’t have an Edge server, ththen
  allow “Anonymous users” on default
        i           t t      i I t      t
  receive connector to receive Internet e-
  mail
• Configure Accepted Domains
Configure Exchange 2003

• Install the hotfix described at KB 937031
  ●   Event ID 1036 is logged on an Exchange
      2007 server that is running the CAS role when
      mobile devices connect to the Exchange 2007
      server to access mailboxes on an Exchange g
      2003 back-end server
          g
• Set Integrated Windows Authentication on
  the ActiveSync virtual directory on all 2003
          (
  servers (use ESM for this) )
Configure DNS

                    A
• Create address “A” records for
  legacy.example.com to point to the
                   front end
  Exchange 2003 front-end server
• Change/create address “A” records for
  mail example com to point to the new CAS
  mail.example.com
  server
  Update firewall rules t allow/enforce th
• U d t fi     ll l to ll / f           the
  above
Next role - Mailbox

           standalone,
• If MB is standalone install role on
  dedicated server

• If will co-exist with CAS or HT, then add
     l to i ti
  role t existing server

• Note: DAG servers can host more than a
  single role
     g
Configure Offline Address Books

                  defined,
• For each OAB defined change the
  generation server to a Exchange 2010
  server
• Enable both web-based distribution and
  public-folder
  public folder based distribution for each
  OAB
Configure Send Connectors

• On each hub transport that will send e-e
  mail to the Internet, create an Internet
  send connector and test it
• On each Exchange 2003 server that had a
         connector,
  SMTP connector delete it (and verify that
  email is still flowing)
Replicate Public Folders

• Use PFDAVAdmin on Exchange 2003 side
  to add Exchange 2010 mailbox servers as
  replication partners
• Use ExFolders on Exchange 2010 side to
  do the same thing
• Use Get-PublicFolderStatistics cmdlet to
  d t     i    h       li ti is      t
  determine when replication i current
• Do system and user public folders!
Move Mailboxes

                                      cmdlet,
• Using the MoveRequest wizard or cmdlet
  move the mailboxes to a Exchange Server
                  server.
  2010 mailbox server
• If the clients are using Outlook 2007 or
             2010,
  Outlook 2010 they will experience no
  outage.
Finishing Up…

• Enter product keys
• Remove Exchange 2003 replicas from
  public folders (user and system)
• Remove Exchange 2003
• (optional) Configure High Availability in
  your Exchange 2010 environment
Deployment Assistant

• Released concurrent with Exchange 2010
  on Monday was the Exchange
  Deployment Assistant
• It can walk you through many standard
  scenarios required for migration to
  Exchange 2010 from 2003 or 2007
  http://technet.microsoft.com/exdeploy2010
• htt //t h t i         ft    / d l 2010
• ….it’s a work in progress
Summary

• Moving to Exchange 2010 is fairly simple

  Certainly       difficult than   to
• C t i l no more diffi lt th 2003 t
  2007

       q        great deal of up-front planning
• It requires a g              p       p      g
  and decision making.
Final Words

     you’ve             session,
• If you ve enjoyed the session consider
  checking out my book:




     p               pp
• http://snurl.com/45ppf

• Thanks for coming!
Your Feedback is Important

Please fill out a session evaluation form
 and either put them in the basket near
                     p
     the exit or drop them off at the
      conference registration desk.


              Thank you!