Herzlich willkommen. Was ist neu in Exchange

Transcription

1 Herzlich willkommen Was ist neu in Exchange

2 Vorstellung der Referenten Markus Luchsinger Datacenter und Microsoft Solution Architekt connectis AG EMBA FH, IDV-TS, MCITP und MCT Seit 2001 Trainer bei Digicomp Markus Hengstler Senior Systems Engineer UMB AG MCITP, MCT und «Microsoft Certified Master: Exchange 2010» Seit 2001 Trainer bei Digicomp 2

3 Was ist neu in Exchange Agenda Architekturänderungen Client Zugriff Vertiefte Integration mit SharePoint und Lync Management Anbindung an die Cloud Installation / Migration Was fehlt.. Q&A 3

4 Architectural Changes - Overall Evolution from 2000 to 2010 Ex Ex CAS HT L7 LB C C C H H H Ex Ex MBX MBX MBX MBX MBX MBX Manual config Backups and hardware solutions for reliability Separate roles Support cheaper storage Separate HA solutions DAG RBAC Hybrid deployments 2000/

5 Architectural Changes - Overall Exchange 2010 Role Architecture Forefront Online Protection for Exchange Edge Transport Routing and AV/AS Internal Network Hub Transport Routing and policy Unified Messaging Voice mail and voice access External SMTP servers Mailbox Stores mailbox and public folder items Phone system (PBX or VOIP) Mobile phone Web browser Layer 7 LB Client Access Client connectivity Web services AD Outlook (remote user) Outlook (local user) Line of business application 5

6 Architectural Changes - Overall Problems Version compatibility all roles needs to have the same version Geo-affinity CAS/HT/MBX has to be on present on every site to work Complicated deployments Correct load balancing is complex to achieve and costly Many namespaces needed for site resilient designs 6

7 Architectural Changes - Overall NEW Exchange 2013 Architecture 2 Building Blocks Client Access Array Database Availability Group Loosely coupled (Versioning) Deployment simplicity L4 LB L4 LB C M C M Simplify for scale, balanced utilization and isolation Integrate HA for all roles Simplify network architecture

8 Architectural Changes - Overall Wrap-Up Ex Ex Ex Ex CAS MBX HT MBX L7 LB C C C H H H M M M M C M L4 LB C M 2000/

9 Layer 4 LB Architectural Changes - Overall Exchange 2010 Role Architecture Exchange Online Protection Internal Network Unified Messaging Phone system (PBX or VOIP) External SMTP servers Edge Exchange 2010 Transport Rout. and AV/AS CAS Array DAG Mobile phone Web browser Outlook (remote user) Outlook (local user) Line of business application AD

10 Architectural Changes - Overall Every Server is an Island EWS protocol MRS proxy protocol SMTP Protocols, Server Agents EWS RPC CA MRS MRSP roxy Transport Assistants Custom WS Transport RPC CA MRS MRSP roxy EWS Assistants Business Logic XSO MailItem CTS Other API XSO MailItem CTS Other API Storage Store Content index Store Content index File system ESE File system ESE Server 1 Server

11 Architectural Changes - Overall OAB OAB generation is not bound to a specific server anymore OAB is generated by each MB-Server that hosts the Organization mailbox OAB for user download is not stored on the CAS only proxies the file from the correct MB-Server to the client More to come on the EHLO-Blog 11

12 Architectural Changes Overall Managed Availability Monitor and recovery is integrated within Exchange Detects (includes integrated synthetic transactions) and recovers automatically if possible (or to take the server offline in the worst case) It s user focused if you can t measure it, you can t monitor it Also focus on problem resolution and not on root cause analysis blogs.technet.com 12

13 Architectural Changes Overall Anti-Spam / Anti-Malware Anti-Malware now included (Exchange 2010 native only possible with implementing of transport rules AFTER the Virus was identified) The included Anti-Spam agents are relatively unchanged from Exchange 2010 Online Protection for Exchange (FOPE) hosted filtering service is still available - Microsoft Exchange Online Protection (EOP) is the new version of this service 13

14 Architectural Changes Client Access Server Consist of of three components: Client access protocols (HTTP, IMAP, POP) SMTP UM Call Router Thin, stateless (protocol sess.), nothing remains in memory, disk etc. (no session affinity needed for Load balancing) Exchange-aware proxy server Supports proxy and redirection logic for client protocols Capable of supporting legacy servers with redirect or proxy logic Public folder access finally also going through CAS No more RPC/MAPI Access for the clients Can be deployed with a single world-wide namespace 14

15 Architectural Changes Client Access Server Access to the CAS (and Mailbox) OWA Outlook EAS EAC PowerShell IMAP SMTP Telephony LB Client Access IIS HTTP Proxy Load Balancer POP, IMAP SMTP UM Redirect SIP + RTP IIS POP IMAP Transport UM Mailbox RPS RpcProxy RPC CA OWA, EAS, EWS, ECP, OAB MDB MailQ 15

16 Architectural Changes Client Access Server Single Common Namespace Example with Round-Robin DNS Peter (Somewhere in CH) DNS Resolution VIP #1 VIP #2 DNS Resolution via Geo-DNS mail.firma.ch Round-Robin between # of VIPs Round-Robin between # of VIPs VIP #1 VIP #2 Peter (Traveling in US) DAG CH DAG US NA-DC1 NA-DC2 NA-DC1 NA-DC2

