Home
%3CLINGO-SUB%20id%3D%22lingo-sub-585115%22%20slang%3D%22en-US%22%3EExchange%20Server%20Deployment%20Assistant%20Update%20for%20Exchange%202010%20and%20Office%20365%20Coexistence%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-585115%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%3EWe're%20happy%20to%20announce%20that%20we've%20enhanced%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Fexdeploy2010%2F%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%20Server%20Deployment%20Assistant%3C%2FA%3E%20to%20include%20support%20for%20configuring%20%3CSPAN%20class%3D%22bold%22%3Erich%20coexistence%3C%2FSPAN%3E%20(also%20known%20as%20%E2%80%9C%3CA%20span%3D%22%22%20class%3D%22bold%22%20href%3D%22http%3A%2F%2Fhelp.outlook.com%2Fen-us%2F140%2Fff633682.aspx%22%20title%3D%22More%20about%20hybrid%20deployments%20and%20migration%20with%20Office%20365%20on%20help.outlook.com%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehybrid%20deployment%3C%2FA%3E%E2%80%9D)%20for%20organizations%20interested%20in%20maintaining%20some%20users%20on-premises%20with%20Exchange%202010%20and%20some%20users%20hosted%20in%20the%20cloud%20by%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Foffice365%2Fonline-software.aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EMicrosoft%20Office%20365%3C%2FA%3E%20for%20enterprises.%20This%20scenario%20is%20in%20addition%20to%20the%20existing%20support%20for%20configuring%20rich%20coexistence%20between%20on-premises%20Exchange%202003%20and%20Exchange%202007%20organizations%20and%20Office%20365.%3C%2FP%3E%20%20%3CP%3EThe%20new%20coexistence%20information%20for%20the%20Exchange%202010%20environment%20is%20only%20available%20in%20English%20at%20this%20time%20and%20requires%20that%20your%20existing%20Exchange%202010%20servers%20are%20updated%20to%20Exchange%20Server%202010%20Service%20Pack%201%20(SP1).%3C%2FP%3E%20%20%3CP%3ERich%20coexistence%20(%E2%80%9Chybrid%20deployment%E2%80%9D)%20offers%20organizations%20the%20ability%20to%20extend%20the%20feature-rich%20experience%20and%20administrative%20control%20they%20have%20with%20their%20existing%20on-premises%20Microsoft%20Exchange%20organization%20to%20the%20cloud.%20It%20provides%20the%20seamless%20look%20and%20feel%20of%20a%20single%20Exchange%20organization%20between%20an%20on-premises%20organization%20and%20a%20cloud-based%20organization.%20In%20addition%2C%20coexistence%20can%20serve%20as%20an%20intermediate%20step%20to%20moving%20completely%20to%20a%20cloud-based%20Exchange%20organization.%20This%20approach%20is%20different%20than%20the%20%3CSPAN%20class%3D%22newterm%22%3Esimple%20Exchange%20migration%3C%2FSPAN%3E%20(aka%20%3CSPAN%20class%3D%22newterm%22%3Ecutover%20migration%3C%2FSPAN%3E)%20and%20%3CSPAN%20class%3D%22newterm%22%3Estaged%20Exchange%20migration%3C%2FSPAN%3E%20options%20currently%20offered%20by%20Office%20365%20outlined%20in%20%3CA%20class%3D%22bold%22%20href%3D%22http%3A%2F%2Fhelp.outlook.com%2Fen-us%2Fbeta%2Fms.exch.ecp.emailmigrationstatuslearnmore.aspx%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EEmail%20Migration%20Overview%3C%2FA%3E%20in%20Exchange%20Online%20help.%3C%2FP%3E%20%20%3CP%3EIf%20you're%20not%20already%20familiar%20with%20the%20Exchange%20Deployment%20Assistant%2C%20it%20allows%20you%20to%20create%20Exchange%20Server%202010%20on-premises%20configuration%20and%20deployment%20instructions%20that%20are%20customized%20to%20your%20environment.%20It%20asks%20you%20a%20small%20set%20of%20simple%20questions%20and%20it%20provides%20a%20checklist%20with%20instructions%20that%20are%20designed%20to%20deploy%20or%20configure%20Exchange%202010%20based%20on%20your%20answers.%20In%20addition%20to%20the%20online%20checklist%2C%20you%20can%20even%20print%20a%20PDF%20of%20your%20checklist.%3C%2FP%3E%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fpostimages%2F8267.ExDeploy-Home.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-filesystemfile.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-postimages%2F8267.ExDeploy_2D00_Home.png%22%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22caption%22%3E%3CSPAN%20class%3D%22bold%22%3EFigure%201%3A%3C%2FSPAN%3E%20The%20%3CA%20href%3D%22http%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3FLinkID%3D171086%22%20title%3D%22Go%20to%20the%20Exchange%20Server%20Deployment%20Assistant%20site%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EExchange%20Server%20Deployment%20Assistant%3C%2FA%3E%20(ExDeploy)%20is%20a%20web-based%20tool%20that%20helps%20you%20upgrade%20to%20Exchange%202010%20on-premises%2C%20deploy%20a%20hybrid%20on-premises%20and%20Exchange%20Online%20organization%20or%20migrate%20to%20Exchange%20Online%3C%2FSPAN%3E%3C%2FP%3E%20%20%3CP%3EYour%20feedback%20is%20very%20important%20for%20the%20continued%20improvement%20of%20this%20tool.%20We%20would%20love%20your%20feedback%20on%20this%20new%20scenario%20and%20any%20other%20area%20of%20the%20Deployment%20Assistant.%20Feel%20free%20to%20either%20post%20comments%20on%20this%20blog%20post%2C%20provide%20feedback%20in%20the%20Office%20365%20community%20%3CA%20href%3D%22http%3A%2F%2Fcommunity.office365.com%2Fen-us%2Ff%2F162.aspx%22%20title%3D%22Go%20to%20the%20migration%20and%20coexistence%20forum%20in%20Office%20365%20community%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Emigration%20and%20coexistence%20forum%3C%2FA%3E%2C%20or%20send%20an%20email%20to%20edafdbk%40microsoft.com%20via%20the%20'Feedback'%20link%20located%20in%20the%20header%20of%20every%20page%20of%20the%20Deployment%20Assistant.%20Thanks!%3C%2FP%3E%20%20%3CP%3E%3CSPAN%20class%3D%22author%22%3EThe%20Exchange%20Team%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-611416%22%20slang%3D%22en-US%22%3EUpgrading%20Exchange%20ActiveSync%20to%20Exchange%202010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-611416%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%3EMany%20of%20you%20have%20been%20asking%20how%20you%20can%20upgrade%20your%20existing%20Exchange%20environment%20to%20Exchange%202010%20from%20a%20client%20access%20perspective.%20For%20most%20of%20you%2C%20this%20will%20also%20mean%20coexisting%20with%20legacy%20Exchange%20and%20Exchange%202010%20for%20a%20period%20of%20time.%26nbsp%3B%20My%20%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Fb%2Fexchange%2Farchive%2F2009%2F11%2F20%2F3408856.aspx%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Efirst%20blog%20article%3C%2FA%3E%20in%20this%20series%20discussed%20the%20overall%20steps%20in%20how%20to%20upgrade%20your%20environment%20from%20a%20client%20access%20perspective.%26nbsp%3B%20This%20article%2C%20the%20third%20in%20the%20series%2C%20discusses%20how%20Exchange%20ActiveSync%20will%20function%20in%20an%20Exchange%202003%20or%202007%20environment%20that%20has%20Exchange%202010%20deployed.%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-1956566745%22%20id%3D%22toc-hId-1956568607%22%3EUpgrading%20EAS%20in%20an%20Exchange%202003%20Environment%20to%20Exchange%202010%3C%2FH1%3E%0A%3CP%3ESome%20of%20you%20may%20have%20environments%20that%20have%20Internet%20facing%20AD%20sites%20and%20non-Internet%20facing%20AD%20sites.%26nbsp%3B%20As%20part%20of%20our%20upgrade%20process%2C%20you%20will%20be%20following%20a%20model%20where%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EEnsure%20all%20Exchange%202003%20servers%20are%20at%20Service%20Pack%202.%3C%2FLI%3E%0A%3CLI%3EDeploy%20Exchange%202010%20CAS%2C%20Hub%20Transport%2C%20and%20Mailbox%20in%20the%20%22Internet%20Facing%20AD%20Site%22.%3C%2FLI%3E%0A%3CLI%3EHave%20legacy%20Exchange%20servers%20in%20the%20%22Non-Internet%20facing%20AD%20site%22%20(if%20they%20exist).%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EIn%20other%20words%2C%20it%20would%20look%20something%20like%20this%20for%20an%20Exchange%202003%20upgrade%2Fco-existence%3A%3C%2FP%3E%0A%3CP%3E%3CA%20target%3D%22_blank%22%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2Fthemes%2Fexchange%2Fimages%2F453470_E2010UpgradeEAS1.jpg%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fthemes%2Fexchange%2Fimages%2F453470_E2010UpgradeEAS1.jpg%22%20rel%3D%22noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CIMG%20height%3D%22318%22%20width%3D%22538%22%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Flegacyfs%2Fonline%2Fmedia%2Fthemes%2Fexchange%2Fimages%2F453470_E2010UpgradeEAS1.jpg%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fthemes%2Fexchange%2Fimages%2F453470_E2010UpgradeEAS1.jpg%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EWith%20this%20configuration%20there%20are%20typically%20a%20few%20questions%20that%20are%20asked%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EWhat%20are%20the%20configuration%20changes%20I%20must%20make%20on%20the%20Exchange%202003%20Front-End%20servers%20to%20support%20ActiveSync%3F%3C%2FLI%3E%0A%3CLI%3EWhat%20are%20the%20configuration%20changes%20I%20must%20make%20on%20the%20Exchange%202003%20mailbox%20servers%3F%3C%2FLI%3E%0A%3CLI%3EWhat%20scenarios%20involve%20proxying%20and%20what%20scenarios%20involve%20redirection%20for%20Exchange%20ActiveSync%20(Exchange%202003)%3F%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CB%3EWhat%20are%20the%20configuration%20changes%20I%20must%20make%20on%20the%20Exchange%202003%20Front-End%20servers%20to%20support%20ActiveSync%3F%20%3C%2FB%3E%3C%2FP%3E%0A%3CP%3EIn%20order%20to%20introduce%20Exchange%202010%20into%20your%20%22Internet%20Facing%20AD%20Site%22%20and%20support%20your%20Exchange%202003%20mailboxes%2C%20you%20will%20move%20the%20primary%20EAS%20namespace%20that%20is%20associated%20with%20the%20Exchange%202003%20Front-End%20servers%20and%20associate%20it%20with%20the%20Exchange%202010%20CAS%20array.%26nbsp%3B%20For%20more%20information%20on%20the%20detailed%20steps%20required%20to%20support%20coexistence%20process%20see%20my%20%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Farchive%2F2009%2F11%2F20%2F453272.aspx%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Efirst%20blog%20article%3C%2FA%3E%20in%20the%20series%2C%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Faa998604(EXCHG.140).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ETechNet%3C%2FA%3E%2C%20or%20within%20the%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Fexdeploy2010%2Fdefault.aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EDeployment%20Assistant%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%3CB%3EWhat%20are%20the%20configuration%20changes%20I%20must%20make%20on%20the%20Exchange%202003%20mailbox%20servers%3F%3C%2FB%3E%3CB%3E%20%3C%2FB%3E%3C%2FP%3E%0A%3CP%3EUsers%20with%20mailboxes%20on%20an%20Exchange%202003%20server%20who%20try%20to%20use%20Exchange%20ActiveSync%20through%20an%20Exchange%202010%20Client%20Access%20server%20will%20receive%20an%20error%20and%20be%20unable%20to%20synchronize%20unless%20Integrated%20Windows%20authentication%20is%20enabled%20on%20the%20Microsoft-Server-ActiveSync%20virtual%20directory%20on%20the%20Exchange%202003%20server.%20This%20allows%20the%20Exchange%202010%20Client%20Access%20server%20and%20the%20Exchange%202003%20back%20end%20server%20to%20communicate%20using%20Kerberos%20authentication.%3C%2FP%3E%0A%3CP%3ETo%20enable%20this%20authentication%20change%20on%20Exchange%202003%20you%20need%20to%20either%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EInstall%20%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fkbid%3D937031%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttp%3A%2F%2Fsupport.microsoft.com%2F%3Fkbid%3D937031%3C%2FA%3E%20and%20then%20use%20the%20Exchange%20System%20Manager%20to%20adjust%20the%20authentication%20settings%20of%20the%20ActiveSync%20virtual%20directory.%3C%2FLI%3E%0A%3CLI%3EOr%2C%20set%20the%20msExchAuthenticationFlags%20attribute%20to%20a%20value%20of%206%20on%20the%20Microsoft-Server-ActiveSync%20object%20within%20the%20configuration%20container%20on%20each%20Exchange%202003%20mailbox%20server.%26nbsp%3B%20An%20example%20script%20is%20provided%20at%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc785437.aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttp%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc785437.aspx%3C%2FA%3E.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CB%3E%3CI%3ENote%3C%2FI%3E%3C%2FB%3E%3A%20It%20is%20important%20that%20you%20do%20not%20use%20IIS%20Manager%20to%20change%20the%20authentication%20setting%20on%20the%20ActiveSync%20virtual%20directory%20as%20the%20DS2MB%20process%20within%20the%20System%20Attendant%20will%20overwrite%20the%20settings%20that%20are%20stored%20in%20Active%20Directory.%3C%2FP%3E%0A%3CP%3E%3CB%3EWhat%20scenarios%20involve%20proxying%20and%20what%20scenarios%20involve%20redirection%20for%20Exchange%20ActiveSync%20(Exchange%202003)%3F%3C%2FB%3E%3CB%3E%3C%2FB%3E%3C%2FP%3E%0A%3CP%3EHopefully%20the%20Exchange%202003%20coexistence%20diagram%20is%20self-explanatory%2C%20but%20if%20it%20is%20not%2C%20the%20key%20thing%20here%20is%20that%20regardless%20of%20the%20location%20of%20the%20Exchange%202003%20mailbox%20(remember%20Exchange%202003%20is%20not%20site%20aware)%2C%20CAS2010%20will%20always%20proxy%20the%20request%20to%20the%20Exchange%202003%20mailbox%20server.%26nbsp%3B%20Also%2C%20since%20Exchange%202003%20does%20not%20support%20Autodiscover%2C%20the%20device%20version%20does%20not%20matter.%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EUser's%20device%20is%20already%20configured%20to%20use%20the%20namespace%20mail.contoso.com.%3C%2FLI%3E%0A%3CLI%3EUser's%20device%20attempts%20to%20synchronize.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20authenticate%20the%20user%2C%20determine%20the%20mailbox%20version%20is%20Exchange%202003%20by%20performing%20a%20service%20discovery%20lookup%20in%20Active%20Directory%2C%20and%20retrieve%20the%20Exchange%202003%20mailbox%20server%20FQDN.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20proxy%20the%20connection%20to%20the%20Exchange%202003%20mailbox%20server's%20Microsoft-Server-ActiveSync%20virtual%20directory.%26nbsp%3B%20In%20the%20IIS%20logs%2C%20you%20will%20see%20a%20response%20similar%20to%3A%3CBLOCKQUOTE%3E%0A%3CP%3EPOST%20%2FMicrosoft-Server-ActiveSync%2Fdefault.eas%20User%3Duser5%26amp%3BDeviceId%3Dfoo%26amp%3BDeviceType%3DPocketPC%26amp%3BCmd%3DFolderSync%26amp%3BLog%3DPrxTo%3Amail.contoso.com_LdapC2_%20443%20contoso%5Cuser5%2010.20.100.117%20MSFT-PPC%2F5.1.2301%20200%200%200%20189%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3C%2FLI%3E%0A%3CLI%3EThe%20mailbox%20server%20will%20authenticate%20the%20user%20and%20retrieve%20and%20render%20the%20mailbox%20data%20and%20will%20provide%20the%20rendered%20data%20back%20to%20the%20CAS2010%20server.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20expose%20the%20data%20to%20the%20end%20user.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CB%3E%3C%2FB%3E%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--988617226%22%20id%3D%22toc-hId--988615364%22%3EUpgrading%20EAS%20in%20an%20Exchange%202007%20Environment%20to%20Exchange%202010%3C%2FH3%3E%0A%3CP%3ESome%20of%20you%20may%20have%20environments%20that%20have%20Internet%20facing%20AD%20sites%20and%20non-Internet%20facing%20AD%20sites.%26nbsp%3B%20As%20part%20of%20our%20upgrade%20process%2C%20you%20will%20be%20following%20a%20model%20where%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EYou%20upgrade%20all%20CAS%20servers%20in%20the%20organization%20to%20Exchange%202007%20SP2.%3C%2FLI%3E%0A%3CLI%3EUpgrade%20all%20Exchange%202007%20servers%20in%20%22Internet%20Facing%20AD%20Site%22%20to%20Exchange%202007%20SP2.%3C%2FLI%3E%0A%3CLI%3EDeploy%20Exchange%202010%20CAS%2C%20Hub%20Transport%2C%20and%20Mailbox%20in%20the%20%22Internet%20Facing%20AD%20Site%22.%3C%2FLI%3E%0A%3CLI%3EHave%20legacy%20Exchange%20servers%20in%20the%20%22Non-Internet%20facing%20AD%20site%22%20(if%20they%20exist).%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EIn%20other%20words%2C%20it%20would%20look%20something%20like%20this%20for%20an%20Exchange%202007%20upgrade%2Fco-existence%3A%3C%2FP%3E%0A%3CP%3E%3CA%20target%3D%22_blank%22%20href%3D%22https%3A%2F%2Fhelpcenter.xactlycorp.com%2Flegacyfs%2Fonline%2Fmedia%2Fthemes%2Fexchange%2Fimages%2F453471_E2010UpgradeEAS2.jpg%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fthemes%2Fexchange%2Fimages%2F453471_E2010UpgradeEAS2.jpg%22%20rel%3D%22noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CIMG%20height%3D%22337%22%20width%3D%22681%22%20src%3D%22http%3A%2F%2Fmigration9.stage.lithium.com%2Flegacyfs%2Fonline%2Fmedia%2Fthemes%2Fexchange%2Fimages%2F453471_E2010UpgradeEAS2.jpg%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fthemes%2Fexchange%2Fimages%2F453471_E2010UpgradeEAS2.jpg%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EWith%20this%20configuration%20there%20are%20typically%20a%20few%20questions%20that%20are%20asked%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EAre%20there%20any%20configuration%20changes%20I%20must%20make%20on%20my%20Exchange%202007%20Client%20Access%20servers%3F%3C%2FLI%3E%0A%3CLI%3EWhat%20are%20the%20configuration%20changes%20I%20must%20make%20on%20the%20Exchange%202003%20mailbox%20servers%2C%20if%20they%20exist%20in%20the%20environment%3F%3C%2FLI%3E%0A%3CLI%3EWhat%20scenarios%20involve%20proxying%20and%20what%20scenarios%20involve%20redirection%20for%20Exchange%20ActiveSync%20(Exchange%202007)%3F%3C%2FLI%3E%0A%3CLI%3EWhat%20scenarios%20involve%20proxying%20and%20what%20scenarios%20involve%20redirection%20for%20Exchange%20ActiveSync%20(Exchange%202003)%3F%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CB%3E%3C%2FB%3E%3C%2FP%3E%0A%3CP%3E%3CB%3EAre%20there%20any%20configuration%20changes%20I%20must%20make%20on%20my%20Exchange%202007%20Client%20Access%20servers%3F%3C%2FB%3E%3C%2FP%3E%0A%3CP%3EIn%20order%20to%20introduce%20Exchange%202010%20into%20your%20%22Internet%20Facing%20AD%20Site%22%20and%20support%20your%20Exchange%202007%20(and%20possibly%202003)%20mailboxes%2C%20you%20will%20move%20the%20primary%20EAS%20namespace%20that%20is%20associated%20with%20the%20Exchange%202007%20CAS%20array%20and%20associate%20it%20with%20the%20Exchange%202010%20CAS%20array.%20In%20addition%2C%20you%20will%20create%20a%20new%20namespace%20for%20legacy%20access%2C%20legacy.contoso.com%20(note%20that%20the%20name%20can%20be%20anything%20you%20want)%20and%20associate%20it%20with%20your%20Exchange%202007%20CAS%20array.%3C%2FP%3E%0A%3CP%3EFor%20CAS2007%20within%20the%20%22Internet%20Facing%20AD%20Site%22%20you%20will%20want%20to%20configure%20the%20EAS%20ExternalURL%20to%20utilize%20the%20legacy.contoso.com%20namespace%20to%20allow%20for%20redirection%20of%20devices%20that%20support%20Autodiscover%20by%20using%20the%20following%20cmdlet%3A%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3ESet-ActiveSyncVirtualDirectory%3CCAS2007%3E%3C%2FCAS2007%3E%3CCAS2007%3E%3C%2FCAS2007%3E%3CCAS2007%3E%3C%2FCAS2007%3E%3CCAS2007%3E%3C%2FCAS2007%3E%3CCAS2007%3E%3C%2FCAS2007%3E%3CCAS2007%3E%3C%2FCAS2007%3E%3CCAS2007%3E%3C%2FCAS2007%3E%3CCAS2007%3E%3C%2FCAS2007%3E%5CMicrosoft-Server-ActiveSync*%20-ExternalURL%20%3CA%20href%3D%22https%3A%2F%2Flegacy.contoso.com%2FMicrosoft-Server-ActiveSync%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Flegacy.contoso.com%2FMicrosoft-Server-ActiveSync%3C%2FA%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EOn%20the%20CAS2010%2C%20you%20will%20set%20the%20ExternalURL%20to%20be%20%3CA%20href%3D%22https%3A%2F%2Fmail.contoso.com%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fmail.contoso.com%3C%2FA%3E%20using%20the%20following%20cmdlet%3A%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3ESet-ActiveSyncVirtualDirectory%3CCAS2010%3E%3C%2FCAS2010%3E%3CCAS2010%3E%3C%2FCAS2010%3E%3CCAS2010%3E%3C%2FCAS2010%3E%3CCAS2010%3E%3C%2FCAS2010%3E%3CCAS2010%3E%3C%2FCAS2010%3E%3CCAS2010%3E%3C%2FCAS2010%3E%3CCAS2010%3E%3C%2FCAS2010%3E%3CCAS2010%3E%3C%2FCAS2010%3E%5CMicrosoft-Server-ActiveSync*%20-ExternalURL%20%3CA%20href%3D%22https%3A%2F%2Fmail.contoso.com%2FMicrosoft-Server-ActiveSync%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fmail.contoso.com%2FMicrosoft-Server-ActiveSync%3C%2FA%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EUnlike%20Exchange%202003%2C%20Exchange%202007%20does%20not%20require%20any%20authentication%20changes%2C%20but%20let's%20understand%20why.%3C%2FP%3E%0A%3CP%3EIn%20Exchange%202007%2C%20for%20EAS%20proxy%20communication%20to%20work%20between%20CAS2007%20in%20the%20%22Internet%20Facing%20AD%20Site%22%20and%20CAS2007%20in%20the%20%22Non-Internet%20Facing%20Site%22%2C%20you%20had%20to%20enable%20Windows%20Integrated%20Authentication%20on%20the%20CAS2007%20ActiveSync%20virtual%20directories%20in%20the%20%22Non-Internet%20Facing%20Site%22.%20If%20you%20didn't%2C%20you%20could%20not%20proxy%20EAS%20traffic.%3C%2FP%3E%0A%3CP%3EWith%20Exchange%202007%20SP2%20(and%20Exchange%202010)%2C%20setup%20creates%20a%20new%20sub-virtual%20directory%20under%20%5CMicrosoft-Server-ActiveSync%2C%20called%20proxy.%20This%20proxy%20virtual%20directory%20has%20Windows%20Integrated%20Authentication%20enabled.%20When%20CAS2010%20has%20to%20proxy%20EAS%20traffic%20to%20CAS2007%20(or%20to%20another%20CAS2010)%2C%20the%20%5CMicrosoft-Server-ActiveSync%5Cproxy%20virtual%20directory%20will%20be%20used%20for%20the%20proxy%20traffic.%3C%2FP%3E%0A%3CP%3E%3CB%3E%3CI%3ENote%3C%2FI%3E%3C%2FB%3E%3A%20This%20behavior%20is%20only%20for%20CAS2010%20to%20CAS2007%2FCAS2010%20EAS%20proxy.%20CAS2007%20to%20CAS2007%20EAS%20proxy%20still%20requires%20Windows%20Integrated%20Authentication%20to%20be%20set%20on%20the%20ActiveSync%20virtual%20directory.%3C%2FP%3E%0A%3CP%3EFor%20more%20information%20on%20the%20detailed%20steps%20required%20to%20support%20coexistence%20process%20see%20my%20%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Farchive%2F2009%2F11%2F20%2F453272.aspx%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Efirst%20blog%20article%3C%2FA%3E%20in%20the%20series%2C%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Faa998604(EXCHG.140).aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ETechNet%3C%2FA%3E%2C%20or%20within%20the%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Fexdeploy2010%2Fdefault.aspx%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EDeployment%20Assistant%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%3CB%3EWhat%20are%20the%20configuration%20changes%20I%20must%20make%20on%20the%20Exchange%202003%20mailbox%20servers%2C%20if%20they%20exist%20in%20the%20environment%3F%3C%2FB%3E%3CB%3E%20%3C%2FB%3E%3C%2FP%3E%0A%3CP%3EIf%20your%20Exchange%202007%20environment%20contains%20Exchange%202003%20mailbox%20servers%2C%20then%20users%20with%20mailboxes%20on%20an%20Exchange%202003%20server%20who%20try%20to%20use%20Exchange%20ActiveSync%20through%20an%20Exchange%202010%20Client%20Access%20server%20will%20receive%20an%20error%20and%20be%20unable%20to%20synchronize%20unless%20Integrated%20Windows%20authentication%20is%20enabled%20on%20the%20Microsoft-Server-ActiveSync%20virtual%20directory%20on%20the%20Exchange%202003%20server.%20This%20allows%20the%20Exchange%202010%20Client%20Access%20server%20and%20the%20Exchange%202003%20back%20end%20server%20to%20communicate%20using%20Kerberos%20authentication.%3C%2FP%3E%0A%3CP%3ETo%20enable%20this%20authentication%20change%20on%20Exchange%202003%20you%20need%20to%20either%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EInstall%20%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fkbid%3D937031%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttp%3A%2F%2Fsupport.microsoft.com%2F%3Fkbid%3D937031%3C%2FA%3E%20and%20then%20use%20the%20Exchange%20System%20Manager%20to%20adjust%20the%20authentication%20settings%20of%20the%20ActiveSync%20virtual%20directory.%3C%2FLI%3E%0A%3CLI%3EOr%2C%20set%20the%20%3CI%3EmsExchAuthenticationFlags%3C%2FI%3E%20attribute%20to%20a%20value%20of%206%20on%20the%20Microsoft-Server-ActiveSync%20object%20within%20the%20configuration%20container%20on%20each%20Exchange%202003%20mailbox%20server.%26nbsp%3B%20An%20example%20script%20is%20provided%20at%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc785437.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc785437.aspx%3C%2FA%3E.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CB%3E%3CI%3ENote%3C%2FI%3E%3C%2FB%3E%3A%20It%20is%20important%20that%20you%20do%20not%20use%20IIS%20Manager%20to%20change%20the%20authentication%20setting%20on%20the%20ActiveSync%20virtual%20directory%20as%20the%20DS2MB%20process%20within%20the%20System%20Attendant%20will%20overwrite%20the%20settings%20that%20are%20stored%20in%20Active%20Directory.%3C%2FP%3E%0A%3CP%3E%3CB%3EWhat%20scenarios%20involve%20proxying%20and%20what%20scenarios%20involve%20redirection%20for%20Exchange%20ActiveSync%20(Exchange%202007)%3F%3C%2FB%3E%3CB%3E%3C%2FB%3E%3C%2FP%3E%0A%3CP%3E%3CB%3E%3CI%3ENote%3C%2FI%3E%3C%2FB%3E%3A%20It%20is%20assumed%20that%20Autodiscover%20is%20associated%20with%20CAS2010%20in%20the%20%22Internet%20Facing%20AD%20site%22.%3C%2FP%3E%0A%3CP%3EHopefully%20the%20Exchange%202007%20coexistence%20diagram%20is%20self-explanatory%2C%20but%20if%20it%20is%20not%3A%3C%2FP%3E%0A%3CP%3EFor%20the%20first%20scenario%2C%20let's%20consider%20the%20behavior%20for%20User1.%26nbsp%3B%20Since%20User1%20is%20located%20in%20the%20same%20AD%20site%20as%20the%20Internet%20facing%20CAS2010%20and%20CAS2007%20is%20also%20Internet-facing%20(ExternalURL%20is%20populated)%20User1's%20experience%20will%20depend%20on%20whether%20the%20device%20supports%20Autodiscover.%3C%2FP%3E%0A%3CP%3EFor%20the%20legacy%20device%20scenario%20(i.e.%2C%20the%20device%20does%20not%20support%20Autodiscover%20or%20protocol%20version%2012.1%20or%20later)%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EUser1's%20device%20is%20already%20configured%20to%20use%20the%20namespace%20mail.contoso.com.%3C%2FLI%3E%0A%3CLI%3EUser1's%20device%20attempts%20to%20synchronize.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20authenticate%20the%20user%20and%20access%20Active%20Directory%20and%20retrieve%20the%20following%20information%3A%3COL%3E%0A%3CLI%3EUser's%20mailbox%20version%3C%2FLI%3E%0A%3CLI%3EUser's%20mailbox%20location%20(AD%20Site)%3C%2FLI%3E%0A%3CLI%3EThe%20ExternalURL%20of%20Exchange%202007%20Client%20Access%20Server(s)%20EAS%20virtual%20directory%20located%20within%20the%20mailbox's%20AD%20site%20(if%20it%20exists)%3C%2FLI%3E%0A%3CLI%3EThe%20InternalURL%20of%20the%20Exchange%202007%20Client%20Access%20Servers(s)%20EAS%20virtual%20directory%20located%20within%20the%20mailbox's%20AD%20site%20(if%20it%20exists)%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLI%3E%0A%3CLI%3EWhile%20the%20user's%20mailbox%20does%20reside%20in%20the%20%22Internet%20Facing%20AD%20Site%22%20and%20the%20ExternalURL%20is%20populated%20on%20CAS2007%20in%20that%20site%2C%20because%20the%20device%20does%20not%20support%20redirection%20via%20Autodiscover%2C%20CAS2010%20will%20proxy%20the%20connection%20to%20the%20Exchange%202007%20CAS%20infrastructure%20in%20the%20%22Internet%20Facing%20AD%20Site%22.%20Specifically%20the%20request%20is%20proxied%20to%20CAS2007%20(InternalURL%20value)%20%5CMicrosoft-Server-ActiveSync%5CProxy%20virtual%20directory.%3C%2FLI%3E%0A%3CLI%3ECAS2007%20will%20authenticate%20the%20user%20and%20retrieve%20and%20render%20the%20mailbox%20data%20from%20the%20Exchange%202007%20mailbox%20server%20and%20will%20provide%20the%20rendered%20data%20back%20to%20the%20CAS2010%20server.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20expose%20the%20data%20to%20the%20end%20user.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EFor%20the%20Autodiscover-supported%20device%20scenario%20(e.g.%2C%20Windows%20Mobile%206.1%20or%20later)%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EUser3's%20device%20is%20already%20configured%20to%20use%20the%20namespace%20mail.contoso.com.%3C%2FLI%3E%0A%3CLI%3EUser3's%20device%20attempts%20to%20synchronize.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20authenticate%20the%20user%20and%20access%20Active%20Directory%20and%20retrieve%20the%20following%20information%3A%3COL%3E%0A%3CLI%3EUser's%20mailbox%20version%3C%2FLI%3E%0A%3CLI%3EUser's%20mailbox%20location%20(AD%20Site)%3C%2FLI%3E%0A%3CLI%3EThe%20ExternalURL%20of%20Exchange%202007%20Client%20Access%20Server(s)%20EAS%20virtual%20directory%20located%20within%20the%20mailbox's%20AD%20site%20(if%20it%20exists)%3C%2FLI%3E%0A%3CLI%3EThe%20InternalURL%20of%20the%20Exchange%202007%20Client%20Access%20Servers(s)%20EAS%20virtual%20directory%20located%20within%20the%20mailbox's%20AD%20site%20(if%20it%20exists)%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLI%3E%0A%3CLI%3ESince%20the%20user's%20mailbox%20does%20reside%20in%20the%20%22Internet%20Facing%20AD%20Site%22%2C%20the%20ExternalURL%20is%20populated%20on%20CAS2007%20in%20that%20site%2C%20and%20the%20device%20does%20support%20redirection%20via%20Autodiscover%20(this%20is%20determined%20by%20the%20protocol%20version%20of%20ActiveSync%20when%20establishing%20a%20synchronization%3B%20it%20must%20be%20version%2012.1%20or%20later)%2C%20CAS2010%20will%20return%20a%20response%20(HTTP%20error%20code%20451)%20indicating%20that%20the%20device%20should%20use%20legacy.contoso.com%20namespace%20for%20all%20synchronization%20events.%26nbsp%3B%20You%20can%20see%20the%20response%20in%20the%20IIS%20logs%3A%3CBLOCKQUOTE%3E%0A%3CP%3EPOST%20%2FMicrosoft-Server-ActiveSync%2Fdefault.eas%20User%3Duser3%26amp%3BDeviceId%3Dfoo%26amp%3BDeviceType%3DPocketPC%26amp%3BCmd%3DSettings%26amp%3BLog%3DRdirTo%3Ahttps%253a%252f%252flegacy.contoso.com%252fMicrosoft-Server-ActiveSync_Error%3AMisconfiguredDevice_%20443%20contoso%5Cuser3%2010.20.100.117%20MSFT-PPC%2F5.2.5082%20451%200%200%2017%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3C%2FLI%3E%0A%3CLI%3EThe%20device%20updates%20its%20profile%20to%20use%20legacy.contoso.com%20and%20attempts%20to%20synchronize%20with%20legacy.contoso.com.%3C%2FLI%3E%0A%3CLI%3ECAS2007%20will%20authenticate%20the%20user%20and%20retrieve%20and%20render%20the%20mailbox%20data%20from%20the%20Exchange%202007%20mailbox%20server%20and%20will%20provide%20the%20rendered%20data%20back%20to%20the%20device.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CSTRONG%3E%3CEM%3EImportant%3C%2FEM%3E%3C%2FSTRONG%3E%3A%20Some%20third-party%20ActiveSync%20devices%20advertise%20support%20for%20protocol%20version%2012.1%20or%20later%3B%20however%2C%20they%20do%20not%20correctly%20process%20the%20451%20error%20response%20by%20updating%20the%20device%20profile.%26nbsp%3B%20For%20these%20devices%20you%20will%20have%20to%20manually%20update%20the%20namespace%20in%20the%20device%20ActiveSync%20profile%20once%20CAS2010%20has%20been%20deployed%20with%20the%20legacy.contoso.com%20namespace.%26nbsp%3B%20Please%20contact%20your%20device%20manufacturer%20to%20determine%20when%20they%20will%20provide%20support%20for%20redirection.%3C%2FP%3E%0A%3CP%3ENow%20let's%20consider%20User2%20from%20the%20Exchange%202007%20coexistence%20diagram.%26nbsp%3B%20User2%20could%20be%20utilizing%20a%20third-party%20ActiveSync%20device%20or%20a%20Windows%20Mobile%20device.%26nbsp%3B%20For%20Windows%20Mobile%20support%2C%20the%20device%20is%20either%205.0%2C%206.0%2C%20or%206.1%2B%20or%20later.%26nbsp%3B%20Note%20that%206.1%2B%20supports%20Autodiscover%2C%20but%20since%20User2%20is%20located%20in%20the%20%22Non-Internet%20Facing%20AD%20Site%22%2C%20the%20redirect%20functionality%20does%20not%20come%20into%20play%20here.%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EUser2's%20device%20is%20already%20configured%20to%20use%20the%20namespace%20mail.contoso.com.%3C%2FLI%3E%0A%3CLI%3EUser2's%20device%20attempts%20to%20synchronize.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20authenticate%20the%20user%20and%20access%20Active%20Directory%20and%20retrieve%20the%20following%20information%3A%3COL%3E%0A%3CLI%3EUser's%20mailbox%20version%3C%2FLI%3E%0A%3CLI%3EUser's%20mailbox%20location%20(AD%20Site)%3C%2FLI%3E%0A%3CLI%3EThe%20ExternalURL%20of%20Exchange%202007%20Client%20Access%20Server(s)%20EAS%20virtual%20directory%20located%20within%20the%20mailbox's%20AD%20site%20(if%20it%20exists)%3C%2FLI%3E%0A%3CLI%3EThe%20InternalURL%20of%20the%20Exchange%202007%20Client%20Access%20Servers(s)%20EAS%20virtual%20directory%20located%20within%20the%20mailbox's%20AD%20site%20(if%20it%20exists)%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLI%3E%0A%3CLI%3ESince%20the%20user's%20mailbox%20resides%20in%20the%20%22Non-Internet%20Facing%20AD%20Site%22%20and%20the%20ExternalURL%20is%20not%20populated%20on%20any%26nbsp%3B%20Client%20Access%20server(s)%20in%20that%20site%2C%20CAS2010%20will%20proxy%20the%20connection%20to%20the%20Exchange%202007%20CAS%20infrastructure%20in%20the%20%22Non-Internet%20Facing%20AD%20Site%22.%20Specifically%20the%20request%20is%20proxied%20to%20CAS2007%20(InternalURL%20value)%20%5CMicrosoft-Server-ActiveSync%5CProxy%20virtual%20directory%3C%2FLI%3E%0A%3CLI%3ECAS2007%20will%20authenticate%20the%20user%20and%20retrieve%20and%20render%20the%20mailbox%20data%20from%20the%20Exchange%202007%20mailbox%20server%20and%20will%20provide%20the%20rendered%20data%20back%20to%20the%20CAS2010%20server.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20expose%20the%20data%20to%20the%20end%20user.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CH3%20id%3D%22toc-hId-754193109%22%20id%3D%22toc-hId-754194971%22%3EWhat%20happens%20when%20the%20user's%20mailbox%20is%20moved%20to%20Exchange%202010%3F%3C%2FH3%3E%0A%3CP%3EFor%20this%20scenario%2C%20the%20important%20thing%20to%20understand%20is%20how%20is%20the%20device%20currently%20configured%3F%20Either%20the%20device%20is%20utilizing%20the%20legacy.contoso.com%20namespace%20(due%20to%20Autodiscover%20during%20device%20setup%20or%20due%20to%20the%20redirect)%2C%20or%20the%20device%20is%20utilizing%20the%20mail.contoso.com%20namespace%20(and%20thus%20CAS2010%20is%20proxying%20to%20the%20legacy%20CAS%20or%20Exchange%202003%20mailbox%20server).%3C%2FP%3E%0A%3CP%3EFor%20the%20Autodiscover-supported%20device%20scenario%20case%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EUser3's%20device%20is%20already%20configured%20to%20use%20the%20namespace%20legacy.contoso.com.%3C%2FLI%3E%0A%3CLI%3EUser3's%20device%20attempts%20to%20synchronize.%3C%2FLI%3E%0A%3CLI%3ECAS2007%20will%20authenticate%20the%20user%20and%20access%20Active%20Directory%20and%20retrieve%20the%20following%20information%3A%3COL%3E%0A%3CLI%3EUser's%20mailbox%20version%3C%2FLI%3E%0A%3CLI%3EUser's%20mailbox%20location%20(AD%20Site)%3C%2FLI%3E%0A%3CLI%3EThe%20EAS%20virtual%20directory%20ExternalURL%20of%20the%20Client%20Access%20Server(s)%20that%20matches%20the%20mailbox%20version%2C%20located%20within%20the%20mailbox's%20AD%20site%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLI%3E%0A%3CLI%3ESince%20the%20user's%20mailbox%20version%20is%20now%20greater%20than%20the%20CAS2007%20version%2C%20CAS2007%20must%20either%20respond%20with%20a%20403%20or%20451%20response%20code.%20Since%20the%20ActiveSync%20protocol%20version%20of%20User3's%20device%20is%2012.1%20or%20later%2C%20the%20device%20supports%20Autodiscover.%20Therefore%2C%20CAS2007%20will%20return%20a%20response%20(HTTP%20error%20code%20451)%20indicating%20that%20the%20device%20should%20use%20mail.contoso.com%20namespace%20for%20all%20synchronization%20events.%3C%2FLI%3E%0A%3CLI%3EThe%20device%20updates%20its%20profile%20to%20use%20mail.contoso.com%20and%20attempts%20to%20synchronize%20with%20mail.contoso.com.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20authenticate%20the%20user%20and%20retrieve%20and%20render%20the%20mailbox%20data%20from%20the%20Exchange%202010%20mailbox%20server%20and%20will%20provide%20the%20rendered%20data%20back%20to%20the%20device.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EFor%20the%20legacy%20device%20case%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EUser1's%20device%20is%20already%20configured%20to%20use%20the%20namespace%20mail.contoso.com.%3C%2FLI%3E%0A%3CLI%3EUser1's%20device%20attempts%20to%20synchronize.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20authenticate%20the%20user%20and%20access%20Active%20Directory%20and%20retrieve%20the%20following%20information%3A%3COL%3E%0A%3CLI%3EUser's%20mailbox%20version%3C%2FLI%3E%0A%3CLI%3EUser's%20mailbox%20location%20(AD%20Site)%3C%2FLI%3E%0A%3CLI%3EThe%20EAS%20virtual%20directory%20ExternalURL%20of%20the%20Client%20Access%20Server(s)%20that%20matches%20the%20mailbox%20version%2C%20located%20within%20the%20mailbox's%20AD%20site%3C%2FLI%3E%0A%3CLI%3EThe%20EAS%20virtual%20directory%20InternalURL%20of%20the%20Client%20Access%20Server(s)%20that%20matches%20the%20mailbox%20version%2C%20located%20within%20the%20mailbox's%20AD%20site%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLI%3E%0A%3CLI%3EBecause%20the%20device%20does%20not%20support%20Autodiscover%20(protocol%20version%20is%20less%20than%2012.1)%2C%20prior%20to%20the%20mailbox%20move%2C%20CAS2010%20simply%20proxied%20the%20ActiveSync%20traffic%20to%20CAS2007.%20Now%20that%20the%20mailbox%20is%20moved%2C%20CAS2010%20simply%20retrieves%20and%20renders%20the%20mailbox%20data%20from%20the%20Exchange%202010%20mailbox%20server.%3C%2FLI%3E%0A%3CLI%3ECAS2010%20will%20expose%20the%20data%20to%20the%20end%20user.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CH3%20id%3D%22toc-hId--1797963852%22%20id%3D%22toc-hId--1797961990%22%3EConclusion%3C%2FH3%3E%0A%3CP%3EHopefully%20this%20information%20dispels%20some%20of%20the%20myths%20around%20proxying%20and%20redirection%20logic%20for%20Exchange%20ActiveSync%20in%20Exchange%20Server%202010%20when%20upgrading%20either%20from%20Exchange%202007%20or%20Exchange%202003.%26nbsp%3B%20Please%20let%20us%20know%20if%20you%20have%20any%20questions.%3C%2FP%3E%0A%3CP%3E--%20%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Farchive%2F2005%2F08%2F25%2F409819.aspx%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ERoss%20Smith%20IV%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E

