Eesti. Baltimaad. Põhja Euroopa. Priit Timpson Atea teenuste osakond

Office/Lync/Exchange/SharePoint 2013 Priit Timpson Atea teenuste osakond

Modern Interface Touch Mode Reading mode Editing PDFs Excel on multiple monitors SkyDrive - Connect to the Cloud, Connect to Your Content Outlook cache sizes, speed,.ost compression Etc. Office 2013

Full IPv6 support VDI plugin, allowing full A/V support in virtual desktop environments H.264 SVC codec support Skype federation support (coming) Hybrid deployments of on-premises and Lync Online cloud servers now supported (this capability is called "hybrid voice") Lync 2013

New role Office Web Apps server Consolidation of roles Director role optional not “recomended“ A\V Conferencing always on Front-End Archiving and Monitoring on Front-End (optional) Lync 2013 Std. also Persistent Chat on Front- End Lync 2013

Persistent Chat – alternative for distribution lists With this comes also new RBAC rolePersistent Chat Manager Lync 2013

Enterprise voice features – inter-trunk routing to connect an IP-PBX and a PSTN gateway Manager/delegate simultaneous ringing (multiple designated phones ring at the same time) Lync 2013 now supports M-N trunk routing. This allows you to have multiple trunks to different gateways, and a gateway to have multiple trunks to different Mediation Servers Hybrid voice with Lync Online Lync 2013

Disaster recovery and high-availability improvements Reduntant roles for common pool (same as in Lync 2010) No more Metropolitan Site Resilency New - Lync Pool pairing (Ent. with Ent.; Std. with Std.) both sites are active. Manual failover, failback Lync 2013

Lync Web App changes – Audio/Video over browser, no more Attendee New Mobility client – not jet relased and no dates. Will be supporting audio and video calls over mobile data, wi-fi Lync 2013

Coexistence and Migration Supported are Microsoft Lync Server 2010 Microsoft Office Communications Server 2007 R2 Migration to diffrent Forest not supported Public SSL, IP-s etc. Lync 2013

New Architecture! From Exchange server roles to 2 roles in Exchange Client Access Server role and Mailbox Server role Exchange 2013

Domain-joined machine in the internal Active Directory forest – Thin, stateless (protocol session) server Comprised of three components: – Client access protocols (HTTP, IMAP, POP) – SMTP – UM Call Router Exchange-aware proxy server – Understands requests from different protocols (OWA, EWS, etc.) – Supports proxy and redirection logic for client protocols – Capable of supporting legacy servers with redirect or proxy logic – Contains logic to route specific protocol requests to their destination end-point Exchange 2013 CAS

Load Balancer MDB HTTP Proxy IIS Client Access RPC CA Mailbox IIS RPS OWA, EAS, EWS, ECP, OAB POP, IMAP SMTP UM POP IMAP Transp ort UM SMTP POP, IMAP HTTP MailQ Client Protocol Architecture in Exchange 2013 RpcProxy SMTP SI P Redirect SIP + RTP POP/IMAP Outlook Web AppOutlookEASEACPowerShell

Outlook Connectivity in Exchange 2013 Exchange 2013 supports RPC/HTTP only; No RPC/TCP – Simplifies the protocol stack – Provides an extremely reliable and stable connectivity model because RPC session is always on Mailbox server hosting active copy – Eliminates need for RPC CAS Array namespace(s) – Eliminates end user interruptions like “The Exchange administrator has made a change that requires you to quit and restart Outlook” during mailbox moves

A Single Common Namespace Example Geographical DNS Solution Sue (somewhere in NA) DNS Resolution DAG VIP #1VIP #2 Sue (traveling in APAC) DNS Resolution via Geo-DNS Round-Robin between # of VIPs DAG VIP #3VIP #4 mail.contoso.com Round-Robin between # of VIPs

SMTP Inbound/Outbound Mail Flow Inbound Mail Flow 1.FET accepts initial SMTP conversation if source passes connection filtering 2.Applies protocol, sender, and recipient filtering based on message envelope up to the SMTP data command 3.Proxies the message to the appropriate destination Outbound Mail Flow 1.MBX 2013 determines if mail recipient is a remote destination and selects a FET within local site when the FrontEndProxyEnabled parameter on Send Connector is set to $true 2.MBX 2013 connects to FET and initiates SMTP conversation 3.FET proxies outbound connection to appropriate destination 16

Mailbox Server Role Server that hosts the components that process, render and store Exchange data – Includes components previously found in separate roles Only Client Access servers connect directly to the Mailbox server – Clients connect to Client Access servers Note – one exception is UM with RTP – Connectivity to a mailbox is always provided by the protocol instance local to the active database copy

Managed Store Store service process (Microsoft.Exchange.Store.Service.exe) – Manages worker process lifetime based on mount/dismount – Logs failure item when store worker process problems detected – Terminates store worker process in response to “dirty” dismount during failover Store worker process (Microsoft.Exchange.Store.Worker.exe) – One process per database, RPC endpoint instance is database GUID – Responsible for block-mode replication for passive databases – Fast transition to active when mounted – Transition from passive  active increases ESE cache size 5X

E2010 vs. E2013 Performance Comparison * Results based on daily Outlook cached mode Load Generator simulations (10 databases, 1000 users) to measure key metrics used to identify performance improvements/regressions (Beta2 build 466, subject to change) 48-76% IOPS reduction (disk IOPS capacity not expected to change) 18-41% Average RPC Latency reduction 17-34% increase in CPU per RPC processed (offset by additional CPU cores) ~4X increase in store memory overhead (~4GB vs. ~1GB not including ESE cache) 19

