.png)
|
Start here |
You want to deploy SharePoint 2013, Lync Server 2013, Exchange Server 2013 or you have a custom solution and you want to know how get Office Web Apps. Let us introduce you to Office Web Apps Server. Office Web Apps Server is an Office server product that provides browser-based file viewing and editing services for Office files. Office Web Apps Server works with products and services that support WOPI, the Web app Open Platform Interface protocol. These products, known as hosts, include SharePoint 2013, Lync Server 2013, and Exchange Server 2013. You can see a high-level overview of what Office Web Apps Server is and how it works in the Office Web Apps Server poster.
Office Web Apps Server Poster
Office Web Apps Server also enables users to view Office files in shared folders and websites by using Online Viewers.
If you have some Excel expert users and business intelligence solutions in your organization, learn about the differences between Excel Web App and Excel Services to decide which you should enable.
Office Web Apps can be used on many devices such as such as Windows Phones, iPhones, iPads, Windows 8 tablets, and Android devices.
If you have SharePoint 2013 configured to use Office Web Apps Server, users can co-author documents in Word, PowerPoint, Excel, and OneNote Web Apps.
If you want to see how to deploy Office Web Apps Server to use with SharePoint 2013, watch the Video: Configure Office Web Apps for SharePoint 2013. |
.png) |
Plan Office Web Apps Server |
Before you deploy Office Web Apps Server, make sure that you plan your Office Web Apps Server deployment.
Software requirements
Hardware, topology, and network planning
Microsoft IT has deployed Office Web Apps Server by using a topology that can support 200,000 users. By following the topology guidelines, based on our performance tests, an Office Web Apps Server, with two Intel Xeon processors (8 cores), 8 GB of RAM, and a 60 GB hard disk, should support up to 10,000 users where most of the usage is viewing. A server that has a 16 core CPU and 16 GB of RAM should support up to 20,000 users. These results will vary depending on usage patterns and other factors such as network hardware.
You can secure Office Web Apps Server communications by using HTTPS, by using SSL offloading for hardware load balancers, by restricting which servers can join an Office Web Apps Server farm based on OU membership, or by limiting host access for Office Web Apps Server by using the Allow List.
Office Web Apps Server requires its own server instance and can't be run with other services or applications, such as SharePoint 2013. If you are limited on hardware, you can virtualize Office Web Apps Server.
We recommend a load balancing solution when you run Office Web Apps Server on two or more servers. If you use a load balancer, you have to install the certificate on the load balancer. Certificates that are used by Office Web Apps Server have to meet these requirements.
Review the firewall requirements for Office Web Apps Server to help prevent problems caused by firewalls that are blocking communication between the web browser, the servers that run Office Web Apps Server, and the servers that run SharePoint 2013.
Planning for software updates
Planning for SharePoint
Planning for other hosts
|
|
Migrating from Office Web Apps in SharePoint 2010 |
Are you currently using SharePoint 2010 Products and plan to migrate to SharePoint 2013? Unfortunately, SharePoint 2010 Products can't be a host for Office Web Apps Server, and Office Web Apps won’t be available after you upgrade to SharePoint 2013. Be sure to read about SharePoint authentication requirements. If you used classic mode authentication in SharePoint 2010, you’ll have to migrate from classic mode to claims-based authentication.
One of the biggest changes is that you do not install Office Web Apps on the same servers that run SharePoint 2013. What else is new in Office Web Apps when it is used with SharePoint 2013 Products? |
|
Custom WOPI solutions |
If you have a custom solution and want to use that custom solution as a host for Office Web Apps, learn how to create a custom WOPI host.
|
.png) |
Deploy Office Web Apps Server |
The first step is to prepare servers to run Office Web Apps Server. Next install Office Web Apps Server and apply the latest Office Web Apps Server update. Then install language packs for Office Web Apps Server.
To evaluate how Office Web Apps Server works, you can deploy a single-server Office Web Apps Server farm in a test environment. Or, to deploy something more secure, you can deploy a single-server Office Web Apps Server farm that uses HTTPS. If you have to support lots of users, you can deploy a multi-server, load-balanced Office Web Apps Server farm that uses HTTPS.
After you've deployed Office Web Apps Server, you have to configure the host. You can configure SharePoint 2013, configure Exchange Server 2013 and configure Lync Server 2013 to use Office Web Apps Server.
If you want to see what's involved in deploying Office Web Apps Server to use with SharePoint 2013, watch the Video: Configure Office Web Apps for SharePoint 2013. |
.png) |
Use Office Web Apps |
To help your users get started, check out these resources:
|
.png) |
Manage Office Web Apps Server |
Plan and establish an update process for the Office Web Apps Server farm. Office Web Apps Server updates must be applied in a specific way.
You can find a list of the most recent Office Web Apps Server updates on the Microsoft Office Updates blog and on the TechNet Update center for Office, Office servers, and related products.
If you've deployed Office Web Apps Server to use with SharePoint 2013, the default open of Office documents will be in the browser. But, you can change this behavior so that Office documents open in a client.
If your organization decides to use Excel Services instead of Excel Web App to view workbooks in the browser, you can use the Windows PowerShell cmdlet New-SPWOPISuppressionSetting to turn off Excel Web App for Excel workbooks.
If you want to disconnect SharePoint 2013 from Office Web Apps Server, use the Windows PowerShell cmdlet Remove-SPWOPIBinding. |
.png) |
Troubleshoot Office Web Apps Server |
Troubleshoot errors in Office Web Apps when it is used with SharePoint 2013 |
.png) |
Reference information |
Here are links to Windows PowerShell commands and other types of reference information:
Office Web Apps Server
SharePoint 2013
|
.png) |
Downloads |
Here are the downloads that are related to Office Web Apps Server:
|
.png) |
Videos |
|
.png)
|
Ask questions and provide feedback |
If you have questions about how to deploy and manage Office Web Apps Server, you can submit your questions in the Office 2013 and Office 365 ProPlus - Planning, Deployment, and Compatibility forum on TechNet. |