Office Online Server brings the advantage of rich content viewing and editing to Outlook on the web clients for on-premises environments. This session shows how simple it is to deploy OOS in combination with Exchange Server 2016.

1. Michel de Rooij
April 26th, 2016
BE-COM E-COMMUNICATIONS EVENT:
EXCHANGE 2016 & OFFICE ONLINE SERVER

2. • Michel de Rooij
• Consultant @ Conclusion FIT (NL)
• Office Server and Services MVP
(formerly Exchange MVP, 3y)
http://bit.ly/ProEx2013SP1
• michel@eightwone.com
• Blog: eightwone.com
• Twitter: @mderooij

3. • OOS
• Architecture
• Deployment
• Configuring
• Demo
AGENDA

4. • 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
OOS: OFFICE ONLINE SERVER

5. OOTW WITHOUT/WITH OOS

6. • 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
TOPOLOGY
oos.us.contoso.com oos.emea.contoso.com
oos.contoso.com

7. 1. OWA user clicks ‘View’
2. Exchange retrieves discovery info
for file type
3. OOS returns discovery info
with unique URL
4. Exchange creates <iframe>, loading
unique URL
5. Client uses unique URL (with token)
6. Exchange transfers contents to OOS
7. OOS renders contents
HOW IT WORKS ..
https://meet.myexchangelabs.com/wv/wordviewerframe.aspx?ui=en-
US&rs=en-
US&WOPISrc=https%3A%2F%2Fmail.myexchangelabs.com%3A443%2
Fowa%2Fe08e45e6-03a0-45c7-9722-
e7f70040fb8f%2540myexchangelabs.com%2Fwopi%2Ffiles%2F%40%2
Fowaatt%3Fowaatt%3DLVMtMS01LTIxLTIxMDAxODI1MDEtMTkyNDYw
ODEwOS00NDk4MzU0OTUtMTEzM7Gj9p2xbNMIAQEBAAA%253d&hh
=1 HTTP/1.1
3
2
6
Exchange 2016 Office Online Server
2016
OWA Client

8. • Requirements
• Install Office Online Server & Language Packs
• Configure Namespace
• Create & Configure OOS Farm
• (Re)configuring Exchange
DEPLOYMENT

9. • 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

10. • 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
REQUIREMENTS (2)

11. INSTALL Should be fixed in GA

12. • Certificate
• OOS Discovery Endpoint
• OOS Farm(s) External & Internal URLs
• SAN or wildcard
• DNS
• Reachable for Clients & Exchange
• Can point to Load Balancer VIP
CERTIFICATE & NAMESPACE

13. • No GUI
• PowerShell-only
MANAGING OOS

14. • 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 –ExternalURL
https://oos.apac.contoso.com
• Remove-OfficeWebAppsMachine
• Removes local machine from farm
CONFIGURE FARM
-EditingEnabled:$true

15. • OU-bound
• Set-OfficeWebAppsFarm –FarmOU
ou=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
RESTRICTING FARM

16. • 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-WebAppPool MSExchangeOWAAppPool
• Both set?
• Org-level used as fall-back
CONFIGURING DISCOVERY ENDPOINT

17. DISCOVERY ENDPOINT

18. • 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
CO-EXISTENCE
oosfarm.contoso.com
wac.contoso.com
(org-level)
OOS Servers WAC Servers

19. • Enable/Disabling or Forcing (default enabled)
• Exchange level:
• Set-OWAVirtualDirectory –Identity ex1*
• Mailbox level:
• Set-OWAMailboxPolicy –Identity user1 ..
• WacViewingOnPublicComputersEnabled
WacViewingOnPrivateComputersEnabled
• ForceWacViewingFirstOnPublicComputersEnabled
ForceWacViewingFirstOnPrivateComputersEnabled
EXCHANGE & OOS

20. DEMO

21. DEMO - CREATING AN OOS FARM

22. • 2 Web Sites:
• 1 on port 80/443 (clients)
• 1 on 809 (farm)
DEMO – IIS WEB SITES

23. • (Get-OfficeWebAppsFarm).LogLocation
DEMO – LOGGING/ TROUBLESHOOTING

24. • Note: Edit will create new Draft message with copy of the attachment
DEMO – OOS IN ACTION

25. • https://technet.microsoft.com/en-us/library/jj219456(v=office.16).aspx
LINKS

26. Q&A