EXL305. Section 1 What’s the Same / What’s New / What’s Different in Exchange 2010 (background on where things will trip you up during the transition.

Slides:



Advertisements
Similar presentations
Painless Transitions from Microsoft Exchange 2003 to Microsoft Exchange 2007 J. Peter Bruzzese Co-Founder of ClipTraining MCSE/MCT/ MCITP: Messaging for.
Advertisements

Minimising IT costs, maximising operational efficiency minimising IT costs, maximising operational efficiency Balance.
Daniel Kenyon-Smith UC Consultant – MCS UK. Optimize for Software + Services Deployment Flexibility Continuous Availability Simplify Administration Manage.
Exchange Server 2010 Upgrade and Deployment Meelis Nigols koolitaja IT Koolitus.
Overview of Server Roles in Exchange Server 2010 In Exchange Server 2010, servers are installed with specific functional roles: Mailbox Server role Edge.
Module 12 Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010.
Welcome to the Exchange 2013 Webcast Deployment & Coexistence.
F5 solution for Microsoft Exchange. 2 Exchange 2010 Architecture External SMTP servers Edge Transport Routing and AV/AS Phone system (PBX or VoIP) Client.
MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter 14 Upgrading to Exchange Server 2003.
F5 Solution for Microsoft Exchange 2010 James Hendergart Business Development Manager Helen Johnson Solution Engineer.
Getting Started with Exchange Server 2007 Simple Installation, Setup and Administration Scenarios Johann Kruse: 2 nd November 2006.
NHSmail: Technology Refresh 26 th February 2008 Mike Dolan NHSmail Migration Manager.
Installing Exchange 2010 IT:Network:Applications.
Jaap Wesselius May 27, 2009 Exchange Server 2010 what’s new?
DBI405. Agenda Reporting Services Scale Out Architecture Report Catalog Best Practices Scale Out Deployment Best Practices Performance Optimization.
Deploying Microsoft® Exchange Server 2010
IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.
Exchange 2010 Overview Name Title Group. What You Tell Us Communication overload Globally distributed customers and partners High cost of communications.
Exchange 2007 Overview. What Will We Cover? New features in Microsoft® Exchange 2007 The Exchange Management Console The Exchange Management Shell New.
Implementing High Availability
Scott Schnoll Principal Technical Writer Microsoft Corporation UNC313.
EXC11: Migrating to Exchange 2010 from Exchange 2003 Jim McBee Ithicos Solutions LLC
Scott Schnoll Principal Technical Writer Microsoft Corporation Session Code: UNC3.
Exchange 2010 Project Presentation/Discussion August 12, 2015 Project Team: Mark Dougherty – Design John Ditto – Project Manager Joel Eussen – Project.
Exchange Deployment Planning Services
EXL302-R. Storage Management Balance mailbox size demands with available storage resources Reduce the proliferation of.PST files stored outside of IT.
TechEd /20/2017 2:02 AM © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks.
Martin Coetzer Technical Consultant Microsoft Session Code: UNC310.
Managing Client Access
Module 4 Managing Client Access. Module Overview Configuring the Client Access Server Role Configuring Client Access Services for Outlook Clients Configuring.
EXL319. *Baseline for 80,000 user pool with 8 FEs and 1 BE Lync Server 2010 Capacity Calculator released.
EXL311: Exchange Server 2013 Architecture Deep Dive Scott Schnoll Microsoft Corporation EXL311.
AVAILABILIT Y Cloud = Datacenter N2H LOB Basic needs Think in ROLES.
Chris Goosen Infrastructure Consultant Kloud Solutions.
Securing Microsoft® Exchange Server 2010
IT:Network:Applications.  How messaging servers work  Initial tips for success Exchange management  Server roles  Exchange Server Management  Message.
Module 2 Designing Microsoft® Exchange Server 2010 Integration with the Current Infrastructure.
Exchange Exchange Server Role Architecture in Exchange Server 2013 Server roles in Exchange Server 2013: Client Access Server Mailbox Server Client.
Click to edit Master title style TechNet goes virtual ©2009 Microsoft Corporation. All Rights Reserved. TechNet goes virtual Upgrading and Coexisting with.
Module 9 Configuring Messaging Policy and Compliance.
Scott Schnoll Principal Technical Writer Microsoft Corporation Session Code: UNC307.
EXL321. Lync 2010 Planning tool+ Planning guides+ * new in LS significant enhancements in LS 2010.
Scott Schnoll m Microsoft Corporation.
Exchange Server versionForest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM4397 Exchange 2000 Server SP34406.
Module 4 Planning and Deploying Client Access Services in Microsoft® Exchange Server 2010 Presentation: 120 minutes Lab: 90 minutes After completing.
UPGRADING TO EXCHANGE 2010 Colin Lee MCM/A – Exchange Practice Executive – UC Dell SESSION CODE: EXL310 (c) 2011 Microsoft. All rights reserved. Sofiane.
Appendix A UM in Microsoft® Exchange Server 2010.
EXC303 - Exchange Server 2007 SP1 Overview Martin Coetzer Technical Consultant Microsoft.
Module 3 Planning and Deploying Mailbox Services.
Module 6: Managing Client Access. Overview Implementing Client Access Servers Implementing Client Access Features Implementing Outlook Web Access Introduction.
Module 12 Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010.
Module 11 Upgrading to Microsoft ® Exchange Server 2010.
Exchange Server 2013 Architecture
AD Web browser Outlook (remote user) Mobile phone Line of business application Outlook (local user) External SMTP servers Exchange Online Protection.
Read/understand sizing, scalability, capacity guidance Documentation on technet, Exchange team blog, etc. Collect data on existing deployment.
Module 2: Installing Exchange Server Overview Introduction to the Exchange Server 2007 Server Roles Installing Exchange Server 2007 Completing the.
Exchange Server 2007 Deployment and Migration Strategies Nireshen Beerbul
Scott Schnoll m Microsoft Corporation.
Exchange Server versionForest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM4397 Exchange 2000 Server SP34406 Exchange.
Implementing Microsoft Exchange Online with Microsoft Office 365
Jeff Mealiffe Sr. Program Manager Microsoft Corporation SESSION CODE: UNC301 Evan Morris Sr. Systems Engineer Hewlett-Packard.
Exchange Hybrid: Deployment, best practices, and what’s new
BE-com.eu Brussel, 26 april 2016 EXCHANGE 2010 HYBRID (IN THE EXCHANGE 2016 WORLD)
Information explosion 1.4X 44X Internet AD Web browser Outlook (remote user) Mobile phone Line of business application Outlook (local user) External.
Deployment on your terms Hybrid Exchange deployment on your terms On-premises.
Office 365 Help Desk Troubleshooting Guide
Autodiscover is Hero of Exchange Motherland!
Tech·Ed North America /11/ :55 AM
Tech Ed North America /15/2019 2:35 PM Required Slide
Enterprise Topography
Presentation transcript:

EXL305

Section 1 What’s the Same / What’s New / What’s Different in Exchange 2010 (background on where things will trip you up during the transition process)

64-bit E2010  Reduce IO/ sec req’d by 70%  ¼ the disk  4x more users  Large inboxes  Still uses EDB database structure (not SQL as once rumored)  No more.STM files (that were in Exchange 2003)  2 billion log files  E log (similar to Exchange 2007) When working with x64-bit  Need to closely review add-ins to make sure they support 64-bit (anti-virus, fax utils, gateway products, etc)  RAM is critical (lots works better on mailbox servers, but diminishing return on CAS and Hub Transport…)

Enterprise Network External SMTP servers Mailbox Storage of mailbox items Edge Transport Routing & AV/AS Unified Messaging Voice mail & voice access Phone system (PBX or VOIP) Client Access Client connectivity Web services Hub Transport Routing & Policy Web browser Outlook (remote user) Mobile phone Outlook (local user) Line of business application

DB1 Front End Server NodeB (passive) Outlook OWA, ActiveSync, or Outlook Anywhere San Jose Dallas Standby Cluster Third-party data replication needed for site resilience Complex site resilience and recovery Clustering knowledge required DB2 DB3 DB4 DB5 DB6 Failover at Mailbox server level DB1 DB2 DB3 Clustered Mailbox Server had to be created manually NodeA (active)

DB1 Client Access Server NodeB (passive) SCR Outlook OWA, ActiveSync, or Outlook Anywhere San Jose Dallas Standby Cluster No GUI to manage SCR Complex activation for remote server / datacenter Clustering knowledge required DB2 DB3 DB4 DB5 DB6 DB1 DB2 DB3 DB4 DB5 DB6 Failover at Mailbox server level DB1 DB2 DB3 Clustered Mailbox Server can’t co-exist with other roles NodeA (active) CCR

DB3 DB4 DB5 Client Access Server Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 Mailbox Server 6 Mailbox Server 4 Dallas San Jose Mailbox Server 5 DB5 DB1 Failover managed by/with Exchange Database level failover Easy to extend across sites All clients connect via CAS servers DB1 DB3 DB5 DB2 DB1 DB4 DB1 DB2 DB3

“Integrating Apple Macs, iPads, iPhones into a Windows / Active Directory based environment” – (May 11, 2011 posted content) “Authoritative Guide to Exchange Calendaring” – (July 20, 2010 posted content)

Section 2 Migration Process Best Practices

Exchange 2007 Decommission Order: 1. Mailbox server 2. Unified Messaging server 3. Hub Transport server 4. Client Access server 5. Edge Transport server Exchange 2003 Decommission Order: 1. Mailbox server 2. SMTP 3. Front End

Proxy Internet Facing AD Site Internal AD Site Decommission old servers Upgrade Internal sites NEXT Upgrade Internet-facing sites FIRST Upgrade servers to SP2 1 Move Mailboxes Internet Internet hostname switch Unified Messaging switch SMTP switch Move Infra Pointers 4 SSL cert purchase End users don’t see this hostname Used when new CAS tell clients to talk to legacy environments Legacy hostnames for old FE/CAS 3 Start small Gradually add more servers to support scale Deploy E2010 Servers 2 E200x Servers TIP!

Generates custom instructions on how to install or upgrade to Exchange 2010 Help determine the cause of performance, mail flow, and database issues Verify Internet-facing services are set up and configured properly Determine overall health of Exchange system and topology

Domain Controller Domain Controller Directory Replication File Replication Service Directory objects (users, computers, etc.) SYSVOL (logon scripts, policies, etc.) Use ReplMon (in the Windows Support Tools on Windows CD) to validate replication Also use frsdiag.exe to confirm FRS replication FRS replicates the SYSVOL, contains NETLOGON share, stores logon scripts and system policies, contains Group Policies in separate folders AD Health Check Guide ($9.95 / 104-pages / step-by-step guide):

Setup /PrepareSchema, /PrepareAD, /PrepareDomain Setup /PrepareLegacyExchangePermissions

Clients and SMTP servers Autodiscover /autodiscover E2003/E2007 services

Deploying SSL Certificates Note

New-ExchangeCertificate -GenerateRequest -Path c:\certificates\request.req -SubjectName “c=US, o=contoso Inc, cn=mail1.contoso.com” -DomainName mail.contoso.com, autodiscover.contoso.com, legacy.contoso.com -PrivateKeyExportable $true

Deploying Exchange 2010 Topology decisions—CAS load balancing Note

Transition Planning ActiveSync – 2003/2007

Activesync Error

Transition Planning Offline Address Book (OAB)

Transport Roles Exchange 2010 resiliency improvements

Migration of Bridgehead / Hub Transport Add Exchange 2010 Hub Transport servers in addition to existing E2003 Bridgehead / E2007 HT servers

Transition Planning Disabling Link State (for Exchange 2003 > 2010 Transitions)

Step 5: Switch Internet submission to Edge 2010 SMTP Transport Upgrade E2003 Bridgehead E2003 Back-End E2010 HUB E2010 MBX E2007 HUB E2007 MBX E2010 Edge E2007 Edge Internet SMTP Servers Step 1: Upgrade existing E2003 and E2007 servers to SP2 Step 2: Install HUB and MBX 2010 Step 3: Switch Edgesync +SMTP to go to HUB2010 Step 4: Install Edge 2010

CAS / HUB / MAILBOX 1 CAS / HUB / MAILBOX 2 Member servers of DAG can host other server roles DB2 2 server DAGs, with server roles combined or not, should use RAID 8 processor cores recommended with a maximum of 64GB RAM UM role not recommended for co- location

Migration of Mailboxes to E2010 Build Exchange 2010 Mailbox Server Role Systems (including DAG replica servers (if desired) )

Transition Planning Upgrade LDAP to OPATH

Client Mailbox Server 1Mailbox Server 2 Client Access Server Online Move Mailbox Minimal User Disruption

Unified Messaging / Unified Communications Integrating Exchange 2010 to Lync 2010: Integrating Exchange 2010 SP1 to OCS 2007: exchange-server-2010-sp1-owa/

Public Folders

Retiring Exchange 2003 / 2007

Transition Planning Removing the Last Exchange 2003 / 2007 Server from Org

SharePoint 2010 User Profile Sync Service: “outlook pictures” Mail Tips Luciana Ramos;

Things to Remember

Resources Sessions On-Demand & CommunityMicrosoft Certification & Training Resources Resources for IT ProfessionalsResources for Developers Connect. Share. Discuss.

Scan the Tag to evaluate this session now on myTechEd Mobile