Micrsft Office 365 Services Migratin Service Descriptin Published: June 2011 Fr the latest infrmatin, see http://www.micrsft.cm/nline.
The infrmatin cntained in this dcument represents the current view f Micrsft Crpratin n the issues discussed as f the date f publicatin and is subject t change at any time withut ntice t yu. This dcument is prvided as-is. Infrmatin and views expressed in this dcument, including URL and ther Internet website references, may change withut ntice. Yu bear the risk f using it. MICROSOFT MAKES NO WARRANTIES, EPRESS OR IMPLIED, IN THIS DOCUMENT. Sme examples depicted herein are prvided fr illustratin nly and are fictitius. N real assciatin r cnnectin is intended r shuld be inferred. This dcument des nt prvide yu with any legal rights t any intellectual prperty in any Micrsft prduct. Yu may cpy and use this dcument fr yur internal, reference purpses. Yu may mdify this dcument fr yur internal, reference purpses. This dcument is prprietary t Micrsft. The descriptins f ther cmpanies prducts in this dcument, if any, are prvided nly as a cnvenience t yu. Any such references shuld nt be cnsidered an endrsement r supprt by Micrsft. Micrsft cannt guarantee their accuracy, and the prducts may change ver time. Als, the descriptins are intended as brief highlights t aid understanding, rather than as thrugh cverage. Fr authritative descriptins f these prducts, please cnsult their respective manufacturers. Micrsft may have patents, patent applicatins, trademarks, cpyrights, r ther intellectual prperty rights cvering subject matter in this dcument. Except as expressly prvided in any written license agreement frm Micrsft, the furnishing f this dcument des nt give yu any license t these patents, trademarks, cpyrights, r ther intellectual prperty. Micrsft Office 365 Migratin Service Descriptin June 2011 2
Sme infrmatin relates t pre-released prduct, which may be substantially mdified befre it is cmmercially released. All trademarks are the prperty f their respective wners. 2011 Micrsft Crpratin. All rights reserved. Micrsft, Active Directry, ActiveSync, Lync, Outlk, SharePint, SQL Server, Windws, and Windws PwerShell are either registered trademarks r trademarks f Micrsft Crpratin in the United States and/r ther cuntries. The names f actual cmpanies and prducts mentined herein may be the trademarks f their respective wners. Micrsft Office 365 Migratin Service Descriptin June 2011 3
Cntents Intrductin...7 In This Dcument... 7 Acrnyms... 8 General Assumptins...9 General Custmer Respnsibilities... 9 General Prject Assumptins... 9 Service Prvisining... 10 Service Prvisining Scenaris... 10 Scenari 1: N Directry Synchrnizatin... 10 Scenari 2: Directry Synchrnizatin, N Identity Federatin... 10 Scenari 3: Identity Federatin (Recmmended)... 11 Apprach... 11 Scpe and Respnsibilities... 11 Additinal Custmer Respnsibilities... 15 Out f Scpe... 15 Entrance Criteria... 16 Exit Criteria... 19 Migratin frm Exchange Server t Exchange Online... 20 Migratin Scenaris... 20 Scenari 1: Cutver Migratin... 20 Scenari 2: Staged Exchange Migratin... 20 Scenari 3: Hybrid Deplyments... 20 Micrsft Office 365 Migratin Service Descriptin June 2011 4
Apprach... 21 Scpe and Respnsibilities... 22 Additinal Custmer Respnsibilities... 23 Out f Scpe... 24 Entrance Criteria... 25 Exit Criteria... 26 Migratin frm IBM Ltus Ntes/Dmin t Exchange Online... 27 Apprach... 27 Scpe and Respnsibilities... 28 Out f Scpe... 30 Preparatin... 30 Prject Timeline... 30 Replicatin... 32 Cexistence... 32 Installatin, Cnfiguratin, and Testing f CMT fr Cexistence Gateway... 32 Zer-Tuch Applicatin Remediatin (ZApp) Cnfiguratin and Testing (Optinal)... 33 Data Migratin... 34 Pst-Migratin Supprt... 34 Additinal Custmer Respnsibilities... 34 General... 34 Preparatin... 34 Replicatin... 36 Cexistence... 36 Data Migratin... 37 Micrsft Office 365 Migratin Service Descriptin June 2011 5
Assumptins... 37 General Assumptins... 37 Exceptin Events... 38 Entrance Criteria... 38 Exit Criteria... 39 Migratin frm Other Email Systems t Exchange Online... 40 Apprach... 40 Scpe and Respnsibilities... 40 Additinal Custmer Respnsibilities... 41 Out f Scpe... 42 Entrance Criteria... 42 Exit Criteria... 42 Micrsft Office 365 Migratin Service Descriptin June 2011 6
Intrductin Micrsft Exchange Online is ne f the Office 365 nline services available frm Micrsft. These Internet-based services are designed t make it easier fr rganizatins t rapidly and cst-effectively access up-t-date cmmunicatins and cllabratin technlgies. Micrsft Exchange Online is a remtely hsted enterprise messaging slutin based n Micrsft Exchange Server. With Exchange Online, yur rganizatin's email is hsted n servers that are hused in Micrsft data centers. Email is accessible t users n a wide range f devices frm inside yur crprate netwrk r ver the Internet. An ptinal feature f Exchange Online is assistance with the migratin f email, calendar, and cntact data frm an existing custmer envirnment, including cexistence with the existing messaging systems during the migratin phase. This migratin service ffers a standardized cnsistent slutin t prvide tested and knwn migratin prcesses t successfully migrate a custmer t Micrsft Online Services. It emplys best practices develped with custmers and partners, cmbined with the experience f migrating hundreds f enterprise custmers t Micrsft Online Services. The Exchange Online email migratin and cexistence service makes use f Micrsft Exchangebased servers, migratin servers (and replica servers, fr IBM Ltus Ntes), cexistence servers, migratin tls, and supprt prcesses t prvide a remtely hsted migratin service t the custmer. These majr cmpnents reside in bth the Micrsft data center and n-premises at the custmer lcatin. In This Dcument The purpse f this service descriptin is t prvide infrmatin abut the email migratin services that are available frm Micrsft Premier Deplyment (MPD) fr Office 365: Migratin t Office 365 Exchange Online frm the custmer s n-premises Exchange Server slutin, r frm ther supprted third-party email slutins. The scpe f services that are applicable t migratin f the email system t Office 365 Exchange Online. The respnsibilities f bth MPD and the custmer, fr each cmpnent f the migratin prcess. The dcument assumes that the custmer has reviewed the Office 365 Service Descriptins. Imprtant This service descriptin is intended fr Office 365 deplyments and is subject t change at any time withut ntice. This service descriptin is applicable fr use with an accmpanying Micrsft Premier Deplyment (MPD) Wrk Order (WO) based n the MPD Deplyment Rate Card. Micrsft Office 365 Migratin Service Descriptin June 2011 7
Acrnyms DirSync Micrsft Online Services Directry Synchrnizatin tl DNS Dmain Name System CAS Exchange 2010 Client Access Server MPD Micrsft Premier Deplyment Micrsft Office 365 Migratin Service Descriptin June 2011 8
General Assumptins This sectin lists the general assumptins that apply t the verall MPD engagement, either service prvisining r migratin t Exchange Online. General Custmer Respnsibilities The fllwing general respnsibilities are expected n the custmer side: Be available t schedule and participate in meetings and prgress reviews. Prvide access t infrmatin, data, systems, netwrks, decisins, and apprvals as planned r within reasnable timeframes after a request, t ensure the prject schedule is nt negatively impacted. Help reslve prject issues, and escalate as necessary. Schedule and ensure the cmmitment f custmer resurces per the prject schedule. Assign custmer persnnel t the prject wh have apprpriate business and technical knwledge f the current envirnment and the cmmunicatins skills necessary t participate. Perfrm applicatin assessment r remediatin. Deply required client sftware. Prvide cmmunicatin, training, and supprt t end users. General Prject Assumptins The custmer will escalate eventual issues t Micrsft thrugh a maximum f tw individuals, typically the custmer s prject manager and technical lead. Micrsft Office 365 Migratin Service Descriptin June 2011 9
Service Prvisining The gal fr service prvisining is t enable custmer s users t cnsume Online Services n Office 365. Service prvisining includes the Plan and Prepare phases f deplyment, as described in the Micrsft Online Services Custmer Deplyment Guide, with n data migratin. Service prvisining can be applied n its wn, when n mailbx migratin is freseen. This can be the case when the custmer has nt subscribed t the Exchange Online service, r when the mailbx transitin apprach f chice desn t include server data migratin. Service prvisining can als apply in cmbinatin with mailbx migratin, as described in fllwing sectins. Nte Mailbx migratin includes service prvisining. Service Prvisining Scenaris There are three main scenaris that can be selected fr service prvisining. Scenari 1: N Directry Synchrnizatin The service prvisining scenari withut directry synchrnizatin applies when user identities and grups fr Online Services are created and managed directly in the Office 365 administratin prtal, r thrugh Windws PwerShell cmmand-line interface cmdlets. In this scenari users have tw sets f credentials: ne fr n-premises authenticatin, ne fr nline authenticatin. The passwrd plicy fr nline credentials is managed nline, separately frm any n-premises passwrd plicy, and users must change nline passwrds peridically. N single sign-n (SSO) experience is prvided t users. This scenari is typically adpted when n Active Directry service is in place fr user authenticatin n the custmer's premises. If this scenari is selected in cnjunctin with the cutver migratin scenari fr Exchange Server-t- Exchange Online migratins, then user prvisining is managed in the Migrate phase f deplyment. Scenari 2: Directry Synchrnizatin, N Identity Federatin Service prvisining with directry synchrnizatin but n identity federatin applies when an Active Directry is in place fr n-premises authenticatin, and users and grups are synchrnized frm the n-premises directry t the nline directry. This scenari nly prvides the ability t autmate the creatin and management f user identities and grups fr Online Services frm the n-premises directry it des nt prvide SSO. Users still have tw distinct sets f credentials fr n-premises and nline authenticatin, and distinct passwrd plicies apply separately. Micrsft Office 365 Migratin Service Descriptin June 2011 10
Scenari 3: Identity Federatin (Recmmended) Service prvisining with identity federatin applies when identity federatin is established between the n-premises Active Directry envirnment and the Office 365 envirnment. Users nly authenticate n premises, and their identities flw securely t the Online Services, achieving SSO. (Depending n the client perating system and applicatin versins, an initial sign-n may be required, but the user credentials are the same as used fr n-premises authenticatin.) Directry synchrnizatin is required in this scenari. Users must be activated fr the Online Services fr which they have a license, after user identities are prvisined t Office 365, and after adpting ne f these three scenaris. The activatin prcess can happen n the Office 365 administratin prtal r thrugh Windws PwerShell cmdlets. Apprach Micrsft assists with prject planning and preparatin fr accunt prvisining. Micrsft prvides assessment f the custmer s current Active Directry envirnment in preparatin fr Micrsft Online Services, and assistance with planning and cnfiguratin; Micrsft des nt prvide remediatin. The versin f the Micrsft Office 365 Deplyment Readiness Tl is available t facilitate Active Directry assessment. Micrsft wrks with custmers t prvisin supprted identity types in the custmer s Office 365 tenant via the supprted prvisining methds shwn in Table 1. Micrsft prvides an autmated license assignment prcess t activate users and assciate accunts with specific licenses designated by the custmer. Table 1: Supprted Identity Types and Prvisining Methds Identity Type By Directry Synchrnizatin frm Active Directry By CSV/Bulk Imprt Cntact Yes Manual creatin Distributin grup Yes Manual creatin Glbal security grup Yes Manual creatin Universal security grup Yes N/A Mailbx-enabled user Yes Yes Mail-enabled user Yes N/A Nn-mail enabled user Yes N/A Scpe and Respnsibilities Table 2 lists the areas that are within the scpe fr MPD in service prvisining, alng with the respnsibilities f bth MPD and the custmer, listed by area. (Respnsibilities that flw acrss multiple areas are listed in Additinal Custmer Respnsibilities later in this sectin.) Micrsft Office 365 Migratin Service Descriptin June 2011 11
Table 2: Service Prvisining Scpe and Respnsibilities Scpe Area Applies t: Respnsibilities: Scenari 1: N Directry Sync Scenari 2: Directry Sync, N Identity Federatin Scenari 3: Identity Federatin MPD Custmer Planning Prvides guidance and recmmendatins. Defines and manages the prject schedule. Assigns resurces t the prject as required. Dmain validatin Prvides guidance and supprts the custmer in registering and validating the required dmains with Office 365. Registers the required dmains with Office 365. Makes changes t the external DNS t validate dmain wnership. Identity prvisining t Office 365 Executes autmatic prvisining f users n the Office 365 tenant, based n data prvided by the custmer, using supprted methds. Prvides a list f users t be prvisined t Office 365. Executes manual creatin f cntacts, mail-enabled distributin grups, and mail-enabled security grups, if needed. License assignment and user activatin Establishment f DirSync Executes autmatic license assignment and user activatin, based n data prvided by the custmer, using supprted methds. Prvides guidance and supprts the custmer in installing and cnfiguring the DirSync tl. Prvides lists f user accunts t be activated, ne fr each Online Service t which the custmer has subscribed. Installs and cnfigures DirSync n the dedicated server, including Micrsft SQL Server setup if required. DirSync setup requires Enterprise Admin credentials. Executes and maintains backups f all data invlved. Micrsft Office 365 Migratin Service Descriptin June 2011 12
Scpe Area Applies t: Respnsibilities: Scenari 1: N Directry Sync Scenari 2: Directry Sync, N Identity Federatin Scenari 3: Identity Federatin MPD Custmer Establishment f Active Directry Federatin Services Prvides guidance and supprts the custmer in installing and cnfiguring AD FS n tw dedicated servers. If applicable, prvides guidance and supprts the custmer in installing and cnfiguring tw dedicated AD FS prxy servers. Installs and cnfigures an AD FS farm n tw dedicated servers. Establishes lad balancing between the tw AD FS servers, the tw AD FS prxy servers, r bth, using either the Netwrk Lad Balancing service r an external lad balancer. Establishment f identity federatin with Office 365 Prvides guidance and supprts the custmer in setting up an AD FS farm cmpsed f tw servers. Prvides guidance and supprts the custmer in establishing identity federatin with Office 365. Installs and cnfigures the Office 365 Federatin tl. Executes Windws PwerShell cmdlets t cnfigure identity federatin. Publishes AD FS endpints n the Internet thrugh either the AD FS prxies r an existing secure reverse prxy slutin. Client cnfiguratin Prvides guidance and recmmendatins. Manages client imaging, sftware deplyment, and cnfiguratin management. Micrsft Office 365 Migratin Service Descriptin June 2011 13
Scpe Area Applies t: Respnsibilities: Scenari 1: N Directry Sync Scenari 2: Directry Sync, N Identity Federatin Scenari 3: Identity Federatin MPD Custmer PART I Exchange Online cnfiguratin Prvides guidance and supprts the custmer in executing the cnfiguratins. Micrsft Lync Online cnfiguratin Micrsft SharePint Online cnfiguratin Prvides guidance and supprts the custmer in cnfiguring Lync Online (e.g., file transfer, Audi and Vide, dmain federatin, public instant messaging cnnectivity). Prvides guidance and supprts the custmer in cnfiguring SharePint Online (e.g., delegated administratin). Cnfigures Lync Online as required. Cnfigures SharePint Online as required. Ntes Within the scpe f MPD's respnsibilities fr service prvisining, MPD guidance and supprt are limited t prviding implementatin dcumentatin and high-level architectural discussins. Guidance is available fr implementing AD FS 2.0 fr use with SSO in Office 365 fr enterprises. Fr additinal infrmatin, visit the Office 365 cmmunity website. The Audi and Vide feature f Lync Online is restricted based n the User Lcatin prperty defined fr each user (n the User Infrmatin page f the Office 365 administratin prtal). This prperty defines the primary cuntry r regin where the user signs in t Office 365. Fr a list f the lcatins where this feature is available, see License Micrsft Office 365 Migratin Service Descriptin June 2011 14
Restrictins fr Office 365. If yur regin is nt specified in the list, the Enable Audi Vide ptin is unavailable n the User Infrmatin page f the administratin prtal. Additinal Custmer Respnsibilities This sectin cvers respnsibilities that flw acrss multiple areas f the service prvisining prcess. Assign resurces t initiate, mnitr, and cmplete prvisining during windws that have been agreed with Micrsft, t include evenings and weekends. Plan, develp, and execute cmmunicatin and training plans fr all end users. Ensure that each end-user desktp meets Office 365 client prerequisites prir t migratin. (Fr infrmatin abut client prerequisites, see the Office 365 Service Descriptin.) Plan and crdinate all end-user supprt befre the first prductin user mailbx is activated. Perfrm all end-user Tier 1 and Tier 2 supprt. Escalate Tier 3 supprt issues t Micrsft via a maximum f tw pints f cntact, typically the custmer s prject manager r Micrsft Exchange administratr. Migrate client-side data (ptinal). Set up frwarding frm the custmer s n-premises email slutin t Office 365 (ptinal). Set up DNS recrds management. Set up messaging hygiene. Out f Scpe Any area that is nt explicitly listed in Scpe and Respnsibilities earlier in this sectin is ut f scpe fr the MPD engagement and, when applicable, is t be cnsidered a custmer respnsibility. The areas that are ut f scpe fr the MPD engagement include, but are nt limited t, the fllwing: Active Directry structure cmpnents, including directry service cmpnents such as trusts and site definitins Active Directry data cleanup and remediatin DirSync custmizatin (the DirSync tl is a sftware appliance, and its cnfiguratin cannt be changed) Client sftware deplyment and cnfiguratin, including withut limitatin any infrmatin wrker data migratin that invlves email, dcuments, prcesses, r custm data types Micrsft Office 365 Migratin Service Descriptin June 2011 15
Applicatin cexistence cnfiguratin, including but nt limited t: Exchange rich cexistence features setup Exchange simple cexistence features setup Entrance Criteria The entrance criteria (prerequisites) fr service prvisining are listed in Table 3. If ne r mre f the entrance criteria are nt currently met, the custmer can cntact a Micrsft r partner executive representative fr supprt; Micrsft Online Services can ffer supprt fr any remediatin r extended preparatin activity t help the custmer meet all the entrance criteria fr service prvisining. Table 3: Prerequisites fr Service Prvisining Entrance Criteria ID Descriptin Applies t: Scenari 1: N Directry Sync Scenari 2: Directry Sync, N Identity Federatin Scenari 3: Identity Federatin ENC001 ENC002 ENC003 The custmer has prvisined an Office 365 tenant, and makes available t the MPD team a managed user accunt with Glbal Administratr permissins fr the whle duratin f the MPD engagement. The custmer has defined (r is able t define by the date defined with MPD in accrdance with the prject schedule), lists f user accunts that will need t be activated fr each Online Service the custmer has subscribed t. The custmer is able t manage and apply changes t the relevant DNS system, bth internally and externally. ENC004 The custmer has a healthy Active Directry infrastructure in place fr authenticatin f users. ENC005 The custmer s Active Directry infrastructure has a single frest tplgy. ENC006 All relevant attributes in the custmer s Active Directry are ppulated crrectly fr all users and grups, and the Office 365 Deplyment Readiness Tl reprts n errrs in the Active Directry sectins. Micrsft Office 365 Migratin Service Descriptin June 2011 16
Entrance Criteria ID Descriptin Applies t: Scenari 1: N Directry Sync Scenari 2: Directry Sync, N Identity Federatin Scenari 3: Identity Federatin ENC007 The custmer has prvisined and deplyed (r will prvisin and deply by the date defined with MPD in accrdance with the prject schedule) ne (1) server r virtual machine that satisfies the DirSync tl requirements. This server must be cnnected t the internal netwrk, with utbund Internet access, and cnfigured up t the perating system level including the mst recent relevant updates. If the custmer Active Directry frest has mre than 50,000 bjects, a server running SQL Server 2005 is als required fr DirSync. ENC008 Active Directry is deplyed and running in Windws 2003 r later with a functinal level in mixed r native mde. ENC009 All users use (r will use) the same public UPN suffix name. ENC010 The custmer has prvisined and deplyed (r will prvisin and deply by the date defined with MPD in accrdance with the prject schedule) tw (2) servers r virtual machines that satisfy the Active Directry Federatin Services (AD FS) requirements. These servers must be cnnected t the internal netwrk, with utbund Internet access, and cnfigured up t the perating system level including the mst recent relevant updates. Micrsft Office 365 Migratin Service Descriptin June 2011 17
Entrance Criteria ID Descriptin Applies t: Scenari 1: N Directry Sync Scenari 2: Directry Sync, N Identity Federatin Scenari 3: Identity Federatin ENC011 ENC012 If the custmer chses t publish Active Directry Federatin Services (AD FS) thrugh prxies deplyed in a DMZ: The custmer has prvisined and deplyed (r will prvisin and deply by the date defined with MPD in accrdance with the prject schedule) tw (2) servers r virtual machines that satisfy the Active Directry Federatin Services (AD FS) prxy requirements. These servers must be cnnected t the internal netwrk, with inbund and utbund Internet access, and cnfigured up t the perating system level including the mst recent relevant updates. Or, if the custmer chses t publish Active Directry Federatin Services (AD FS) thrugh an existing reverse prxy like Micrsft Threat Management Gateway (TMG), Micrsft Unified Access Gateway (UAG) r anther Micrsft r third-party secure reverse prxy slutin: The custmer has a functining secure reverse prxy slutin in place and is able t set up the publishing f AD FS https endpints, including prper SSL certificate cnfiguratin. The custmer has acquired (r will acquire by the date defined with MPD in accrdance t the prject schedule) a prper SSL certificate frm a public trusted certificatin authrity (e.g., VeriSign, GDaddy) fr Active Directry Federatin Services. Micrsft Office 365 Migratin Service Descriptin June 2011 18
Exit Criteria The exit criteria fr service prvisining are listed in Table 4. Table 4: Exit Criteria fr Service Prvisining Exit Criteria ID Descriptin Applies t: Scenari 1: N Directry Sync Scenari 2: Directry Sync, N Identity Federatin Scenari 3: Identity Federatin EC001 All the necessary users and grups have been prvisined t Office 365. EC002 DirSync runs regularly with n unexpected errrs. EC003 Identity federatin wrks prperly fr users, bth internally and externally. Micrsft Office 365 Migratin Service Descriptin June 2011 19
Migratin frm Exchange Server t Exchange Online Fr custmers wh plan t migrate their Exchange Server email system, Exchange Online Standard ffers the migratin services described in Table 5: Supprted Cntent Types fr Exchange Online, later in this sectin. Each area is described later in this sectin, alng with the sets f respnsibilities t be taken n by Micrsft and the custmer during the email migratin. Migratin Scenaris There are three main scenaris that can be selected fr mailbx migratin frm an existing Exchange rganizatin. Scenari 1: Cutver Migratin The mailbx migratin scenari fr cutver migratin applies when DirSync is nt in place. Because n cexistence capability is prvided in this scenari, all mailbxes are typically migrated in ne migratin event (usually ver a weekend). Scenari 2: Staged Exchange Migratin The mailbx migratin scenari with Staged Exchange migratin applies when user mailbxes are migrated ver an extended perid f time, in different migratin events, althugh the end gal is that all users will be migrated t Exchange Online. This scenari requires that DirSync be in place. Scenari 3: Hybrid Deplyments Fr cmpanies running n-premises Exchange Server email envirnments, Exchange Online allws administratrs t establish a hybrid deplyment between the n-premises envirnment and the nline envirnment. In a hybrid envirnment, sme users cnnect t Exchange Online while thers cntinue t use the lcal Exchange Server envirnment, and all f the users can share the same email dmain name. This scenari requires that DirSync be in place, as well as an Exchange 2010 SP1 CAS/HUB rle server n-premises (nte: The mailbx server rle is als required fr n-premises Exchange 2003 rganizatins). Micrsft Office 365 Migratin Service Descriptin June 2011 20
Apprach Micrsft prvides assessment f the custmer s current Active Directry preparatin fr Micrsft Online Services, and assistance with planning and cnfiguratin; Micrsft des nt prvide remediatin. Supprted platfrms: Exchange Server 2010, Exchange Server 2007, Exchange Server 2003 Hsted Exchange Server 2010, Hsted Exchange Server 2007 Migratin includes up t 500 megabytes (MB) f server-based data per mailbx fr supprted cntent types. Fr additinal infrmatin, refer t the MPD Deplyment Rate Card. Mail data migratin is limited t server-based data fr calendar, cntacts, and email messages. Exchange Online migratins supprt the cntent types listed in Table 5. Table 5: Supprted Cntent Types fr Exchange Online Area Cntent Types Cutver and Staged Exchange Migratins Hybrid Deplyments Message items Yes Yes Flders Yes Yes Mail Rules Outlk server-side rules nly Yes Categries Yes Yes Read status Yes Yes Flags Yes Yes Mapping f special flders Yes Yes Calendar items Yes Yes Recurrence Yes Yes Calendar Exceptin Yes Yes Meeting requests Yes Yes OOF settings Yes Yes Categries Yes Yes Tasks Yes Yes Ntes Yes Yes Cntacts Yes Yes Public delegates Yes Yes Flder permissins Yes Yes Micrsft Office 365 Migratin Service Descriptin June 2011 21
Area Cntent Types Cutver and Staged Exchange Migratins Hybrid Deplyments Other Send/receive as N Nt Yet Full mailbx permissin N Nt Yet Custm frms Yes Yes Flder favrites Yes Yes Offline data file (OST) N Yes Outlk data file (PST) N Nt migrated but maintained under same prfile Scpe and Respnsibilities Table 6 lists the areas that are within the scpe fr MPD in an Exchange Server t Exchange Online mailbx migratin, alng with the respnsibilities f bth MPD and the custmer, listed by area. (Respnsibilities that flw acrss multiple areas are listed in Additinal Custmer Respnsibilities later in this sectin.) Table 6: Exchange Server t Exchange Online Mailbx Migratin Scpe and Respnsibilities Scpe Area Applies t: Respnsibilities: Scenari 1: Cutver Migratin Scenari 2: Staged Exchange Migratin Scenari 3: Hybrid Deplyment MPD Custmer Planning Prvides guidance, recmmendatins. Defines and manages the prject schedule. Assigns resurces t the prject as required. Mailbx size reductin Cnfiguratin f permissins n all mailbxes t be migrated DNS cnfiguratin Prvides guidance, recmmendatins. Prvides guidance, recmmendatins. Prvides guidance, recmmendatins. Executes mailbx size reductin activities. Cnfigures the required permissins. Executes the cnfiguratin in the relevant DNS systems (internal and external). Publishing f the Mailbx Replicatin Service (MRS) Prvides guidance, recmmendatins. Cnfigures the publishing f MRS. Micrsft Office 365 Migratin Service Descriptin June 2011 22
Scpe Area Applies t: Respnsibilities: Scenari 1: Cutver Migratin Scenari 2: Staged Exchange Migratin Scenari 3: Hybrid Deplyment MPD Custmer Cnfiguratin f Exchange n-premises fr hybrid Prvides guidance, supprts the custmer in executing the cnfiguratins. Executes the Exchange n-premises cnfiguratins (e.g., Outlk Anywhere publishing, Availability web service, Exchange Web Services, Outlk Web Access). Cnfiguratin f Exchange federatin trust Prvides guidance, supprts custmer in cnfiguring Exchange federatin trust. Cnfigures the Exchange federatin trust. Mailbx migratin Crsspremises mail ruting cnfiguratin Executes migratin prcess tgether with the custmer. Prvides guidance, supprts custmer in cnfiguring crsspremises mail ruting, including Frefrnt Online Prtectin fr Exchange when applicable. Prvides required accunts and credentials t MPD. Executes and maintains backups f all data invlved. Participates with the required resurces fr the whle duratin f the migratin. Cnfigures crsspremises mail ruting. Validates crss-premises mail ruting. Additinal Custmer Respnsibilities This sectin cvers respnsibilities that flw acrss multiple areas f the Exchange Server t Exchange Online Migratin prcess. Plan and test pst-migratin end-user activities. Plan, develp, and execute cmmunicatin and training plans fr all end users. If applicable, cnfigure Outlk Anywhere n the n-premises server running Exchange Server. Micrsft Office 365 Migratin Service Descriptin June 2011 23
Perfrm hybrid deplyment verificatin tests. Ensure that each end-user desktp meets Office 365 client prerequisites prir t migratin. (Fr infrmatin abut client prerequisites, see the Office 365 Service Descriptin.) Plan and crdinate all end-user supprt befre the first prductin mailbx is migrated. Perfrm all end-user Tier 1 and Tier 2 supprt. Escalate Tier 3 supprt issues t Micrsft via a maximum f tw pints f cntact, typically the custmer s prject manager and technical lead r Micrsft Exchange administratr. Migrate client-side data (ptinal). Reactivate mbile devices. Cmmunicate with end users as necessary. Acquire third-party Secure Sckets Layer (SSL) certificates as needed. Perfrm DNS recrds management. Clean up Active Directry in the n-premises envirnment. Update DNS recrds, as necessary. Out f Scpe The fllwing cmpnents and actins are nt supprted as part f the Exchange Online email migratin feature: Active Directry structure cmpnents, including directry service cmpnents such as trusts and site definitins Active Directry data cleanup and remediatin Ratinalizatin and definitin f cmmn Grup Plicy bjects (GPOs) fr User, Wrkstatin, and Server Management DirSync cnfiguratin (DirSync is a sftware appliance; its cnfiguratin cannt be changed) Client sftware deplyment and cnfiguratin, including withut limitatin: Micrsft Outlk r Micrsft Enturage Office 365 Desktp Setup (previusly named Service Cnnectr) Micrsft.NET Framewrk Micrsft Lync 2010 client Public flders Tw-tier/multifactr authrizatin Authrizatin page custmizatin Cbranding Micrsft Office 365 Migratin Service Descriptin June 2011 24
Archiving slutin Exchange Online custmizatin Entrance Criteria The entrance criteria (prerequisites) fr mailbx migratin are listed in Table 7. If ne r mre f the entrance criteria are nt currently met, the custmer can cntact a Micrsft r partner executive representative fr supprt; Micrsft Online Services can ffer supprt fr any remediatin r extended preparatin activity t help the custmer meet all the entrance criteria. Table 7: Prerequisites fr Exchange Server Mailbx Migratin Entrance Criteria ID Descriptin Applies t: Scenari 1: Cutver Migratin Scenari 2: Staged Exchange Migratin Scenari 3: Hybrid Deplyment ENC101 ENC102 Service prvisining has been cmpleted with Scenari 1 (N Directry Synchrnizatin), and all relevant service prvisining exit criteria are met. The custmer has fewer than 10,000 mailbxes t migrate, and fewer than 50,000 bjects prvisined n Office 365. ENC103 Service prvisining has been cmpleted with Scenari 2 (Directry Synchrnizatin, n Identity Federatin) r Scenari 3 (Identity Federatin), and all relevant exit criteria are met. ENC104 ENC105 ENC106 The custmer has an existing and healthy n-premises Exchange Server versin 2003, 2007, r 2010, r hsted Exchange rganizatin versin 2007 r 2010. The custmer has Autdiscver prperly cnfigured and expsed t the Internet, including an SSL certificate issued by a public trusted certificatin authrity (e.g., VeriSign, GDaddy). The custmer has Outlk Anywhere prperly cnfigured fr RPC ver HTTP access, with an SSL certificate issued by a public trusted certificatin authrity (e.g., VeriSign, GDaddy). Micrsft Office 365 Migratin Service Descriptin June 2011 25
Entrance Criteria ID Descriptin Applies t: Scenari 1: Cutver Migratin Scenari 2: Staged Exchange Migratin Scenari 3: Hybrid Deplyment ENC107 ENC108 The custmer has prvisined and deplyed (r will prvisin and deply by the date defined with MPD in accrdance with the prject schedule) ne (1) server r virtual machine that satisfies the Exchange 2010 cexistence server requirements. This server must be cnnected t the DMZ with inbund and utbund Internet access, r cnnected t the internal netwrk with utbund Internet access and published n the Internet fr the relevant endpints thrugh an existing reverse prxy like Micrsft Threat Management Gateway (TMG), Micrsft Unified Access Gateway (UAG) r anther Micrsft r third-party secure reverse prxy slutin. The server must be cnfigured up t the perating system level, including the mst recent relevant updates. The Active Directry schema fr the frest t be federated is at versin Exchange 2010 SP1. Exit Criteria There is ne exit criterin fr all scenaris f Exchange Server mailbx migratin: EC101 All the users in scpe fr migratin are migrated successfully. Micrsft Office 365 Migratin Service Descriptin June 2011 26
Migratin frm IBM Ltus Ntes/Dmin t Exchange Online Fr custmers wh plan t migrate their Ltus Ntes/Dmin email system, Micrsft ffers the migratin services described in Table 8: Ltus Ntes t Exchange Online Mailbx Migratin Scpe and Respnsibilities. Each area is described in this sectin, alng with the sets f respnsibilities t be taken n by Micrsft and the custmer during the email migratin. Apprach The hsted migratin service frm Ltus Ntes/Dmin t Office 365 fr enterprises migrates users frm an existing n-premises installatin f Ltus Ntes/Dmin. It utilizes the technlgy, resurces, and migratin specialists f Micrsft partner Binary Tree t minimize the time and expense cmpared t a traditinal phased migratin prject. Binary Tree is an industry leader in enabling migratin and cexistence between enterprise messaging and cllabratin envirnments based n Ltus Ntes/Dmin and Micrsft Exchange. The hsted migratin includes the fllwing: Migratin planning and preparatin, including end-user cmmunicatins and scheduling Replicatin f all server-based data t Dmin staging servers t ptimize migratin thrughput and minimize data crruptin Cexistence between the existing Ntes/Dmin messaging envirnment and the new Exchange Online messaging envirnment Data migratin Pst-migratin supprt and issue reslutin Preparatin. Preparatin fr migratin includes installatin, cnfiguratin, and testing f the Binary Tree Cmmn Migratin Tl (CMT) fr Exchange, CMT fr Cexistence, and the ptinal Zer-Tuch Applicatin Remediatin (ZApp) tl. As part f this service, the custmer als receives a messaging analysis that identifies envirnmental variables that culd impact the migratin; the analysis als prvides recmmended actin items. Using the CMT fr Exchange management interface, we prvide a standard set f user cmmunicatin templates that can be used directly r custmized by the custmer. These templates include end-user driven actins t synchrnize cntacts and decrypt e-mail, instructins regarding mail rules that may need t be recreated in Exchange, and Outlk training material. Replicatin. By replicating all server-based Ntes/Dmin messaging data that is t be migrated t a secure data center, the custmer avids incurring the csts assciated with building and supprting a temprary migratin infrastructure. This methd als alleviates any f the ptential netwrk cnstraints that are usually assciated with migrating t a hsted envirnment. We prvide a safe ID that enables the custmer t crss-certify at the rganizatinal level. Secure ne-way replicatin is used t synchrnize the data t the hsted migratin Dmin staging servers in the secure data center. Micrsft Office 365 Migratin Service Descriptin June 2011 27
Cexistence. Prviding cexistence during the migratin is a critical success factr. As such, we strngly encurage a cexistence slutin based n CMT fr Cexistence. Binary Tree prvides implementatin assistance fr CMT fr Cexistence t prperly deply, validate, and initially mnitr the cexistence envirnment. The n-premises Active Directry is used as the authritative surce fr prvisining accunts via DirSync in the Office 365 fr enterprises envirnment. We recmmend that the custmer update Active Directry with infrmatin frm the Dmin Directry t remediate name and accunt discrepancies that are ften present between Ntes/Dmin messaging envirnments and Active Directry (such as legal versus cmmn name and last-name changes). Data migratin. The Ntes/Dmin data migratin includes the fllwing fr the server-based mail databases that are identified: 90 days f e-mail histry fr users 90 days f calendar histry and all future calendar entries fr users 90 days f task histry and all future tasks fr users Nte Migratin f 90 days f data is included in the standard rate. Migratin f 180 days f data is available at an extended rate. Fr details, see the MPD Deplyment Rate Card. All cntacts in the user s mail file n the server Cnference rms and future reservatins Mail-in databases (migrated t Exchange shared mailbxes) Pst-migratin supprt. Remte pst-migratin supprt is available t address any migratinrelated cncerns. Further details are utlined thrughut this sectin. Any services that are nt specifically addressed in the fllwing sectins are ut f scpe and will nt be prvided r supprted by Micrsft. Scpe and Respnsibilities Table 8 lists the areas that are within the scpe fr MPD in a Ltus Ntes t Exchange Online mailbx migratin, alng with the respnsibilities f bth MPD and the custmer, listed by area. (Respnsibilities that flw acrss multiple areas are listed in Additinal Custmer Respnsibilities later in this sectin.) Micrsft Office 365 Migratin Service Descriptin June 2011 28
Table 8: Ltus Ntes t Exchange Online Mailbx Migratin Scpe and Respnsibilities Scpe Area Respnsibilities: General Preparatin Replicatin Cexistence MPD Assist with prject planning and preparatin. Run the prject kickff meeting and wrk with custmer t establish highlevel migratin timeline. Prvide guidance fr Active Directry cleanup. Prvide migratin schedule template. Setup hsted migratin Dmin server staging envirnment. Integrate hsted envirnment with custmer s n-premises Dmin server envirnment. Replicate databases t the hsted envirnment. Replicate CMT fr Exchange management database t an n-premises Dmin server. Ntify custmer f any databases t which access is bstructed. Install, cnfigure, and test CMT fr Cexistence. Cnfigure ZApp fr CMT fr Cexistence. Transfer knwledge f key cexistence cncepts and nging maintenance. Custmer Perfrm prject management tasks and expedite the migratin. Cmplete the pre-engagement questinnaire prir t scheduling any n-site services. Plan and execute end-user training, cmmunicatin, and supprt. Prvide netwrk, facilities, and materials access t cnsultants. Perfrm full administratin f the identity and messaging envirnments. Install, patch, and verify client and server thrughut the prject. Wrk with MPD t establish high-level migratin timeline. Perfrm all Ntes/Dmin server and data preparatin. Perfrm all Active Directry cleanup and preparatin. Perfrm all DNS updates. Create mail database migratin schedule. Cnfigure Dmin server authenticatin and cnnectivity with hsted migratin envirnment. Prvide a Ntes ID that has Full Access Administratin rights t the Dmin servers invlved in the migratin. Identify and remedy any nn-standard mail file access issues that wuld prevent replicatin. Ensure that at least ne (1) separate Windws-based Dmin server and at least ne (1) separate Windws-based Internet Infrmatin Services Server are set up t supprt the cexistence cnfiguratin. Prvide up t six (6) test databases and cnfirm cnfiguratin by testing database functinality. Prvide cnfiguratin assistance n n-premises systems as needed t cmplete the cexistence cnfiguratin. Ensure that all cmpnents are fully functinal n physical as well as virtual machines. Micrsft Office 365 Migratin Service Descriptin June 2011 29
Scpe Area Respnsibilities: Data Migratin MPD Migrate mail databases based n the migratin schedule. Mnitr the migratin and prvide status updates at the end f each migratin windw. Help reslve any missing data r incrrect data migratin issues. Custmer Maintain mail database migratin schedule. Prperly set mail frwarding fr migrated users, if CMT fr Cexistence is nt implemented. Wrk t reslve any utstanding migratin issues. Out f Scpe Any area that is nt explicitly listed in Scpe and Respnsibilities earlier in this sectin is ut f scpe fr the MPD engagement and, when applicable, is t be cnsidered a custmer respnsibility. Areas that are ut f scpe fr the MPD engagement include, but are nt limited t, the fllwing: Dmin Directry t Active Directry synchrnizatin. Optinal Identity Federatin Preparatin Prject Timeline The prject frmally begins with a kick-ff meeting, either in persn r virtual, t establish the prject charter and the prject planning assumptins: Target number f users per migratin event Target migratin events per week Expected prject duratin All prerequisites and expectatins The prject delivery timeline begins when all required analysis and cexistence hardware has been prcured. A lead time f fur weeks frm the date the purchase rder is received is generally assumed. Calendar weeks 1-3 invlve the fllwing: Messaging analysis and review CMT fr Exchange deplyment and cnfiguratin Preparatin and deplyment f CMT fr Cexistence, and ZApp if applicable Dmin server and replicatin cnfiguratin Staging envirnment setup Micrsft Office 365 Migratin Service Descriptin June 2011 30
Migratin planning Calendar weeks 4 and 5 invlve pilt migratins and prductin migratin schedule finalizatin. Several pints are imprtant t keep in mind: The ttal number f pilt users is nt t exceed 100 users. Pilt migratins are cnducted during the nrmal business hurs in a custmer s time zne. Based n best-practice recmmendatins, pilt migratins shuld nt include VIPs, including crprate executives and their assistants. Any changes t pilt migratins must be mutually agreed n by all parties. The prductin migratin schedule must be finalized and agreed n by all parties. End-user cmmunicatins must be finalized. Calendar week 6 invlves pre-prductin migratin f users, with a target number f ne-half f the planned prductin migratin event ttals. Fr example, if the prductin migratin targets are 500 users per migratin event and three (3) migratin events per week (1500 users in a week), the pre-prductin migratin week wuld cnsist f a ttal f 750 users. This will serve as an acceptance test r dry run f an actual prductin week. Calendar weeks 7 and 8 prvide fr an ptinal buffer perid, during which all parties prepare fr the prductin migratin events and schedules. N service delivery actins are planned during this perid. An extensin f the buffer perid must be mutually agreed upn by all parties, with full understanding f impact n the prductin migratin timeline and csts. The next N weeks invlve prductin migratins, based n the fllwing assumptins: The maximum duratin f the prductin migratin is N = T / 800, where T is the ttal number f users and N is the estimated number f weeks. Nte The number 800 is derived frm the estimated weekly target f 1,000 users minus the allwable delta f 20 percent. Example: A prductin migratin f 10,000 users must be cmpleted in a maximum f 13 weeks. Each additinal prductin migratin event beynd the target maximum duratin r an exceptin event (see Exceptin Events belw) is separately charged at the amunt f $10,000 per event. There is a weekly target f 1,000 users, which may be reduced based n the ttal number f users. Micrsft Office 365 Migratin Service Descriptin June 2011 31
Replicatin A senir messaging cnsultant wrks with the custmer t replicate the necessary data frm the custmer s n-premises Dmin servers t a secure data center. Depending n the amunt f data and the available bandwidth, replicatin can take several weeks t cmplete. Activities Set up a hsted migratin Dmin server staging envirnment. Integrate the hsted migratin Dmin staging envirnment with the custmer s npremises Dmin envirnment. Crss-certify the hsted migratin rganizatin and the custmer s n-premises rganizatin. Add the hsted migratin Dmin staging server names t the LcalDmainServers access grup (r the custmer equivalent). Authrize the hsted migratin management ID fr Full Access Administratin rights t the custmer s n-premises Dmin envirnment. Alternative The custmer can prvide the deplyment team an ID t be used as a migratin management ID that has Full Access Administratin rights t the Dmin envirnment. Replicate t the hsted migratin Dmin staging servers all databases that are t be migrated. Replicate the CMT fr Exchange management database t an n-premises Dmin server. Phase Cmpletin Artifacts Cnfiguratin f ne-way (push) scheduled replicatin f the custmer s n-premises Dmin Directry t the hsted migratin Dmin staging servers Cnfiguratin f ne-way (push) scheduled replicatin f all databases t be migrated frm the n-premises Dmin servers t the hsted migratin Dmin staging servers Cnfiguratin f bi-directinal scheduled replicatin f CMT fr Exchange management interface between the data center and an n-premises Dmin server Cexistence Installatin, Cnfiguratin, and Testing f CMT fr Cexistence Gateway A senir messaging cnsultant installs and cnfigures the CMT fr Cexistence gateway n a prductin Dmin cexistence server that is lcated in the prductin Ntes dmain. A senir messaging cnsultant then prvides knwledge transfer sessins t the custmer team, teaching them the key cexistence cncepts t prperly administer the envirnment. Micrsft Office 365 Migratin Service Descriptin June 2011 32
Nte Micrsft strngly recmmends that CMT fr Cexistence be implemented. Ntes and third-party applicatins, cnnectrs, r gateways that include the fllwing functins will nt functin prperly withut CMT fr Cexistence: Send e-mail messages with custm Ntes elements such as buttns, htspts, and any ther frms nt included in the standard Dmin mail templates. Send encrypted Ntes items. Fr custmers that chse nt t implement CMT fr Cexistence, it is slely the custmer s respnsibility t prperly set mail frwarding fr migrated users. Activities Install, cnfigure, and test the CMT fr Cexistence gateway. Transfer knwledge f key cexistence cncepts and nging maintenance. Phase Cmpletin Artifacts Successful installatin and cnfiguratin f CMT fr Cexistence Verificatin f CMT fr Cexistence functinality Zer-Tuch Applicatin Remediatin (ZApp) Cnfiguratin and Testing (Optinal) A senir messaging cnsultant cnfigures Zer-Tuch Applicatin Remediatin (ZApp) fr CMT fr Cexistence. The custmer is respnsible fr prviding up t six (6) Ntes databases that use Ntes-specific elements t be used fr testing in the prductin envirnment. Nte ZApp is an ptinal add-n that requires additinal fees based n ttal user cunt. See the MPD Deplyment Rate Card fr details. Activities Hld a ZApp technical review meeting t determine the ZApp initial cnfiguratin and deplyment strategy, and t set the expectatins fr nging ZApp cnfiguratin maintenance. Install, cnfigure, and test ZApp. Phase Cmpletin Artifacts Successful installatin and cnfiguratin f ZApp and the strage database (BTStre.nsf) Verificatin f ZApp functinality with prductin applicatins and Exchange test accunts Micrsft Office 365 Migratin Service Descriptin June 2011 33
Data Migratin Migratin specialists migrate mail databases based n the migratin schedule. The specialists mnitr the migratin and prvide status updates at the end f each migratin windw. Remte pst-migratin supprt is available t address any migratin-related cncerns. After the migratin is cmplete, the data center is sanitized f all custmer data using bestpractice methdlgies. Pst-Migratin Supprt A senir cnsultant wrks with the custmer t prvide supprt fr migrated users after each migratin event and reslves any utstanding data migratin issues. Additinal Custmer Respnsibilities This sectin cvers respnsibilities that flw acrss multiple areas f the Ltus Ntes t Exchange Online Migratin prcess. General Be available t schedule and participate in meetings and prgress reviews. Prvide infrmatin, data, decisins, and apprvals within reasnable timeframes in rder t ensure that the prject schedule is nt negatively impacted. Help reslve prject issues, and escalate issues as necessary. Schedule and ensure the cmmitment f custmer resurces per the prject schedule. Assign peple t the prject wh have apprpriate business and technical knwledge f the current envirnment, and the cmmunicatins skills necessary t participate. Perfrm full administratin f the Active Directry, Ltus Ntes/Dmin, Exchange Online, and any ther messaging envirnments including cnfiguring and validating mail ruting between the custmer s n-premises messaging envirnment and the Internet. Prvide cnsultants with adequate access t the netwrk and materials needed t perfrm their duties. Typically mst, if nt all, wrk is perfrmed remtely. Preparatin Ensure that all Dmin mail servers are at Release 6.0.3 r higher. Ensure that all internal Ntes/Dmin mail traffic is ruting via NRPC (nt SMTP). Perfrm all Active Directry preparatin, including: Synchrnizatin with Dmin Directry Federatin and synchrnizatin with Office 365 fr enterprises Ensure the integrity f Ntes data t be migrated. (Crrupt r incmplete data will nt migrate successfully.) Micrsft Office 365 Migratin Service Descriptin June 2011 34
Unencrypt encrypted Ntes data. Nte Binary Tree prvides an end-user driven prcess fr decrypting e-mail; hwever, it is the custmer s respnsibility t ensure that this actin is cmpleted. This actin requires the Ltus Ntes client, and is nt available via Dmin Web Access (intes). Synchrnize each user's Ntes cntacts with his/her server-based mail file. Nte Binary Tree prvides an end-user driven prcess fr synchrnizing cntacts; hwever, it is the custmer s respnsibility t ensure that this actin is cmpleted. This actin requires the Ltus Ntes client, and is nt available via Dmin Web Access (intes). Assign a valid, unique InternetAddress in the Dmin Directry fr each persn, mail-in database, cnference rm, and resurce t be migrated. Fr Messaging Analysis, prvide remte access t tw (2) wrkstatins with the fllwing requirements: Dmin administrative access Windws P Prfessinal with 2 GB f RAM and 25 GB f free disk space High speed netwrk access t all Dmin servers Outbund access t Dmin staging servers via TCP prt 1352 Outbund FTP and HTTP/S access Internet Explrer Web Brwser Ltus Ntes 7.0.3 Client, Admin Client, and Designer Client Micrsft Excel Ntes ID permissins: Full Remte Cnsle Administratr access rights t all servers being inspected in the dmain(s). A minimum f Reader access rights in each database s Access Cntrl List, but Manager access is preferred and recmmended fr ease f administratin. If the Ntes ID used fr inspectin des nt have this level f access t every database t be inspected, ne f the fllwing actins must be taken befre the inspectin can be cmpleted: Add the Ntes ID t each database s ACL; Add the Ntes ID t a grup with the required access rights that is already in the database s ACL; r Use the Ntes Full Access Administratin feature. Hwever, this feature must be enabled befre each client sessin and may slw the analysis. Micrsft Office 365 Migratin Service Descriptin June 2011 35
Replicatin Ensure that prt 1352 is pen utbund n the Dmin servers, fr cmmunicatin with the hsted migratin Dmin staging servers. Crss-certify a staging envirnment safe ID at the rganizatinal level, t be used t certify a Dmin server ID and a migratin ID. Add the hsted migratin Dmin staging servers t the LcalDmainServers access grup (r custmer equivalent). Prvide cnnectivity infrmatin fr all mail servers, t create cnnectin dcuments fr ne-way replicatin frm the custmer envirnment t the secure data center. Set up cnnectin recrds t the hsted replicatin servers in the custmer s Dmin Directry. Ensure that the hsted migratin Dmin staging servers can pull replicas f the Dmin Directry and all mail databases t be migrated. Cexistence Ensure that at least ne (1) separate Windws-based Dmin server is set up t supprt messaging, calendaring, free/busy lkup, and the ptinal ZApp add-n, with the fllwing system requirements: 32-bit Windws Server 2003 perating system r Windws Server 2008 with Pentium 4 prcessr r higher, preferably a server class prcessr such as en r Quad Cre Minimum f 2 gigabytes (GB) RAM, 4 GB RAM recmmended At least 80 GB hard disk space, 150 GB if using ZApp Micrsft.NET Framewrk 3.5 SP1 and Micrsft Visual C++ 2008 SP1 develpment system, with Redistributable Package installed Dmin Release 7.0.3 r 8.5.2 Minimum 100-MB netwrk adaptr, 1-GB recmmended Ensure at least ne (1) separate Windws-based Internet Infrmatin Services server is set up t supprt free/busy lkup between Ntes/Dmin and Office 365, with the fllwing system requirements: 64-bit Windws Server 2008 R2 Micrsft Internet Infrmatin Services 7.x Micrsft.NET Framewrk 4.0 Full SSL certificate Ensure that all cmpnents f CMT fr Cexistence are fully functinal n physical as well as virtual machines. Nte Micrsft Office 365 Migratin Service Descriptin June 2011 36
When setting up prf-f-cncept r pilt cexistence envirnments, Binary Tree recmmends and supprts the use f virtual machines as a means f lwering the expense f such prjects. Hwever, Binary Tree has nt yet gathered sufficient infrmatin abut prductin cexistence envirnments t determine whether virtual envirnments have the same stability and scalability characteristics as physical nes. Based n the fact that a majrity f prductin cexistence envirnments have been and are deplyed n physical machines, Binary Tree advises ptential custmers f this fact, but defers t the custmer t make the final decisin with respect t virtualizatin. Binary Tree prvides prduct supprt in bth physical and virtual envirnments; hwever, if either stability r scalability issues are fund in a virtual envirnment, Binary Tree may recmmend switching t a physical envirnment t crrect the issue. Data Migratin N additinal requirements. Assumptins General Assumptins The weekly migratin schedule days and times are mutually agreed upn in advance f the preprductin migratin, in accrdance with the fllwing parameters: There is a maximum f fur (4) migratin events per week, which include the fllwing: Up t ne (1) migratin event per weekend Up t three (3) migratin events between Mnday and Thursday There must be a cnsistent number f migratin events per week, n cnsistent days f each week. There is ne migratin event ne batch f Exchange Online activatins and data migratins per day. Start times fr migratin events may be different n different days f the week. There is a weekly target f 1,000 users t be migrated with a migratin event target f 500 users. Fr custmers with between 2,400 and 5,000 users, the weekly target may be reduced t 500 users with a migratin event target f 250 users. Fr custmers with between 5,000 and 10,000 users, the weekly target may be reduced t 750 users with a migratin event target f 375 users. There is a cnsistent number f users migrated per migratin event. (Example: 500 users per migratin event, tw migratin events per week, fr each week f the prject.) Nte Micrsft Office 365 Migratin Service Descriptin June 2011 37
There is an allwable delta f 20 percent, utside f which the number f users per migratin event cannt fall (see the fllwing Exceptin Events sectin). Fr example, if the migratin event target is 500 users, n event can exceed 600 users, nr fall belw 400 users. A lckdwn perid is the perid f time befre a migratin event when n additinal users may be added t r drpped frm a scheduled migratin event. The lckdwn perid fr adding users is determined based n the time requirement fr replicating data t the data center and preparing accunts fr migratin. users. The lckdwn perid fr adding users may be much lnger than fr remving Exceptin Events An exceptin event is a migratin event in which the number f users falls belw the migratin event target minus 20 percent. These are the assumptins cncerning exceptin events: Any migratin event that falls belw the allwed minimum is either cancelled r treated as a free r chargeable exceptin event, t be agreed upn by all parties. One (1) free exceptin event is allwed per 30 days during the Migrate phase. All exceptin events must be separately funded, and must cmply with the lckdwn perid. A larger maximum fr an event is acceptable withut additinal charge, if it is arranged at least three weeks in advance. Entrance Criteria The entrance criteria (prerequisites) fr this mailbx migratin are listed in Table 9. If ne r mre f the entrance criteria are nt currently met, the custmer can cntact a Micrsft r partner executive representative fr supprt; Micrsft Online Services can ffer supprt fr any remediatin r extended preparatin activity t help the custmer meet all the entrance criteria. Table 9: Prerequisites fr Ntes/Dmin Mailbx Migratin Enter Criteria ID ENC201 ENC202 ENC203 ENC204 ENC205 Descriptin Service prvisining has been cmpleted with ne f the three service prvisining scenaris, and all relevant exit criteria are met. All required analysis and cexistence hardware has been prcured. The custmer has cmpleted the pre-engagement questinnaire prir t scheduling any n-site services. The custmer has full administratin permissins f any and all identity and messaging envirnments. All Dmin mail servers are at Release 6.0.3 r higher. Micrsft Office 365 Migratin Service Descriptin June 2011 38
Enter Criteria ID ENC206 ENC207 ENC208 ENC209 Descriptin All internal Ntes/Dmin mail traffic is ruted via Ntes Remte Prcedure Call (NRPC) rather than Simple Mail Transfer Prtcl (SMTP). Prt 1352 is pen utbund fr all Dmin mail servers fr cmmunicatin with the hsted migratin Dmin staging servers. The custmer is ready t deliver a Ntes ID with Full Access Administratin rights t the Dmin servers invlved in the migratin. Active Directry schema extensins fr Exchange Server 2010 SP1 are applied. Exit Criteria There is ne exit criterin fr Ntes/Dmin mailbx migratin: EC201 All the users in scpe fr migratin are migrated successfully. Micrsft Office 365 Migratin Service Descriptin June 2011 39
Migratin frm Other Email Systems t Exchange Online Other email is defined as any email platfrm that is nt Exchange Server, Ltus Ntes/Dmin, r Nvell GrupWise. Fr these platfrms, Micrsft prvides the email migratin services described in Table 10: Mailbx Migratin Scpe and Respnsibilities f Other Email Systems. Each area is described later in this sectin, alng with the sets f respnsibilities t be taken n by MPD and the custmer during a migratin. Nte Supprted cntent types depend n surce platfrm and migratin technlgies used. Fr details, cntact the custmer's Micrsft accunt team and Micrsft Premier Deplyment. Apprach Fr IMAP4-based email systems, email migratin is executed cmpletely frm the Micrsft Online data center, and n n-premises deplyment is required. T be able t access mailbx data, the custmer must prvide user credentials in the frm f CSV files. N cexistence functinality is prvided in this scenari. Micrsft prvides assessment fr Active Directry preparatin fr Micrsft Online Services, and assistance with planning and cnfiguratin; Micrsft des nt prvide remediatin. The cntent types that Micrsft supprts depend n the custmer s surce platfrm and the migratin technlgies t be used. The custmer s Micrsft accunt team and MPD can prvide details. Mail data migratin is limited t server-based data fr supprted cntent types. These are the supprted platfrms: Gmail IMAP4-based email systems Migratin includes up t 500 MB f server-based data per mailbx fr supprted cntent types. Mailbxes that are larger than 500 MB, up t 4.25 GB, are priced at twice the base rate. Custm qutes are required fr mailbxes larger than 4.25 GB. Scpe and Respnsibilities Table 10 lists the areas that are within the scpe fr MPD in mailbx migratin, alng with the respnsibilities f bth MPD and the custmer, listed by area. (Respnsibilities that flw acrss multiple areas are listed in Additinal Custmer Respnsibilities later in this sectin.) Micrsft Office 365 Migratin Service Descriptin June 2011 40
Table 10: Mailbx Migratin Scpe and Respnsibilities f Other Email Systems Scpe Area Respnsibilities: Planning Mailbx size reductin Cnfiguratin f permissins n all mailbxes t be migrated Cnfigure email system t allw Internet access based n migratin prtcl DNS cnfiguratin Mailbx migratin MPD Prvides guidance and recmmendatins. Prvides guidance and recmmendatins. Prvides guidance and recmmendatins. Prvides guidance and recmmendatins. Prvides guidance and recmmendatins. Executes the migratin prcess tgether with the custmer. Executes pst-migratin validatin testing. Custmer Defines and manages the prject schedule. Assigns resurces t the prject as required and agreed. Executes mailbx size reductin activities. Cnfigures the required permissins. Enables Internet access fr migratin prtcl and test. Executes the cnfiguratin in the relevant DNS systems (internal and external). Prvides required accunts and credentials t MPD. Executes and maintains backups f all data invlved. Participates with the required resurces fr the whle duratin f the migratin. Additinal Custmer Respnsibilities This sectin cvers respnsibilities that flw acrss multiple areas f the service prvisining prcess. Plan, develp, and execute cmmunicatin and training plans fr all end users. Ensure that each end-user desktp meets Office 365 client prerequisites prir t migratin. (Fr infrmatin abut client prerequisites, see the Office 365 Service Descriptin.) Plan and crdinate all end-user supprt befre the first prductin mailbx is migrated. Perfrm all end user Tier 1 and Tier 2 supprt. Escalate Tier 3 supprt issues t Micrsft via a maximum f tw pints f cntact, typically the custmer s prject manager r Micrsft Exchange administratr. Migrate client-side data (ptinal). Set up frwarding frm the n-premises email slutin t Office 365 (ptinal). Perfrm DNS recrds management. Micrsft Office 365 Migratin Service Descriptin June 2011 41
Set up messaging hygiene. Out f Scpe The fllwing cmpnents and actins are nt supprted as part f the Exchange Online email migratin feature: Active Directry structure cmpnents, including directry service cmpnents such as trusts and site definitins Active Directry data cleanup and remediatin DirSync cnfiguratin r custmizatin (DirSync is a sftware appliance; its cnfiguratin cannt be changed) Creatin f a custm email data migratin slutin Client sftware deplyment and cnfiguratin Archiving slutin Exchange Online custmizatin Rich cexistence features Entrance Criteria The entrance criteria (prerequisites) fr mailbx migratin are listed in Table 11. If ne r mre f the entrance criteria are nt currently met, the custmer can cntact a Micrsft r partner executive representative fr supprt; Micrsft Online Services can ffer supprt fr any remediatin r extended preparatin activity t help the custmer meet all the entrance criteria. Table 11: Prerequisites fr Mailbx Migratin f Other Email Systems Entrance Criteria ID ENC401 ENC402 ENC403 Descriptin Service prvisining has been cmpleted with ne f the three scenaris, and all relevant service prvisining exit criteria are met. Access t IMAP prts (143/993) f the surce system is available. Credentials (username / passwrd) t access each user mailbx are available. Exit Criteria There is ne exit criterin fr this mailbx migratin: EC401 All the users in scpe fr migratin are migrated successfully. Micrsft Office 365 Migratin Service Descriptin June 2011 42