IOPS Reductions ~99.5% Reduction!

Support for Larger Mailboxes Large Mailbox Size is 100 GB+ – Aggregate Mailbox = Primary Mailbox + Archive Mailbox + Recoverable Items – 1-2 years of mail (minimum) Increase IW productivity Eliminate or reduce PST files Eliminate or reduce third-party archive solutions OST size control with Outlook Day15011 MB 1 Month MB 1 Year GB 2 Years GB 4 Years GB

Modern Public Folders Public folders based on the mailbox architecture Single-master model – Hierarchy is stored in a PF mailbox (one writeable) – Content can be broken up and placed in multiple mailboxes – The hierarchy folder points to the target content mailbox Because it’s a mailbox, it’s in a mailbox database…thus, – High availability achieved through continuous replication – No separate replication mechanism Similar administrative features to current PFs – No end-user changes MBX 2013 MBX 2013 CAS2013 MBX 2013 MBX 2013 MBX 2013 MBX 2013 Public logon Private logon Public logon Content Mailbox Hierarchy Mailbox

Modern Public Folders 1 - User connects to their home Public Folder mailbox first, which should be located near their primary mailbox. 2- Folder contents live in one specific mailbox for that folder. All content operations are redirected to the mailbox for that folder 3 – Folder hierarchy changes are intercepted and written to writeable copy of Public Folder hierarchy 4 – All Public Folder mailboxes listen for hierarchy changes and update similar to Outlook clients 5 - When a Public Folder mailbox gets full, move some folders to a new mailbox

New Search Foundation Primer Core Catalo g CTS Incoming Documents Filter Word Brea k Conte nt XForm MAR S Write r Incoming Queries “CTS Flow” IMS Content XForm Quer y Parse “IMS Flow” Results Uses Search Foundation Significantly improved query performance Significantly improved indexing performance

All core Exchange functionality for a given mailbox is served by the MBX 2013 server where that mailbox’s database is currently activated Mailbox access fails over when a database fails over Protocols shift to the server hosting the active database copy Managed Availability: Internal monitoring and high availability are tied together and can be used to detect and recover from problems as they occur and are discovered Best copy selection now includes health of services when selecting best copy (best copy and server selection) Failover time reductions Service Availability Improvements 25

DAG Multiple databases per volume Lagged copy automatic log play down w. Safty Net DAG Network autoconfig CAS and MBX recovery independent Transport HA - Every message is redundantly persisted before its receipt is acknowledged to the sender Etc. Exchange 2013 HA 26

Exchange 2013 Prerequisites Supported coexistence scenarios – Exchange Server 2010 SP3* – Exchange Server 2007 SP3 (+ coexistence RU*) Supported client access methods – Outlook 2013, Outlook 2010, Outlook 2007 – RPC over HTTP is only method of connectivity for Outlook clients – Entourage 2008 for Mac, Web Services Edition – Outlook for Mac 2011

Upgrading to Exchange 2013 From an existing Exchange 2007 environment RU E2007 SP3 CAS E2007 SP3 HUB E2007 SP3 MBX Clients Internet-facing site – upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2007 Servers RU 1. Prepare Install Exchange 2007 SP3 + RU across the ORG Prepare AD with Exchange 2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS Validate using Remote Connectivity Analyzer 6. Move mailboxes Build out DAG Move Exchange 2007 users to Exchange 2013 MBX 7. Repeat for additional sites 2. Deploy Exchange 2013 servers Install both Exchange 2013 MBX and CAS servers RU E2013 CAS E2013 MBX 3. Create legacy namespace Create DNS record to point to legacy Exchange 2007 CAS 4. Obtain and Deploy Certificates Obtain and deploy certificates on Exchange 2013 CAS servers configured with legacy namespace, Exchange 2013 namespace, and autodiscover namespace Deploy certificates on Exchange 2007 CAS legacy.contoso.com

Upgrading to Exchange 2013 (Cont’d) SP/RU E2010 or 2007 CAS E2010 or 2007 HUB E2010 or 2007 MBX Clients Internet facing site – Upgrade first autodiscover.contoso.com mail.contoso.com Intranet site Exchange 2010 or 2007 Servers SP/RU 1. Prepare Install Exchange SP and/or updates across the org Prepare AD with Exchange 2013 schema and validate 5. Switch primary namespace to Exchange 2013 CAS 6. Move mailboxes 7. Repeat for additional sites 3. Create legacy namespace 4. Obtain and deploy certificates 1 2. Deploy Exchange 2013 servers 29

Public Folder Migration Process Analyze existing Public Folders – Tool available to analyze existing Public Folder hierarchy to determine how many Exchange 2013 Public Folder mailboxes are recommended Copy Public Folder data – Users continue to access existing Public Folder deployment while data is copied – Data migration happens in the background Switch clients to Exchange 2013 Public Folders – There will be a short downtime while the migration is finalized Once migration completes, everyone switches at the same time – Can switch back, but any post migration Public Folder changes are lost

Exchange 2013 Archiving eDiscovery Integration with ohter MS 2013 products Hybrid Data Loss Prevention (DLP – identify, monitor, protect) OWA – Touch Mode, Offline Etc.

Questions/Küsimused?

Tänan! Priit Timpson Atea Eesti Systems Engineer