260 likes | 365 Views
BE-COM e-communications event: Exchange 2016 & Office Online Server. Michel de Rooij April 26 th , 2016. Michel de Rooij Consultant @ Conclusion FIT (NL) Office Server and Services MVP (formerly Exchange MVP, 3y). michel@eightwone.com Blog: eightwone.com Twitter: @ mderooij.
E N D
BE-COM e-communications event:Exchange 2016 & Office Online Server Michel de RooijApril 26th, 2016
Michel de Rooij • Consultant @ Conclusion FIT (NL) • Office Server and Services MVP (formerly Exchange MVP, 3y) • michel@eightwone.com • Blog: eightwone.com • Twitter: @mderooij http://bit.ly/ProEx2013SP1
AGEnda • OOS • Architecture • Deployment • Configuring • Demo
OOS: Office Online server • Browser-based Office • Word, Excel, PowerPoint, and OneNote • Rich Document Viewing or Editing • Integrates w/Exchange 2016, SharePoint 2016 and Skype for Business • Not new, but many TLA changes .. • OWA, OWC, WAC .. • Available through Volume Licensing Service Center only • Technical Preview was Public • GA not available yet
Topology • Single or Multiple OOS servers? • Farm • Load Balancer • Client affinity • Single or Multiple Locations • Discovery Endpoint • ‘Autodiscover’ for OOS • Exchange Org-level and Server-level
How it works .. https://meet.myexchangelabs.com/wv/wordviewerframe.aspx?ui=en-US&rs=en-US&WOPISrc=https%3A%2F%2Fmail.myexchangelabs.com%3A443%2Fowa%2Fe08e45e6-03a0-45c7-9722-e7f70040fb8f%2540myexchangelabs.com%2Fwopi%2Ffiles%2F%40%2Fowaatt%3Fowaatt%3DLVMtMS01LTIxLTIxMDAxODI1MDEtMTkyNDYwODEwOS00NDk4MzU0OTUtMTEzM7Gj9p2xbNMIAQEBAAA%253d&hh=1 HTTP/1.1 OWA user clicks ‘View’ Exchange retrieves discovery infofor file type OOS returns discovery info with unique URL Exchange creates <iframe>, loadingunique URL Client uses unique URL (with token) Exchange transfers contents to OOS OOS renders contents
DeploymenT Requirements Install Office Online Server & Language Packs Configure Namespace Create & Configure OOS Farm (Re)configuring Exchange
RequirementS • Dimensioning • ~10k users/server (concurrent, viewing) • 8 GB / 8 Xeon cores • 60 GB storage • Don’t collocate with other roles • Not on Domain Controllers, Exchange servers, .. • Network • OOS accessible on 80/tcp and 443/tcp • Intra-farm 809/tcp • Virtualization & SSL Offloading supported
Requirements (2) • Windows Server 2012 R2 • Windows Features • Add-WindowsFeature Web-Server, Web-Mgmt-Tools, Web-Mgmt-Console, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Static-Content,Web-Performance, Web-Stat-Compression, Web-Dyn-Compression, Web-Security, Web-Filtering, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext45, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Includes, InkandHandwritingServices • Visual C++ Redistributable for Visual Studio 2015 • http://go.microsoft.com/fwlink/p/?LinkId=620071 • .NET Framework 4.5.2 • http://go.microsoft.com/fwlink/?LinkId=616890 • OOS
INSTALL Should be fixed in GA
Certificate & Namespace • Certificate • OOS Discovery Endpoint • OOS Farm(s) External & Internal URLs • SAN or wildcard • DNS • Reachable for Clients & Exchange • Can point to Load Balancer VIP
managing OOS No GUI PowerShell-only
-EditingEnabled:$true Configure Farm • New-OfficeWebAppsFarm –InternalURL https://oos.contoso.com –ExternalURL https://oos.emea.contoso.com –CertificateName 'Contoso Certificate' -EditingEnabled • Operates against local machine • Use certificate friendly name • New-OfficeWebAppsMachine–MachineToJoin oos1.consoto.com • Adds current OOS server to OOS farm running on oos1.contoso.com • Set-OfficeWebAppsFarm –ExternalURLhttps://oos.apac.contoso.com • Remove-OfficeWebAppsMachine • Removes local machine from farm
Restricting FARM • OU-bound • Set-OfficeWebAppsFarm –FarmOUou=OOSServers,ou=NL,dc=contoso,dc=com • Allow Interaction • New-OfficeWebAppsHost –domain 'contoso.com' • Specific Roles • Set-OfficeWebAppsMachine –Roles [All | FrontEnd | WordBackEnd | ExcelBackEnd | PowerPointBackEnd] • Only recommended large farms • More on OOS configuring • http://bit.ly/ConfOOS
Configuring Discovery Endpoint • Organization or Server-level • Set-OrganizationConfig –WACDiscoveryEndpoint https://oos.contoso.com/hosting/discovery • Set-MailboxServer –Identity Ex1 -WACDiscoveryEndpoint https://oos.contoso.com/hosting/discovery • Restart-WebAppPoolMSExchangeOWAAppPool • Both set? • Org-level used as fall-back
Co-existence • Exchange 2016 doesn’t support WAC • Exchange 2013 doesn’t support OOS • Exchange 2013 knows org-level only • Use Set-MailboxServer @ Ex2016 • Use multiple OOS with LB to prevent fall-back
Exchange & OOS • Enable/Disabling or Forcing (default enabled) • Exchange level: • Set-OWAVirtualDirectory –Identity ex1\* • Mailbox level: • Set-OWAMailboxPolicy –Identity user1 .. • WacViewingOnPublicComputersEnabledWacViewingOnPrivateComputersEnabled • ForceWacViewingFirstOnPublicComputersEnabledForceWacViewingFirstOnPrivateComputersEnabled
DEMO – IIS WEB SITES • 2 Web Sites: • 1 on port 80/443 (clients) • 1 on 809 (farm)
DEMO – LOGGING/ TROUBLESHOOTING (Get-OfficeWebAppsFarm).LogLocation
DEMO – OOS in action Note: Edit will create new Draft message with copy of the attachment
Links https://technet.microsoft.com/en-us/library/jj219456(v=office.16).aspx