Exchange Server versionForest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM4397 Exchange 2000 Server SP34406.

Slides:



Advertisements
Similar presentations
5 server roles Tightly-coupled in terms of versioning functionality user partitioning geo-affinity Previous Server Role Architecture Internal Network.
Advertisements

MEC /5/2017 1:13 PM © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks.
Public folders in O365 High availability, data redundancy, and low cost storage thru DAGs Multi-master replication simplified and replaced.
Exchange 200X to 2010 Migration Adam Farage Premier Field Engineering blogs.technet.com/b/theexchangeguy.
Exchange Server 2010 Upgrade and Deployment Meelis Nigols koolitaja IT Koolitus.
Scott Schnoll Exchange Server 2013 Site Resilience.
Module 12 Upgrading from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010.
Welcome to the Exchange 2013 Webcast Deployment & Coexistence.
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.
 They’re available in Exchange Online  Great for simple sharing and distribution list archiving in Outlook  Site Mailboxes and SharePoint are better.
Part 2 Transport Unified Messaging Managed Availability.
4/16/2017 © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks.
Pre-Release Programs Be first in line! Exchange & SharePoint On-Premises Programs Customers get: Early access to new features Opportunity to shape features.
Jaap Wesselius May 27, 2009 Exchange Server 2010 what’s new?

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.
Implementing High Availability
EXC11: Migrating to Exchange 2010 from Exchange 2003 Jim McBee Ithicos Solutions LLC
Configuring Hybrid Exchange the Easy Way
Overview of Exchange 2013 Architecture Transport components shipping with Exchange 2013 Mail Routing Scenarios Transport High Availability SMTP Client.
AD Web browser Outlook (remote user) Mobile phone Line of business application Outlook (local user) External SMTP servers Exchange Online Protection.
MEC /19/2017 7:51 PM © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks.
Exchange Deployment Planning Services
Instructions You must bring your own laptop, your presentation and a power supply Technical staff is present in all to assist with network, audio and video.
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.
Introduction 4 FeatureSimpleHybrid Mail routing between on-premises and cloud (recipients on either side) Mail routing with shared namespace (if desired)
Managing Client Access
Eesti. Baltimaad. Põhja Euroopa. Priit Timpson Atea teenuste osakond.
EXL311: Exchange Server 2013 Architecture Deep Dive Scott Schnoll Microsoft Corporation EXL311.
Office 365 Exchange Online Migration Overview. Catapult Overview  An independent wholly owned subsidiary of CSI since 2013  Privately founded in 1993,
AVAILABILIT Y Cloud = Datacenter N2H LOB Basic needs Think in ROLES.
Chris Goosen Infrastructure Consultant Kloud Solutions.
Topic Of This Hour Exchange 2013: Database Availability Group Exchange 2013: Modern Public Folders Dec 18, 2013 Timing for the different Geography: 5:00.
Securing Microsoft® Exchange Server 2010
User CAS DAG For any given mailbox’s connectivity, the user is always served by the server that hosts the active database copy Each CAS determines.
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.
MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter Two Installing and Configuring Exchange Server 2003.
Scott Schnoll m Microsoft Corporation.
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.
Transport components shipping with Exchange 2013 Overview of Exchange 2013 Architecture Architectural improvements made in Transport History, Challenges,
Modern Public Folders Architecture Architecture Public folders are based on the mailbox architecture Hierarchy is stored in all public folder.
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
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
Exchange Server versionForest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM4397 Exchange 2000 Server SP34406 Exchange.
ProductExchange 2013 SP1Exchange 2013 RTMExchange 2010 SP3Exchange 2007 SP3 Outlook 2013 SP1 or later MAPI over HTTP Outlook Anywhere Outlook Anywhere.
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.
Microsoft Exchange Server 2013 Security Mick Tomlinson– Technical Instructor New Horizons.
Appendix B Advanced Topics in Exchange Server 2010.
VIRTUAL SERVERS Chapter 7. 2 OVERVIEW Exchange Server 2003 virtual servers Virtual servers in a clustering environment Creating additional virtual servers.
Deployment on your terms Hybrid Exchange deployment on your terms On-premises.
Office 365 Migration – Understanding Migrations Part 1
Autodiscover is Hero of Exchange Motherland!
Implementing Exchange Server 2013
Deploy Microsoft Exchange Server 2016
StoredTech Evolution from Project Pitfalls to Higher Profits
Office 365 – Understanding Migrations: Hybrid migrations
TechEd /17/ :40 PM © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered.
Exchange 2013 Upgrade and Coexistence
Implementing Exchange Server 2013
TechEd /15/2019 6:07 AM © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks.
Tech Ed North America /15/2019 2:35 PM Required Slide
Presentation transcript:

