Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article was written by Tom Schauer, Technical Specialist.
You can rebuild Microsoft Office Web Apps server farm with a few easy steps. To do this, follow these steps:
Note
- Because there is a minimal configuration from an Office Web Apps perspective and zero data loss, there is little risk to rebuild an Office Web Apps farm.
- These steps can be used for fixing technical issues with Office Web Apps.
Take the Microsoft Office Web Apps server farm offline if there is a load balancer.
Collect the current farm information through PowerShell by using the following command on a Microsoft Office Web Apps (WAC) Server(s):
Get-OfficeWebAppsFarm > c:\MyWACfarm.txt
Note
Save this output because you will need it for later steps.
For a multi-server farm, remove each child machine from the farm, and then remove the parent machine by using PowerShell on WAC Servers.
Remove-OfficeWebAppsMachine
To find which server is the Parent and which servers are the Child, review the farm output from step 2 and look toward at the bottom for "Machines" listed. The first server is your Parent server and the rest are Child servers. Run the following command on the Child servers first, and as soon as it is completed, run the command on the Parent server. This will delete the farm.
Reboot the Office Web Apps Servers.
Re-create the farm through PowerShell on WAC servers by using the parameter values from the command that we ran in step 2.
New-OfficeWebAppsFarm -InternalURL "http://WACServer.corp.contoso.com" -AllowHttp -EditingEnabled -OpenFromURLEnabled
Reunite the Child servers with the Parent server through PowerShell on the WAC server. To do this, run the following command on each Child server:
New-OfficeWebAppsMachine -MachineToJoin *ParentServer*
Put the farm back online if there is a load balancer.
If you want to rebuild the bindings, run the following commands on SharePoint Servers through SharePoint PowerShell:
Remove-SPWOPIBinding –All:$true New-SPWOPIBinding –ServerName "WACServer.corp.contoso.com" -AllowHttp
To verify that your Microsoft Office Web Apps server farm was configured correctly, go to https://servername/hosting/discovery in a web browser.
If Office Web Apps server is working as expected, you should see a Web Application Open Platform Interface Protocol (WOPI)-discovery XML file in your web browser.
For example:
<?xml version="1.0" encoding="utf-8" ?>
- <wopi-discovery>
- <net-zone name="internal-http">
- <app name="Excel" favIconUrl="http://servername/x/_layouts/images/FavIcon_Excel.ico" checkLicense="true">
Note
You need to replace WACServer.corp.contoso.com in previous steps with the correct information from your farm.
For more information about how to configure Microsoft Office Web Apps, see Configure Office Online Server for SharePoint Server.