Posted on December 21, 2014 · Posted in Misc

Installing Office Web Apps on SharePoint 2013

With the release of SharePoint 2013 has changed the concept of Office Web Apps, is now a separate farm (or single server) that can be used also as Exchange or Lync servers. Suppose that SharePoint 2013 is installed and we need to configure the server for Office Web Apps.

Let’s install the necessary components:

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

Now download and install the Office Web Apps (available for download only under Volume Licensing agreement ).

After server rebooting, open PowerShell and register our server (we use http):

Import-Module OfficeWebApps
New-OfficeWebAppsFarm -InternalURL "" -AllowHttp -EditingEnabled


Now check the operability follow the link

Now proceed to configuring the SharePoint server. Start SharePoint Management Shell from sp_farm account (Share Point server farm account) and execute:

New-SPWOPIBinding -ServerName -AllowHTTP

To make sure that we use http:


To force http usage:

Set-SPWOPIZone –zone “internal-https”

We should get:


Check that the command AllowOAuthOverHttp returns:


If the returned value is False, then switch to True :

$config = (Get-SPSecurityTokenServiceConfig)

$config.AllowOAuthOverHttp = $true



It’s time to check the functioning of the Office Web Apps. We will create a new Team Site, named docs

It is well-known that the system account Administrator has a problem with Office Web Apps. Let’s create two users(user1 and user2). Then include the Domain Users group to the docs site owners.

Now we can log on with these users and make sure that everything is working properly.

Office Web Apps docs

We have described the basic setup, let’s get to work options using SSL. Create  a new server for WebApps, call it wa and install Office Web Apps package again.

Obtain such certificate: WA certificate

Restart server, open Powershell amd register our servers (with https):

Import-Module OfficeWebApps

New-OfficeWebAppsFarm -InternalUrl “” -ExternalUrl “” –CertificateName “WebApps SAN Cert” -EditingEnabled

Add A record to DNS zone for converting to IP address.

Now check the operability of link


Run SharePoint Management Shell from sp_farm account and execute:

New-SPWOPIBinding -ServerName

To make sure that we use https


If our service is only available within the internal network:

Set-SPWOPIZone –zone “internal-https”

If also available outside:

Set-SPWOPIZone –zone “external-https”

SPWOPIZoneRemains attached SSL certificate to the IIS site and test the Office Web Apps.

Related Articles