Exchange Server versionForest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM4397 Exchange 2000 Server SP34406 Exchange Server 2003 RTM6870 Exchange Server 2003 SP16870 Exchange Server 2003 SP26870 Exchange Server 2007 RTM10637 Exchange Server 2007 SP Exchange Server 2007 SP Exchange Server 2007 SP Exchange Server 2010 RTM14622 ExchangeServer 2010 SP Exchange Server 2010 SP Exchange Server 2010 SP Exchange Server Exchange Server 2013 CU Exchange Server 2013 CU215281

AuthN, Proxy, Re-direct AuthN, Proxy, Re-direct Protocols, API, Biz-logic Protocols, API, Biz-logic Assistants, Store, CI Exchange 2010 Architecture AuthN, Proxy, Re-direct AuthN, Proxy, Re-direct Store, CI Protocols, Assistants, API, Biz-logic Exchange 2013 Architecture Client Access Mailbox Client Access Hub Transport, Unified Messaging Mailbox Hardware Load Balancer L4 LB L7 LB

SP3 E2010 CAS E2010 HUB E2010 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 Servers SP3 1. Prepare Install Exchange 2010 SP3 across the ORG Validate existing Client Access using MCA and ExRCA and built-in Test cmdlets Prepare AD with E2013 schema 4. Switch primary namespace to Exchange 2013 CAS E2013 fields all traffic, including traffic from Exchange 2010 users Validate using MCA and ExRCA 5. Move Mailboxes Build out DAG Move E2010 users to E2013 MBX 6. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers SP3 E2013 CAS E2013 MBX 3. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers

RU E2007 SP3 CAS E2007 SP3 HUB E2007 SP3 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2007 SP3 Servers RU 1. Prepare Install Exchange 2007 SP3 + RU across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS Validate using MCA and ExRCA 6. Move Mailboxes Build out DAG Move E2007 users to E2013 MBX 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers RU E2013 CAS E2013 MBX 3. Create Legacy namespace Create DNS record to point to legacy E2007 CAS 4. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers configured with legacy namespace, E2013 namespace and Autodiscover namespace Deploy certificates on Exchange 2007 CAS legacy.contoso.com

SP/RU E2010 or 2007 CAS E2010 or 2007 HUB E2010 or 2007 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 or 2007 Servers SP/RU 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS 6. Move Mailboxes 7. Repeat for additional sites 3. Create Legacy namespace 4. Obtain and Deploy Certificates1 2. Deploy Exchange 2013 servers

SP/RU E2010 or 2007 CAS E2010 or 2007 HUB E2010 or 2007 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 or 2007 Servers SP/RU 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS 6. Move Mailboxes 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 3. Create Legacy namespace 4. Obtain and Deploy Certificates2 2. Deploy Exchange 2013 CU1 servers Install both E2013 MBX and CAS servers

Setup.exe /mode:install /roles:clientaccess Setup.exe /mode:install /roles:mailbox Setup.exe /mode:install /roles:ManagementTools /IAcceptExchangeServerLicenseTerms

