Office Web App Server give your organization the ability to use Word, Excel, PowerPoint and OneNote in your favorite web browser or web based application. Office Web App Server (WAC server) have single or multiple farms deployment scenarios. You can deploy your farm in your internal or DMZ networks. In my scenario I will deploy WAC server farm in my internal network and publish it through Reverse Poxy (TMG).
1. I prefer the newest versions of products and will deploy my WAC server on WIN2K12.
Open PowerShell and paste this code:
2. Download WAC server from HERE
Install product by NEXT NEXT NEXT …
3. Download languages pack for your country if needed from HERE
Install LP by running .exe file.
The Deployment steps finished. Lets start configuration steps.
All of the configuration of WAC server based on PowerShell commands.
We will create multiple servers HTTPS farm. All other types of configurations can be found HERE
1. After installation of WAC server open PowerShell as an administrator and paste the following command:
New-OfficeWebAppsFarm -InternalUrl "https://server.contoso.com" - ExternalUrl "https://wacweb01.contoso.com" -SSLOffloaded –EditingEnabled
This command will create new WAC farm with the internal and external URLs. SSLOFLOAD – for offloading SSL. In our case it’s required because we will use HLB for our farm. This will give our servers the ability to communicate with HLB by using HTTP.
EditingEnabled – it’s the ability given to Sharepoint for editing documents on a web-browser.
2. To add secondary server to the farm install WAC server on a secondary server with language packs and after all tasks finished open PowerShell and paste the following command:
New-OfficeWebAppsMachine –MachineToJoin "server1.contoso.com"
This command will add this machine to the farm created on previous steps. "server1.contoso.com" is the name of the first server.
3. Since we are using HTTPS farm we must have the correct certificate for our FARM. Exact requirements for PKI can be found HERE. How to obtain certificate from CA can be found HERE
The SAN of the certificate must contain internal and external URLs of the farm. Private key must be exportable as we will use this certificate on a multiple servers in the farm. After the certificate issued and installed open PowerShell as an administrator and type the following command: Set-OfficeWebAppsFarm –CertificateName “Friendly name of your certificate”.
4. 4. To verify your installation open internal URL of your WAC server farm on any web browser. The URL syntax is https://server.contoso.com/hosting/discovery . You will get something like this :
For load balancing between the servers you can you use Windows NLB which is not recommended for production environment. For production systems you can use any HLB and also free HLB based on Zen Load Balancer. The initial configuration of Zen HLB is pretty simple. You can mix any other Lync services traffic on the same instance of Zen HLB including WAC server farm. For load balancing WAC server on HLB first of all ad new vNIC. Then create new web farm, enter IP address of the farm, port and name. On your DNS servers (internal and external) create A record pointing to the VIP address of the HLB for internal and the Public IP address for the external zones. The full instruction can be found HERE.
Deployment and Configuration of the WAC farm is finished. Now let’s begin associate our Lync topology with the Office Web App Server Farm.
1. Open Topology Builder and download your initial configuration.
2. Open properties of your FE pool and click Associate Office Web App Server.
3. Create New and provide FQDN of your WAC farm and click OK.
4. Publish your topology.
5. Publishing instruction for WAC server on your Reverse Proxy (TMG) can be found HERE.