O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Going Hybrid with Exchange 2013

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Carregando em…3
×

Confira estes a seguir

1 de 32 Anúncio

Mais Conteúdo rRelacionado

Quem viu também gostou (13)

Anúncio

Semelhante a Going Hybrid with Exchange 2013 (20)

Anúncio

Mais recentes (20)

Going Hybrid with Exchange 2013

  1. 1. Alberto Pascual · Office365 MVP
  2. 2. ServerVirtualizationAlbertoPascual • Microsoft Certifications and awards - Office365 MVP - MCSA Windows Server 2008 - MCITP Windows Server 2008 Enterprise Administrator - MCTS 70-680 / 70-640 / 70-642 / 70-643 - Microsoft Specialist – Administering Office365 for SMB (74-324) - MAP in 2010 and 2013 - Small business specialist - Microsoft Community Contributor 2013 and 2014 • ITPro.es member - http://blogs.itpro.es/guruxp • More than 20 years with IT • Office365 migrations and deployments experienced • Spanish Office365 Community forums Contributor and also English Technet fórums • Co-Founder of the very first Office365 Community in Spain @guruxp a.pascual@Outlook.com @guruxp a.pascual@Outlook.com
  3. 3. How old are you with Exchange?
  4. 4. On-Prem VS Cloud VS
  5. 5. On-Prem VS Cloud VS
  6. 6. On-Prem VS Cloud
  7. 7. Why not going hybrid?  Best of two worlds  Ability to go back and forth with mailboxes  Federation Trust (enables free/busy, calendar sharing, etc)  All in one management from on-prem  More storage (mailbox, mailbox+Online archive, Online archive)  Client autoconfiguration  No new profile or OST regeneration needed  No local bandwidth shared with mobile users
  8. 8. Requirements for going hybrid  Exchange 2010SP3+ / 2013CU2+  If Exchange 2007 > SP3RU10 AND at least one Exchange 2013CU2 CAS and MBX roles*  Office365 M, G, E and A plans. So NO SB plans  Office365 tenant must be 15.0.620.28+ and no Transitioning services true status:  Custom domain registered already in Office365 Subscription  Autodiscover DNS record correctly configured pointing to on-prem CAS server  WAAD Sync Tool (DirSync) deployed and working  SAN Certificate with EWS and Autodiscover URIs included (sorry no self-signed certs)  IF want Online Archive feature: ADFS and SSO is recommended  Always go with RCA tool:  What about Edge servers?: Exchange 2010 SP3+ OR Exchange 2013 SP1 Get-OrganizationConfig | Format-List AdminDisplayVersion,IsUpgradingOrganization https://testconnectivity.microsoft.com
  9. 9. Going Hybrid!
  10. 10. Centralized Transport  Great for compliance and regulations  Secure Mail is the main base  The OnPremisesSmartHost FQDN can be:  A Single EX2013CAS, EX2013/2010 EDGE server  Multiple round robin EX2013CAS, EX2013/2010 EDGE servers  Multiple LB EX2013CAS, EX2013/2010 EDGE servers (great for High availability)  Create an extra “*.*” connector to forward outgoing mail through EOP from On-Premises.
  11. 11. Done? , not yet…
  12. 12. MRS  Mailbox Replication Service Proxy allows you to move mailboxes to/from Exchange Online  You can choose to move Mailbox, Archive or both  Can be Configured via GUI or through PS  Can schedule mailbox moves Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -MRSProxyEnabled $true
  13. 13. What about EDGE?  Good for not exposing internal CAS or MBX servers to Internet  Optional but recommended  Exchange 2010 SP3 or Exchange 2013 SP1
  14. 14. THANKS!

×