17 Architectural Changes Mailbox Server Access only through CAS for everything Server that hosts the components that process, render and store Exchange data includes now all components (previously spread out in different roles) The database is still ESE, but the engine is using FAST and provides better and much faster search and index performance Rewritten store each DB has it s own Store worker process 99% less IOPS then in Exchange 2003 Possible to have multiple DBs per LUN Use a single logical disk partition per physical disk The number of database copies configured per volume should be equal to the number of copies of each database 17

18 Architectural Changes Mailbox Server Public Folder Public folders are stored in public folder mailboxes - no public folder databases anymore Each public folder mailbox will have unique data There is no PF replication as in previous versions. As the public folder data is stored in PF mailboxes, DAG can be used for high availability. No more multi-master replication As Outlook 2003 & earlier clients are not supported in 2013, there is no need form system public folders Public folders can be administered using the EAC & Shell (fully integrated now) 18

19 Architectural Changes Transport components Split of former Hub Transport role into Front End Transport, Transport Service and Mailbox Transport Service 19

20 Architectural Changes Transport components Delivery Groups are the new targets in Routing decisions: DAG, Mailbox DG, Connector Source Server, AD Site, Server List (DL Expansion) 20

21 Architectural Changes Transport components Safety Net (former Transport Dumpster) with configurable retention time (2 days) works in conjunction with Shadow Redundancy 21

22 Architectural Changes Compliance In-Place ediscovery allows searches for content in all Wave15 products Exchange, Sharepoint and Lync simultanously In-Place Hold (Legal Hold) is more granular and can be adjusted to specific time ranges or for specific objects. Also, archived Lync content can be searched inside the Exchange Mailbox Data Loss Prevention (DLP) warns or restricts if sensitive content is about to be sent out of the organization 22

23 Client Access - Outlook 2013 Outlook 2013 connects to CAS by OA (RPCoverHTTPS) only Support for Apps for Office (e.g. Bing Maps or Weather) Office Web Apps Server is used by all Wave15 products to preview or view Office documents Attachment Reminder Sync Slider for Cached Mode allows setting of time range OST about 40% smaller than before People Hub integrates information from social networks in contacts Active Sync can be used to connect Outlook to Exchange (Hotmail) 23

24 Client Access - Outlook Web App 2013 Offline Support with HTML5. Requirement: IE 10, Chrome 17+ or Safari 5 Support for Outlook Apps Automatic optimization for tablet- or smartphone sized screens(touch- Wide, Touch-Narrow) (?layout=twide or tnarrow) 24

25 Integration Lync 2013 Requirements: Mailbox must be on Exchange 2013 OWA/Lync Integration Exchange 2013 Autodiscover Data accessible from Lync S2SOAuth Trust between Lync and Exchange Lync Storage Service and Unified Communications Managed API Features: Archiving Integration uses hidden folder (Purges) inside the Mailbox to archive conversations (instead of Lync SQL archive) Unified Contact Store accesses EWS on Exchange to store and retrieve contacts. Initialy, Lync contacts get migrated to the mailbox High Resolution Photos: AD 48x48, Outlook 96x96, Lync - 648x648 UM Integration: The UM role is split between CAS and MBX 25

26 Integration SharePoint 2013 ediscovery with SharePoint ediscovery Center over multiple SharePoint farms and Exchange Servers Site Mailboxes allow access to mails inside Sharepoint and to Sharepoint documents from Outlook 26

27 Integration - Demo Lync SharePoint Public Folder 27

28 Exchange Administrative Center Web-based administration through ECP website Allows administration of on-premises and online deployments Can be made accessible from outside the intranet Mailbox has to be on a Exchange 2013 server to work properly. Otherwise?ExchClientVer=15 can be added to the URL 28

29 Cloud integration Prerequisites Office 365 for enterprises AD sync Autodiscover DNS records Improvements Reduction of config tools Easier wizard process Two-factor (strong) authentication possible (need single sign-on) 29

30 Office 365 Exchange Online Preview status! Consider Cost HA Storage Security, privacy and regulatory compliance Migration Applications 30

31 Installation / Migration Exchange 2010 need SP3, required for co-existence with Exchange 2013, is scheduled for first half of 2013, same for Exchange 2007 SP3 (Update Rollup)!! -> not mentioned in Technet only on Blogs Coexistence also possible with mixed 2007/2010 environments AD 2003 forest functionality mode is enough (Schema update needed) 8 GB RAM minimum for MBX / 4 GB for CAS and 2008 R2 or 2012 OS 2013 mailbox users can access public folders hosted on Exchange 2010 or mailbox users can only access 2010 PFs. Install Mailbox role first Outlook 2013 works out of box. Outlook 2010 and 2007 needs an update to connect to Exchange Outlook 2003 and earlier are not supported with Exchange

32 What s missing Edge Server role No Public Folder access in OWA (most probably SP1) Only SSL-Bridging for CAS supported (no offloading) UAG cannot publish CAS A fix is expected in SP1 of TMG will work fine though. BUT TMG cannot be ordered after !! Important discontinued Feature RPC over TCP (MAPI from the clients ) Exchange 2013 does not support MAPI access (RPC), also not for third-party products. Outlook Anywhere (RPC over HTTPS) is the only method by which Outlook can connect, internally & externally Exchange 2013 is the LAST release that supports MAPI/CDO switch to EWS 32

33 Wrap up Building Blocks loosely coupled Simplified upgrade and inter operability No more direct access from clients to the MB-Server Rewritten Store service Public folder integration DLP Integration in Lync and SharePoint Outlook ost-file/cache mode enhancements Outlook Web Access enhancements New Admin Center 33

34 34