1 / 33

Eesti. Baltimaad. Põhja Euroopa.

Eesti. Baltimaad. Põhja Euroopa. Priit Timpson Atea teenuste osakond. Office/Lync/Exchange/SharePoint 2013. Priit Timpson Atea teenuste osakond. Office 2013 . Modern Interface Touch Mode Reading mode Editing PDFs Excel on multiple monitors

wyatt
Download Presentation

Eesti. Baltimaad. Põhja Euroopa.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. Office 2013 • Modern Interface • TouchMode • Readingmode • EditingPDFs • Excel on multiplemonitors • SkyDrive - Connect to the Cloud, Connect to Your Content • Outlook cachesizes, speed, .ost compression • Etc.

  4. Lync 2013 • Full IPv6 support • VDI plugin, allowingfull A/V support in virtualdesktopenvironments • H.264 SVC codecsupport • Skype federationsupport (coming) • Hybrid deployments of on-premises and Lync Online cloud servers now supported (this capability is called "hybrid voice")

  5. Lync 2013 • New role Office WebApps server • Consolidation of roles • Directorroleoptionalnot “recomended“ • A\V Conferencingalways on Front-End • Archiving and Monitoring on Front-End (optional) • Lync 2013 Std. alsoPersistent Chat on Front-End

  6. Lync 2013 • Persistent Chat – alternativefordistributionlists • Withthiscomesalsonew RBAC rolePersistent Chat Manager

  7. Lync 2013 • Enterprisevoicefeatures – inter-trunkroutingtoconnectan 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 • Hybridvoicewith Lync Online

  8. Lync 2013 • Disaster recovery and high-availability improvements • Reduntantrolesforcommon pool (sameas in Lync 2010) • No moreMetropolitanSiteResilency • New - Lync Pool pairing (Ent. with Ent.; Std. withStd.) bothsites are active. Manualfailover, failback

  9. Lync 2013 • Lync WebAppchanges – Audio/Video overbrowser, no moreAttendee • New Mobilityclient– notjetrelased and no dates. Willbesupporting audio and video callsovermobiledata, wi-fi

  10. Lync 2013 • Coexistence and Migration • Supported are Microsoft Lync Server 2010Microsoft Office Communications Server 2007 R2 • MigrationtodiffrentForestnotsupported • Public SSL, IP-s etc.

  11. Exchange 2013 • New Architecture! From Exchange 2010 5 server rolesto 2 roles in Exchange 2013. Client Access Server role and Mailbox Server role

  12. Exchange 2013 CAS • 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

  13. Client Protocol Architecture in Exchange 2013 Outlook Web App Outlook EAS EAC PowerShell SMTP POP/IMAP SIP Load Balancer Redirect SIP + RTP IIS POP, IMAP SMTP UM Client Access HTTP Proxy SMTP POP, IMAP HTTP IIS Transport UM POP IMAP RPS OWA, EAS, EWS, ECP, OAB RpcProxy RPC CA Mailbox MDB MailQ

  14. 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

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

  16. SMTP Inbound/Outbound Mail Flow Inbound Mail Flow FET accepts initial SMTP conversation if source passes connection filtering Applies protocol, sender, and recipient filtering based on message envelope up to the SMTP data command Proxies the message to the appropriate destination Outbound Mail Flow 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 MBX 2013 connects to FET and initiates SMTP conversation FET proxies outbound connection to appropriate destination 16

  17. 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

  18. 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

  19. E2010 vs. E2013 Performance Comparison 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 * 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)

  20. IOPS Reductions ~99.5% Reduction!

  21. 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 2013

  22. 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 Public logon Public logon Private logon CAS2013 Hierarchy Mailbox Content Mailbox MBX 2013 MBX 2013 MBX 2013

  23. 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 4 1 2 3 5

  24. New Search Foundation Primer Incoming Documents Incoming Queries Results CTS IMS Filter Word Break Content XForm Content XForm Query Parse “CTS Flow” “IMS Flow” MARS Writer Core Uses Search Foundation Catalog Significantly improved indexing performance Significantly improved query performance

  25. Service Availability Improvements 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 25

  26. Exchange 2013 HA DAG Multipledatabasespervolume Laggedcopyautomaticlogplaydown w. Safty Net DAG Network autoconfig CAS and MBX recoveryindependent Transport HA - Every message is redundantly persisted before its receipt is acknowledged to the sender Etc. 26

  27. 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

  28. Upgrading to Exchange 2013From an existing Exchange 2007 environment • 1. Prepare • Install Exchange 2007 SP3 + RU across the ORG • Prepare AD with Exchange 2013 schema and validate 4 6 5 2 3 7 1 Clients autodiscover.contoso.com mail.contoso.com legacy.contoso.com • 2. Deploy Exchange 2013 servers • Install both Exchange 2013 MBX and CAS servers E2013 CAS 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 Exchange 2007 Servers E2007 SP3 CAS E2007 SP3 HUB RU RU E2013MBX RU RU Intranet site • 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 E2007 SP3 MBX Internet-facing site – upgrade first 7. Repeat for additional sites

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

  30. 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 finalizedOnce migration completes, everyone switches at the same time • Can switch back, but any post migration Public Folder changes are lost

  31. Exchange 2013 • Archiving • eDiscovery • Integrationwith ohter MS 2013 products • Hybrid • Data Loss Prevention (DLP – identify, monitor, protect) • OWA – TouchMode, Offline • Etc.

  32. Questions/Küsimused?

  33. Tänan! Priit Timpson Atea Eesti SystemsEngineer

More Related