We're happy to announce that we've enhanced Exchange Server Deployment Assistant to include support for configuring rich coexistence (also known as “hybrid deployment”) for organizations interested in maintaining some users on-premises with Exchange 2010 and some users hosted in the cloud by Microsoft Office 365 for enterprises. This scenario is in addition to the existing support for configuring rich coexistence between on-premises Exchange 2003 and Exchange 2007 organizations and Office 365.

The new coexistence information for the Exchange 2010 environment is only available in English at this time and requires that your existing Exchange 2010 servers are updated to Exchange Server 2010 Service Pack 1 (SP1).

Rich coexistence (“hybrid deployment”) offers organizations the ability to extend the feature-rich experience and administrative control they have with their existing on-premises Microsoft Exchange organization to the cloud. It provides the seamless look and feel of a single Exchange organization between an on-premises organization and a cloud-based organization. In addition, coexistence can serve as an intermediate step to moving completely to a cloud-based Exchange organization. This approach is different than the simple Exchange migration (aka cutover migration) and staged Exchange migration options currently offered by Office 365 outlined in Email Migration Overview in Exchange Online help.

If you're not already familiar with the Exchange Deployment Assistant, it allows you to create Exchange Server 2010 on-premises configuration and deployment instructions that are customized to your environment. It asks you a small set of simple questions and it provides a checklist with instructions that are designed to deploy or configure Exchange 2010 based on your answers. In addition to the online checklist, you can even print a PDF of your checklist.


Figure 1: The Exchange Server Deployment Assistant (ExDeploy) is a web-based tool that helps you upgrade to Exchange 2010 on-premises, deploy a hybrid on-premises and Exchange Online organization or migrate to Exchange Online

Your feedback is very important for the continued improvement of this tool. We would love your feedback on this new scenario and any other area of the Deployment Assistant. Feel free to either post comments on this blog post, provide feedback in the Office 365 community migration and coexistence forum, or send an email to edafdbk@microsoft.com via the 'Feedback' link located in the header of every page of the Deployment Assistant. Thanks!

The Exchange Team

4 Comments
Not applicable

very good  

Not applicable

Now if only there were screenshots included :) I presume the tool will be updated again when 2010 SP2 will be released later in the year? It's a great tool!

Not applicable

Great. Keep updating it.

Not applicable

After reading you site, Your site is very useful for me .I bookmarked your site!