Installing and configuring the Office Web Application (WAC) Server
Install Pre-Requisites
Run Powershell as Admin:
Enter the following command:
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
The server configuration will now run.
When prompted, restart the computer
Install Office Web Application Server
Run Setup
Accept the license agreement and click Continue
Select the installation directory and click Install Now
Configure Office Web Applications Server
Open PowerShell and run as admin
Run the following commands:
1. Import-Module OfficeWebApps
2. Get-Command “*Office*”
The first command imports the OWA cmdlets, and the second verifies they are available for your use.
Now, we can create the actual OWA server farm:
New-OfficeWebAppsFarm –InternalURL http://yourserver –AllowHttp -EditingEnabled
Let’s break down the New-OfficeWebAppsFarm parameter:
–InternalURL : Use the FQDN of the server to run OWA
-AllowHttp : This command tells OWA which protocol to use when communication occurs between the two entities. HTTP can also be used, but it is recommended that it is used for Dev purposes.
-EditingEnabled : Allows documents to be edited using OWA
To verify that the OWA farm was built correctly, run the following command in Internet Explorer or Edge:
http://yourserver/hosting/discovery
Log into your server, and run the following PowerShell command.
New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP
The –ServerName is the FQDN of the OWA farm server you just created. It should be the same as the –InternalURL you used earlier. Don’t use ‘Http://’ in the server name parameter, just the FQDN of the server.
By default OWA server farm wants to use HTTPS. You can force it to recognize HTTP with the following PowerShell OWA command:
Set-SPWopiZone –zone “internal-http”
Change the AllowOAuthOverHttp setting in SharePoint 2013 to True
To use Office Web Apps with SharePoint 2013 over HTTP in a test environment, set AllowOAuthOverHttp to True. Otherwise Office Web Apps will not work. You can change the current status by running the following example:
(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$config.Update()
Test whether the installation was successful:
(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp
You should receive the following output: