Office Track: Exchange 2013 in the real world - Michael Van Horenbeeck


Published on

ITPROceed 2014 session by Michael Van Horenbeeck
Exchange 2013 in the real world

Published in: Software, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Office Track: Exchange 2013 in the real world - Michael Van Horenbeeck

  1. 1. Exchange 2013 in the real world: from deployment to management Michael Van Horenbeeck (@mvanhorenbeeck)
  2. 2. Agenda What you want things to look like I…am…Frankenstein? How Exchange plays with the other kids Gotchas…? Anyone…? What just happened to my server? Q & A
  3. 3. Assumption You know what Exchange 2013 is and have heard about the new architecture paradigm… Fact If you’re looking for more info, Channel 9 is the place to go!
  4. 4. Planning & Design What you want things to look like…
  5. 5. Namespace Design - PA mail VIP mail VIP • For a site resilient datacenter pair, a single namespace / protocol is deployed across both datacenters – – HTTP: – IMAP: – SMTP: • Load balancers are configured without session affinity, one VIP / datacenter • Round-robin, geo-DNS, or other solutions are used to distribute traffic equally across both datacenters
  6. 6. Topology - PA DAG mail VIP mail VIP Witness Server • Separate Active Directory Sites per physical site • Deploy unbound DAG model spanning each DAG across two datacenters • Active copies across all servers in the DAG • Deploy 4 copies, 2 copies in each datacenter • One copy will be a lagged copy (7 days) with automatic play down enabled • Single network for replication and client traffic • third datacenter for Witness server, if possible
  7. 7. Server Design - PA • Multi-role servers deployed on commodity hardware • JBOD storage utilizing large capacity 7.2K SAS disks • Multiple databases / volume • AutoReseed with hot spare DAG mail VIP
  8. 8. Selina (somewhere in NA) DNS Resolution DAG na VIP na VIP Batman (somewhere in Europe) DNS Resolution DAG eur VIP eur VIP Preferred Architecture
  9. 9. Summary New building block architecture provides flexibility in load balancing, namespace planning and high availability Take advantage of large, low-cost mailboxes by utilizing large capacity 7.2K RPM disks Simpler is better!
  10. 10. Deploying Exchange 2013
  11. 11. Preparing for Exchange 2013 Active Directory Minimum Requirements At least one Windows Server 2003 SP2 or higher* Global Catalog in each AD site with Exchange installed *Use of Windows Server 2012 R2 requires a supported Exchange version At least one writable Domain Controller in each AD site with Exchange Servers installed AD Forest Functional Level must be Windows Server 2003 or higher
  12. 12. OS Requirements Windows Server 2008 R2 SP1 Standard or Enterprise editions Standard edition ok for CAS-only & non-DAG MBX Enterprise edition necessary for DAG joined MBX Windows Server 2012 or 2012 R2 Standard or Datacenter editions 2012 R2 is only supported with 2013 Service Pack 1 or later
  13. 13. OS Requirements .NET framework 4.5 4.5.1 strongly recommended Windows Management Framework 3.0 Unified Communications Managed API 4.0 Other expected OS roles/features (IIS etc…)
  14. 14. Preparing for Exchange Server 2013 Recent Windows Server 2012 R2 Support Updates 2013 SP1 or later 2013 CU3 or earlier 2010 SP3 RU5 or later 2007 SP3 RU13 or later Install on 2012 R2 2012 R2 DCs and a 2012 or lower DFL/FFL 2012 R2 DCs and a 2012 R2 DFL/FFL
  15. 15. Installing exchange 2013
  16. 16. Preparing for Exchange Server 2013 An OAB modification before installing the first Exchange 2013 servers: Exchange 2013 creates a new default OAB for the org. Avoid clients downloading the new default OAB by specifying the existing OAB on all legacy DBs prior to installing Exchange 2013 [PS] C:>Get-OfflineAddressBook | FT Name,IsDefault,ExchangeVersion -AutoSize Name ---- Default Offline Address Book Default Offline Address Book (Ex2013) True 0.20 ( False 0.1 (8.0.535.0) --------- --------------- IsDefault Exchange Version
  17. 17. After Installation (SP1/CU4) The third-party or custom-developed transport agents cannot be installed correctly You cannot enable third-party products that rely on transport agents The Microsoft Exchange Transport service (MSExchangeTransport.exe) cannot start automatically You receive an error message: The TransportAgentFactory type must be the Microsoft .NET class type of the transport agent factory Problem occurs because global assembly cache (GAC) policy configuration files contain invalid XML code Hotfix and Fixit at Download script from Slide courtesy of Scott Schnoll
  18. 18. Interoperability
  19. 19. MBX2013 CAS2013 Load Balancer HTTP Proxy IIS DB Protocol Head HTTP MBX2007 CAS2007 Load Balancer IIS DB Middle Tier Layer OWA Legacy Redirect Request MBX2007 DB Cross-Site OWA Proxy Request CAS2007 IIS Middle Tier Layer Outlook Anywhere Proxy Request ActiveSync Proxy Request SiteBoundary CAS2013 Client Protocol Connectivity Flow Slide courtesy of Microsoft
  20. 20. Ex2007 Coex: URL Configuration Configure a legacy namespace for the ExternalURL values of the Exchange 2007 Virtual Directories (OWA, EWS, UM, OAB, EAS) Blank out the EAS Virtual Directory External URL if Exchange 2013 is deployed in the same site * It doesn’t need to be ;-)
  21. 21. MBX2013 CAS2013 Load Balancer HTTP Proxy IIS DB Protocol Head HTTP Legacy Proxy Request MBX2010 DB Cross-Site Legacy Proxy Request CAS2010 IIS Middle Tier Layer Load Balancer Cross-Site OWA Redirect Request SiteBoundary MBX2010 CAS2010 Load Balancer DB Middle Tier Layer IIS CAS2013 Client Protocol Connectivity Flow Slide courtesy of Microsoft
  22. 22. MBX CAS Load Balancer HTTP Proxy IIS DB Protocol Head Local Proxy Request HTTP HTTP SiteBoundary MBX CAS Load Balancer HTTP Proxy IIS DB Protocol Head HTTP OWA Cross-Site Redirect Request HTTP MBX DB Protocol Head HTTP Cross-Site Proxy Request HTTP SiteBoundary CAS HTTP Proxy IIS CAS2013 Client Protocol Connectivity Flow Slide courtesy of Microsoft
  23. 23. Managed Availability
  24. 24. What is ‘Managed Availability’? “Exchange’s built-in monitoring and remediation center” Probe Monitor Responder
  25. 25. Managed Availability Probes Probes based on HealthSet Models: Client Protocols Storage Mail Flow Migration “Fabric”
  26. 26. Retrieving Server Health Get-HealthReport <server> Get-ServerHealth <server> <-HealthSet>
  27. 27. DEMO Managed Availability in a real-time production environment…
  28. 28. Q & A Michael Van Horenbeeck Twitter: @mvanhorenbeeck Blog:
  29. 29. Resources Various slide decks from the Microsoft Exchange Conference: -
  30. 30. And take home the Lumia 1320 Present your feedback form when you exit the last session & go for the drink Give Me Feedback
  31. 31. Follow Technet Belgium @technetbelux Subscribe to the TechNet newsletter Be the first to know
  32. 32. Belgiums’ biggest IT PRO Conference