Guide to rebuild your Office Web Apps 2013 Farm

Follow the steps under to rebuild your Office Web Apps 2013 farm in case you need it.

Step 1:  Take farm offline (only if there is a load balancer in use)

Step 2: Collect the current Farm information via Powershell (This you have to do on the WAC Server): 

Get-OfficeWebAppsFarm > c:\MyOWAfarm.txt

41

Step 3: Use Powershell (on the WAC Servers) to remove each child machine

Remove-OfficeWebAppsMachine (On each child machine)

This step you only have to go through if you have a multi server farm in your Office Web Apps farm

Step 4: Use Powershell (on the WAC servers) to remove the parent machine

Run the following command in Powershell to delete the farm:

Remove-OfficeWebAppsMachine

42

Then Restart the OWA servers.

Step 5: Recreate the farm via Powershell (on the WAC Server)

If you want you could use the parameter values from “MyOWAfarm.txt”.AppsMachine

New-OfficeWebAppsFarm -InternalURL “http://karm-OWA.sharepoint.com” -AllowHttp -EditingEnabled -OpenFromURLEnabled

Replace http://OWA.sharepoint.com with the value for your OWA server.

 

 

43

Step 6: Add all the other servers to the OWA-farm via Powershell (on WAC Server).  Run this from each child server: 

 

New-OfficeWebAppsMachine -MachineToJoin <ParentServer>

Replace the value of <ParentServer> with your name of your ParentServer

Step 7: Bring farm back online.

You may want to rebuild the bindings via SharePoint Powershell (this you have to run on the SharePoint 2013 Server)

Disconnect SharePoint from the OWA farm:

Remove-SPWOPIBinding –All:$true 

44

Reconnect SharePoint to the OWA farm:


New-SPWOPIBinding –ServerName “KARM-OWA” -AllowHttp

45

 

Congratulations you have successfully recreated your Office Web Apps Farm.

 

Useful Resource:

Guide on how to Install and configure Office Web Apps farm

Configure Office Web Apps for SharePoint 2013

http://technet.microsoft.com/en-us/library/ff431687

Guide on how to install and configure Office Web Apps 2013 server, and connect it to SharePoint 2013

Follow this guide to install Office Web Apps 2013 on a Windows server, and connect it to your SharePoint farm

Step 1  Prepare the server for Office web Apps:

Open powershell cmndlet as an administrator and copy/paste and run the following code to enable all the features required for Office Web Apps

On Windows 2008 R2

First run this command
Import-Module ServerManager
And then this one:

Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-Security,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Console,Ink-Handwriting,IH-Ink-Support,NET-Framework,NET-Framework-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-Win-CFAC

On Windows 2012 R2

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

Step 2:  Install “Office Web Apps Server”

Download Office web apps server from Microsofts pages:

http://www.microsoft.com/en-us/download/details.aspx?id=35489

Click on the downloaded file “wacserver.img” and run the setup.exe file.

1

Choose “I accept the terms of this agreement” and click continue

2

Change the file location to the file location you want, and click “Install Now” Wait until the installation is finished

3

Click close to finish the installation of Office Web Apps Server

Now your Office Web Apps Server is installed and it’s ready to apply language packs.

Step 3:  Install language packs to “Office Web Apps Server”

Download the language pack of your requirements from Microsoft:

http://www.microsoft.com/en-us/download/details.aspx?id=35490

And then install them by clicking on the file you just downloaded  Click I accept the terms of this agreement and then click Continue to install the language pack for your selected language. 7

Click close to finish the installation of the selected language pack.

 

Step 4:  Install updates to “Office Web Apps Server”

Next step now is to make sure that you have the latest version of office web apps installed.

Download the latest update: (Currently it’s service pack 1, KB2880558)

http://www.microsoft.com/downloads/details.aspx?FamilyId=21a642af-3961-4578-ad8c-b7365078c961

Click and run on the downloaded file “wacserversp2013-kb2880558-fullfile-x64-glb.exe”

22

Approve the license terms, and click continue.

23

Wait while the service pack gets installed

24

Click “OK” to finalize the installation of the Service Pack.

Step 5: Open ports

The following firewalls need to be open:

  • Port 443 for HTTPS traffic
  • Port 80 for HTTP traffic
  • Port 809 for private traffic between the servers who runs Office web Apps ( Note this is only necessary if you run more then 1 Office WebApps server)

