Office Web Apps Server supports two primary installation scenarios: a single-server Office Web Apps Server farm, and a multi-server, load-balanced Office Web Apps Server farm. You can use physical servers or virtual machine instances to run Office Web Apps Server, but you can’t install other server applications, such as SharePoint 2013 or SQL Server, on those servers. In environments that contain actual user data.
Supported Operating Systems for Office Web App server 2013
You can run Office Web AppServer on the following operating systems
- The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter with KB2592525 installed
- The 64-bit edition of Windows Server 2012 Standard or Datacenter
server roles, and features that are required for Office Web Apps Server
|Download, Server Role, or Feature||Windows Server 2008 R2||Windows Server 2012|
|Download: Office Web Apps Server||Microsoft Download Center||Microsoft Download Center|
|Download: .NET Framework 4.5||.NET Framework 4.5||Already installed|
|Download: KB2592525||KB2592525||Already installed|
|Download: Windows PowerShell 3.0||Windows PowerShell 3.0||Already installed|
|Server role: Web Server (IIS)||The following list describes the minimum role services that are required for the Web Server (IIS) server role.Common HTTP Features
The following options are recommended but not required:
|The following list describes the minimum role services that are required for the Web Server (IIS) server role.Management Tools
The following services are recommended but not required:
|Feature: Ink and Handwriting Services||Ink and Handwriting Services
||Ink and Handwriting Services
Hardware Requirement – Application Server
The requirements in the following table apply both to installations on a single server with a built-in database and to servers running Office Web App Server 2013 in a multiple server farm installation.
|Processor||Intel Xeon Processor E7 (16 core).|
|Hard disk||500 GBYou must have sufficient space for the base installation and sufficient space for diagnostics such
as logging, debugging, creating memory dumps, and so on. For production use, you also need
additional free disk space for day-to-day operations. Maintain twice as much free space as you
have RAM for production environments. For more information, see Capacity management and sizing for SharePoint Server 2013.
Prepare the servers
In this phase, you get your servers ready to host the product. This includes the supporting servers and
the servers that will have Office web app Server installed. The following servers must be configured to
support and host a farm:
- Domain Controller
- Application Server of Office web app
The following table describes the accounts that are used to install and configure Office WebApp Server 2013.
|domain-OfficeWebApp||This account would responsible to run Office webapp server and services||Logon locally in office web app server and administrative rights, Run Office web app server2013|
prepare a server that runs Windows Server 2012
- Open the Windows PowerShell prompt as an administrator and run the following command examples to install the required roles and services.
For Windows Server 2012
If you are prompted, restart the server when the command finishes.
Install Office Web Apps Server
Mount Office Web Apps 2013 Install on the OWA2013 server and run the Install
Office Web App Server CU Installation
Download and install the Office Web Apps Server 2013 update KB2810007.
Office Web App Server Configuration
Create OWA Farm and Configure to use HTTP and Support Editing
- Login on to OWA2013 Server with Office Web App Service Account
- From an elevated PowerShell command prompt run below command
Test by accessing from outside your server http://owa2013/hosting/discovery
Office Web App Server Binding and Configuration with SharePoint Server 2013
- Login to SP2013WFE with SpAdmin Account
- From an elevated SharePoint PowerShell command prompt run below command
Now you should see a long list application extension registration with the WOPIZone
To confirm type and test below command to verify that the new zone is internal-http
Change the AllowOAuthOverHttp setting in SharePoint 2013 to True. Run below command
That means we will need to allow SharePoint to allow OAuth over HTTP by running below commands
Now check one more time the status of OAuth over http
Now once again check the WOPI Zone and as you can see it is still se to internal-https
For this installation test since I had used internal and http, I am going to set the WOPI Zone accordingly as below.
Test Office Web Apps with SP 2013
Browse to SharePoint site as user and not as system account (OWA does not work for system account)
Thanks Happy SharePointing 😉