Speaker: Wictor Wilén;
From SharePoint 2013 is Office Web Apps no longer an add-on to SharePoint, it is now its own server product – Office Web Apps Server. This new change gives Office Web Apps numerous advantages over the previous add-on model. For instance Office Web Apps can now be updated independently from SharePoint and we can dedicate specific Office Web Apps farms, which can be shared between multiple SharePoint farms, and even Exchange and Lync. In this session we will walk through all you need to know about Office Web Apps Server 2013; from installation, to configuration and how to update it. We will also take a closer look on how to connect the Office Web Apps Server to SharePoint and how it improves the user experience in SharePoint when reading, editing and searching for documents.
8. Office Web Apps 2010
Service Application
Upgraded together with SharePoint 2010
Totally different update schedules
Somewhat “strange” licensing
Docs.com
Skydrive
Facebook
10. What is WAC Server?
Office Web Apps Server 2013
Brand new server product
Fault tolerant and scalable
Independent of SharePoint
Can be shared with SharePoint, Exchange and Lync
Based on a new protocol – WOPI
11. New stuff in WAC 2013
Independent of SharePoint
Better browser/mobile support
Better preview, embedding and co-authoring support
Licensing
• Read post by Spence Harbar: http://askwictor.com/WACEdit
Can show files from UNC paths
Based on the open WOPI protocol
12. How WAC work
Host Frame
SharePoint
App Frame
Exchange Office Web Apps
Lync
13. Hardware and OS Requirements
Hardware
• Same as SharePoint 2013
Virtualization fully supported
Operating systems
• Windows Server 2008 R2 x64
• KB2592525
• Windows Server 2012
.NET Framework 4.5
PowerShell 3.0
Must be joined to a domain
• Preferably the same domain as the SharePoint Servers
• Must be the same forest
14. Server Requirements
Do not run any other server application on the WAC Server
• Exchange, SharePoint, Lync, SQL,…
• Hard block!
Do not run any services that blocks port 80, 443 or 809/810
Office must not be installed
Should not be a domain controller
19. New-OfficeWebAppsFarm
Create and configure the WAC Farm
Internal and external URLs
Configure HTTPS and certificate
• Or HTTP (not recommended) – only use with IPSEC
Cache and logs
Use the –Verbose switch!
Active Directory OU!
21. New-SPWOPIBinding
Connects SharePoint to the WAC Farm
Use FQDN
Adds “WOPI Bindings” to SharePoint
Only server name -> All bindings
You can bind to only Extension, FileName, ProgID etc if needed
If SharePoint uses HTTP configure AllowOAuthOverHTTP
• (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp
22. Connecting it to Lync and Exchange
Exchange 2013
• Set-OrganizationalConfig
–WACDiscoveryEndPoint http://wac/hosting/discovery
Lync 2013
• Use the Lync Server Topology Builder
24. New-OfficeWebAppsMachine
Adds more servers to the WAC Farm
Specify one already existing server in the WAC farm
Roles
• FrontEnd
• WordBackEnd
• ExcelBackEnd
• PowerPointBackEnd
Master Machine
• There can be only one!
26. *-OfficeWebAppsHost
Manage which hostnames that can call the WAC farm
Default: all!
* Is implicit, so sub-domains are allowed
DO NOT FORGET this on Internet facing sites!
27. *-SPWOPISuppressionSetting
Turns of a specific WOPI commands
• -Action
• -ProgID
• -Extension
Example:
• New-SPWOPISuppressionSetting –Action “edit” –Extension “pptx”
30. Update WAC
Is done independently of SharePoint, Exchange or Lync
Create a new WAC farm
Disconnect old WAC farm from SharePoint
Connect new WAC farm to SharePoint
Disconnect and move one server at a time to the new farm
31. Troubleshooting
ULS!
• On the SharePoint farm
• And the WAC farmen
Fiddler is your friend
• As usual…
Repair-OfficeWebAppsFarm
• Removes all Unhealthy servers
Read the WOPI protocol specs
32. [MS-WOPI]
Web Application Open Platform Interface
Open (documented) protocol
Can create own WOPI Hosts/Servers (SharePoint) and connect to own WOPI
Apps/Clients (WAC)
http://askwictor.com/WOPI