E2010 or 2007 CAS E2010 or 2007 HUB E2010 or 2007 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 or 2007 Servers 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS 6. Move Mailboxes 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 4. Obtain and Deploy Certificates legacy.contoso.com3 3. Create Legacy namespace SP/RU

E2010 or 2007 CAS E2010 or 2007 HUB E2010 or 2007 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 or 2007 Servers 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS 6. Move Mailboxes 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 4. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers configured with legacy namespace, E2013 namespace and autodiscover namespace Deploy certificates on Exchange 2007 CAS legacy.contoso.com4 3. Create Legacy namespace SP/RU

E2010 or 2007 CAS E2010 or 2007 HUB E2010 or 2007 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 or 2007 Servers 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS Validate using MCA, ExRCA and Test cmdlets 6. Move Mailboxes 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 4. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers configured with legacy namespace, E2013 namespace and Autodiscover namespace Deploy certificates on Exchange 2007 CAS legacy.contoso.com 3. Create Legacy namespace SP/RU 5

Layer 4 LB Layer 7 LB mail.contoso.com HTTP PROXY RPC/HTTP Clients E2007/E2010 MBX Internet-facing site RPC/HTTP Intranet-facing site E2007/E2010 MBX OA Enabled Client Settings IIS Auth: NTLM E2007/E2010 CAS OA Client Settings IIS Auth: E2007/E2010 CAS HTTP PROX Y 3. Client settings Make legacy OA settings the same as 2013 CAS so all clients get the same proxy hostname 1. Enable Outlook Anywhere on all legacy CAS 2. IIS authentication methods IIS Auth must have NTLM enabled on all legacy CAS RPC Client Auth: Basic IIS Auth: Basic NTLM E2013 CU1 CAS E2013 CU1 MBX RPC Disabled Enabled NTLM 4. DNS cutover A low TTL on the existing record the days prior to the cutover is a good idea.

E2010 or 2007 CAS E2010 or 2007 HUB E2010 or 2007 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 or 2007 Servers 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS Validate using MCA, ExRCA and Test cmdlets 6. Move Mailboxes Build out DAG Move users to E2013 MBX 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers E2013 CAS E2013 MBX 4. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 Client Access Servers configured with legacy namespace, E2013 namespace and Autodiscover namespace Deploy certificates on Exchange 2007 CAS legacy.contoso.com 3. Create Legacy namespace SP/RU 6

Legacy Public FoldersModern Public Folders Content storagePublic Folder databasePublic Folder mailbox Public Folder content replicationCan be replicated between databasesReplication is not possible High availabilityPF replicationDAG PF Hierarchy storageOne per PF database, multi-masterPer PF mailbox, one master only PF Hierarchy synchronizationBased on Direct mailbox sync SearchItems onlyItems and attachments (full-text) Public Folder permission management Access Control Lists (ACLs)Role-based Access Control (RBAC) Public Folder Client permissionsAccess Control Lists (ACLs) Admin PlatformPF Management Console + EMSEAC + EMS Outlook client supportAny Outlook versionOutlook OWA supportOWA 2007, OWA 2010OWA 2013 Exchange Server supportExchange 2010 or earlierExchange 2013

2. Analyze Take snapshot of existing PF folder structure, statistics and permissions Map PF folders to PF mailboxes Outlook clients 1. Prepare Install Exchange SP and/or updates across the ORG Migrate all users that require access to Exchange 2013 Verify PF health (replication, mail flow, etc.) 4. Begin migration request Clients continue to access and create new data during copy After copy is complete migration request status is AutoSuspended 5. Finalize migration request Update snapshot of existing PF folder structure, statistics and permissions Lock source, clients logged off, final sync occurs 3. Create new public folder mailboxes Set to HoldForMigration Mode, mailboxes invisible to clients MBX 6. Validate Check and verify destination folders PF dbase 2 PF dbase 3 E2007 SP3 or E2010 PF Exchange 2013 CU1 PF mbx 1PF mbx 2 MB X 5 PF dbase 1 PFs PF mbx 3 3 RU1 0 SP3

Questions?