Run the following in command prompt as an administrator where you replace <port> with the port you want to open:

netsh advfirewall firewall add rule name=Open Port <port> dir=in action=allow protocol=TCP localport=<port> 

For instance:

netsh advfirewall firewall add rule name=Open Port 80 dir=in action=allow protocol=TCP localport=80

To open port 80.

Step 6: Create SharePoint Office Web Apps server farm – HTTP

If you want to create the Office Web Apps server farm over HTTP follow this guide, usually you will only use HTTP in a dev environment.

To set up the Office Web Apps Server farm with HTTPS move to step 7.

Open powershell commandlet as a administrator and run the following command:

new-OfficeWebAppsFarm -InternalUrl “http://<servername>” -externalurl “http://<servername>” -AllowHttp -EditingEnabled “

for instance:

new-OfficeWebAppsFarm -InternalUrl “http://karm-owa” -externalurl “http://karm-owa.sharepoint.com” -AllowHttp -EditingEnabled

-EditingEnabled opens up so that the users can edit the documents inside Office Web Apps.

25

Choose yes (y) when asked question “Continue with this operation”

Next open CMD as an administrator and run it:

dism /online /enable-feature /featurename:IIS-ASPNET45

35

Open Internet Explorer and try to open up

http://<servername>/hosting/discovery

For example “http://karm-owa/hosting/discovery

26

Step 7: Create SharePoint Office Web Apps server farm – HTTPS

First you need to have created the SSL sertificate.

Open powershell commandlet as a administrator and run the following command:

new-OfficeWebAppsFarm -InternalUrl “https://<servername>” -externalurl “http://<servername>” CertificateName “OfficeWebApps Certificate” -AllowHttp -EditingEnabled “

for instance:

new-OfficeWebAppsFarm -InternalUrl “https://karm-owa” -externalurl “https://karm-owa.sharepoint.com” CertificateName “OfficeWebApps Certificate”  -EditingEnabled

-EditingEnabled opens up so that the users can edit the documents inside Office Web Apps. This requires the users to have license to open up the Office documents.

34

33

Choose yes (y) when asked question “Continue with this operation”

Next open CMD as an administrator and run it:

dism /online /enable-feature /featurename:IIS-ASPNET45

35

Open Internet Explorer and try to open up

https://<servername>/hosting/discovery

For example “https://karm-owa/hosting/discovery

26

 

So you can see that the setup for HTTPS and HTTP is pretty much the same.

Step 8: Connect SharePoint 2013 server to Office Web App server – http

 

Open powershell commandlet on the SharePoint 2013 Server and run the following code:

New-SPWOPIBinding -ServerName <servername> -AllowHTTP

For Example:

New-SPWOPIBinding -ServerName karm-owa -AllowHTTP

Step 9: Check if you have the correct WOPI Settings

Open Powershell cmdlet on the Sharepoint Server 2013 and run the following code:

Get-spwopiZone

38

 

This shows internal-https which is not correct if you shouldn’t have https or if the zone should be external.

For internal-http: run the following command to change this to correct settings in powershell:

Set-SPWOPIZone –zone “internal-http”

For external-http:

Set-SPWOPIZone –zone “external-http”

For external-https:

Set-SPWOPIZone –zone “external-https”

In my example I shall use internal http so i run this code: Set-SPWOPIZone –zone “internal-http”

39

To check that the settings is now correct i re-run the Get-SPwopiZone

Which now as you can see returns internal-http

The last thing you need to do now is to allow traffic over http, this you only have to do if you should use http. If you use https you can skip this step.

 

Step 9: Allow traffic over http

Run the following command in powershell to check if the environment already approves traffic over http

(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

40

If this returns false then running this code to allow:

$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$config.Update()

Then run the following code again to check if it’s correct:

(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

19

If it’s return true then it’s correct and you are finished setting up the connection between the Office Web Apps farm and SharePoint 2013.

Congratulations!

If you have some problems or need help with setting this up, don’t hesitate to contact me

Best regards

 

Knut

Email: knutrelbemoe(at)outlook.com

Twitter: sharePTkarm

Skype: sharePTkarm

Mobile: 0047-98224609

References:

http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx – Set up Office Web Apps

http://support.microsoft.com/kb/947709/en-us  – How to use netsh advfirewall firewall

netsh advfirewall firewall