Workshop Agenda

Module 1 - Overview of Exchange 2010

Module 2 - Exchange Server 2010 Prerequisites
Module 3 - Exchange Deployment Guidelines
Module 4 - Upgrading Exchange roles
Module 5 - Additional Upgrade Tasks

1
 Exchange Server 2010 Prerequisites – Overview

Hardware Requirements
Server Role Memory / Processor Recommendations
Hardware Virtualization Support
Operating System Requirements & Prerequisites
Active Directory Requirements
Preparing the Legacy Exchange Organization
Upgrade/Transition Support
Support for Microsoft Transporter Suite for Lotus Domino
Exchange Server 2010 Roles & Role Co-Existence
Unified Messaging Server Role Prerequisites

2
 Hardware Requirements

Component Requirement
Processor x64 architecture that supports Intel 64 architecture (formerly known as Intel EM64T)
AMD processor that supports the AMD64 platform
Intel Itanium IA64 processors are not supported
Min. Intel Pentium or compatible (the number or cores required depends on roles installed)

Memory Minimum: 4 gigabytes (GB) of RAM (depending on Sever Role(s) installed)

Paging file size Equal to the amount of RAM in the server plus 10 MB
Disk Space Min. 1.2 GB on the drive on which you install Exchange Server 2010
Additional 500 MB for each Unified Messaging (UM) language pack that you plan to install
200 MB of available disk space on the system drive
Min. 500 MB for queue database on an Edge or Hub Server

Drive DVD-ROM drive, local or network accessible

Display 1024 x 768 or higher resolution
Other Keyboard and compatible pointing device
File format Disk partitions formatted as NTFS file systems, which applies to the following partitions:
System partition
Partitions that store Exchange binary files
Partitions containing database and transaction log files
Partitions containing other Exchange files

3
 Hardware Virtualization Support (1)

Windows Server 2008 (R2) Hyper-V or any third-party

hypervisor (validated by Windows Server Virtualization
Validation Program)
Supported guests: Exchange 2010 and Exchange 2007 SP2
(on Windows Server 2008 or newer)
Architect the environment as if physical
Only management software allowed on physical root
machine
Exchange Storage spindles separate from the Guest OS
Virtual Hard Drive storage.
4
 Hardware Virtualization Support (2)

Storage: VHD (fixed size), SCSI pass-through or iSCSI

Only fixed disks supported (no dynamic, or differencing disks)
Hyper-V Snapshots of Exchange guest is not supported.
All Exchange server roles supported, except UM
In a Hyper-V environment, each fixed VHD must be less than
2,040 GB
DAGs are supported in hardware virtualization environments
provided that the virtualization environment doesn't employ
clustered root servers

5
 Operating System Requirements

E2010 an only be installed on 64 bit hardware running

Windows Server 2008 (X64) SP2 or R2.
Does not support
• Windows Web Server 2008 X86/X64
• Windows Server 2008 Enterprise X86/X64 Core installations
Component Requirement
OS for Exchange Server on a 64-bit edition of Windows Server 2008 Standard (R2
computer with 64-bit processor or RTM with Service Pack 2 installed)
Or
64-bit edition of Windows Server 2008 Enterprise
(R2 or RTM with Service Pack 2 installed)

OS for Exchange Management Tools Windows Vista with Service Pack 2 or later or
on a computer with 64-bit processor Windows 7 for Exchange management tools only
installation

7
 Operating System Prerequisites - Windows Server 2008
SP2

Windows Server 2008 AD Remote Management Tools

Microsoft .NET Framework 3.5 SP1
Windows PowerShell V2
Internet Information Services (IIS)
Exchange Server 2010 Role Specific Prerequisites
• Installing Exchange 2010 Hub Prerequisites
• Installing Exchange 2010 Edge Prerequisites
• Installing Exchange 2010 CAS Prerequisites
• Installing Exchange 2010 Mailbox Prerequisites
• Installing Exchange 2010 Unified Messaging Prerequisites

8
 Operating System Prerequisites - Windows Server 2008
R2

Internet Information Services (IIS)

Exchange Server 2010 Role Specific Prerequisites
• Installing Exchange 2010 Hub Prerequisites
• Installing Exchange 2010 Edge Prerequisites
• Installing Exchange 2010 CAS Prerequisites
• Installing Exchange 2010 Mailbox Prerequisites
• Installing Exchange 2010 Unified Messaging Prerequisites
Remote Management Tools, .NET Framework 3.5 and
Windows PowerShell V2 are installed during initial Setup

16
 Active Directory Requirements (1)

Schema Master
• Windows Server 2003 SP1 or above
Forest Function Level
• Windows 2003 Mode or higher
Domain Controllers
• Each domain planned for E2010 must contain Windows Server
2003 SP1 or above (Standard, Enterprise, 32 or 64 Bit)
Domain Function level
• Each domain planned for E2010 must be in Windows 2003
Native mode

18
 Active Directory Requirements (2)

Global Catalog Server

Each domain planned for E2010 must contain Windows Server 2003
SP1 or above (Standard, Enterprise, 32 or 64 Bit)
Read-only Domain Controllers / Read-only Global Catalog
Servers
Exchange Setup Active Directory Switches
• Setup /PrepareLegacyExchangePermissions
• Setup /PrepareSchema
• Setup /PrepareAD
• Setup /PrepareDomain or-Setup /PrepareAllDomains

19
 Exchange 2010 SP1 Setup

Additional OS Hotfix requirements

• Several hotfixes needed:
http://technet.microsoft.com/en-us/library/bb691354.aspx
SP1 contains additional Schema Update (over RTM)
SP1 is a full install DVD
OS prerequisites can be installed during Exchange setup
• select /InstallWindowsComponents (unattended)
• GUI:

Exchange 2010 SP1 FAQ and Known Issues

• http://msexchangeteam.com/archive/2010/09/01/456094.aspx

21
 Setup topics of interest

Installation Guide Templates available:

• http://technet.microsoft.com/en-us/library/ff622322.aspx
After running E2010 Setup /PrepareAD no E2007 supported
• Third-party/in-house developed applications   
• Coexistence or migration requirements   
Exchange 2010 introduced into Exchange 2003 org  it will be
no longer possible install Exchange 2007 server afterwards.
Mailflow issues with E2003 when SMTP address in two
recipient policies – one authoritative, one non-authoritative
• http://msexchangeteam.com/archive/2008/09/05/449764.aspx

22
 Preparing the Legacy Exchange Organization

Coexistence Support
Legacy Exchange Service Pack Requirements
Upgrade/Migration Support
Support for Microsoft Transporter Suite for Lotus Domino

23
 Coexistence Support

Exchange Environment Supported Unsupported

Pure Exchange Server 2010 X
Mixed Exchange Server 2010 / Exchange X
Server 2007 SP2
Mixed Exchange Server 2010 /Exchange X
Server 2003 SP2
Mixed Exchange Server 2010 /Exchange X
Server 2003 RTM or SP1 / Exchange Server
2007 RTM or SP1
Mixed Exchange Server 2010 /Exchange 2000 X
or earlier
Mixed Exchange Server 2010 / Exchange X
Server 2007 SP2 /Exchange Server 2003 SP2

24
 Legacy Exchange Service Pack Requirements

Exchange Server 2007 Service Pack 2 or later

Exchange 2003 Service Pack 2

25
 Upgrade/Coexistence Support

No in place upgrade from any previous version of Exchange

After Exchange 2010 is installed, customers can move
mailboxes to the new environment
Existing messaging system In-place server Transition to a new Migrate to Exchange Server
upgrade to Exchange Exchange Server 2010
Server 2010 2010 organization
Exchange Server 5.5  Not supported Not supported Supported, by upgrading first to
E2003, then to E2010

Exchange 2003 SP2 Not supported Supported Supported

Exchange 2000 Not supported Supported Supported, by upgrading first to

E2003 or 2007, then to E2010

Mixed Exchange 2003 and Not supported Supported Supported, by upgrading first to

Exchange 2000 organization pure E2003, then to E2010

Exchange 2007 SP2 Not supported Supported Supported

26
 Support for Microsoft Transporter Suite for Lotus
Domino

Tools for migrations from both Lotus Domino Servers, and

generic IMAP/POP sources
Exchange Server 2010 does not support the installation of
the Transporter suite on any 2010 server role
Exchange 2010 organizations that undergo
acquisition/merger with Lotus Domino organizations will have
to use third party tools for migration/coexistence
• Exchange 2010 offers no support for the Transporter Suite
• Maintain E2007 if Transporter Suite is required

27
 Exchange Server 2010 Roles & Role Co-Existence

Same Server roles included in Exchange 2007

• Mailbox Server, Client Access Server, Unified Messaging,
Server, Hub Transport Server, Edge Transport Server
Edge role cannot coexist with any other role
CAS, Hub, Mailbox and Unified Messaging server role can
coexist in any combination.
Recommended deployment Order (separate computers):
1. Client Access server role
2. Hub Transport server role
3. Mailbox server role
4. Unified messaging server role

28
 Unified Messaging Server Role Prerequisites

Before installing the Exchange 2010 UM, the following server

roles must exist in the same Active Directory site:
• Exchange 2010 Mailbox Server
• Exchange 2010 Hub Transport Server
• Exchange 2010 Client Access Server

It is unsupported to deploy Exchange 2010 UM into an Active

Directory site that contains only Exchange 2007 server roles
In migration scenarios, all Exchange 2007 server roles must
remain available in the Active Directory site until the
mailboxes of all UM enabled users have been moved to
Exchange 2010
30
 Configuring Exchange Without Internet Access

Exchange .net based Services are Cert enabled

Windows (CryptoAPI) verifies certificate signature
• uses local cache
• If not in cache, uses information on cert to download
Affects installation process of Service Packs & Rollups
Affects startup behaviour of services
Follow http://msexchangeteam.com/archive/2010/05/14/454877.aspx
and adjust registry settings accordingly

31
 Pre-Deployment Analyzer (ExPDA)

Performs overall topology

scan
ExPDA:
Focus only on topology
Readiness
ExBPA (in E2010 Setup):
Focus on local computer
readiness

32
 Terms of Use

© 2010 Microsoft Corporation. All rights reserved.

Information in this document, including URL and other Internet Web site references, is subject to change without notice.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people,
places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain
name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright
laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced,
stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical,
photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
For more information see Microsoft Copyright Permissions at http://www.microsoft.com/permission
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject
matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this
document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
The Microsoft company name and Microsoft products mentioned herein may be either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned
herein may be the trademarks of their respective owners.
THIS DOCUMENT IS FOR INFORMATIONAL AND TRAINING PURPOSES ONLY AND IS PROVIDED "AS IS" WITHOUT
WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.

33