Jens Trier Rasmussen

The odd bit of information about Lync Server 2013, Lync 2010, Exchange 2013, SharePoint Server 2013, Exchange 2010 SP1, OCS 2007 R2, Exchange 2010 and OC 2007 R2

Creating an Office Web Apps Server 2013 farm with 2 machines

Creating an Office Web Apps Server 2013 farm with 2 machines

  • Comments 11
  • Likes

Office Web Apps Server 2013 provides the ability to create a farm with one or more machines in it. Recently I had to create a farm with two machines, and it took a little bit to get my head around how to do it. Here is how I ended up doing it

I had the following environment:

  • Two servers: wac1.contoso.dk and wac2.contoso.dk
  • The internal fqdn of the farm should be wac.contoso.dk and the external fqdn should be wacext.contoso.dk
  • Hardware load balancer configured for wac.contoso.dk

On wac1.contoso.dk

I did the following steps:

  • Installed Office Web Apps Server 2013 and the March 12, 2013 update.
  • Used the MMC certificate snap-in to create a certificate from my internal CA based on WebServer template with:
    • Subject name WacFarm
    • Friendly name WacFarm
    • Subject alternate names of wac1.contoso.dk, wac2.contoso.dk,wac.contoso.dk,wacext.contoso.dk, wac1 and wac2
    • Allow private key to be exported
  • After the certificate was loaded in the personal local computer certificate store, I exported the certificate with the private key to a file
  • Used PowerShell to create the Office Web Apps Farm with the cmd:
    • New-OfficeWebAppsFarm -InternalURL https://wac.contoso.dk -ExternalURL https://wacext.contoso.dk -CertificateName WacFarm -Verbose -AllowHttp:$true

On wac2.contoso.dk

I did the following steps:

  • Installed Office Web Apps Server 2013 and the March 12, 2013 update
  • Used the MMC certificate snap-in to import the certificate, I had exported on wac1.contoso.dk, into the personal local computer certificate store
  • Used PowerShell to join wac2 to the Office Web Apps Farm, which has wac1.contoso.dk as the Master
    • New-OfficeWebAppsMachine -MachineToJoin wac1.contoso.dk

The tricky part to get right was the last command. You have to run it on the machine you wish to join to the farm, and you have to reference an existing machine in the farm. It needs the reference to be able to read the farm settings.

Comments
  • Hi Jens,

    Very interesting post.  I assume a HLB (or HLB context) is always required for the web traffic as it is with Lync 2013?

    Please can you share the HLB configuration, as in whats ports are load balanced and if any particular extra configuration is required on the HLB?

    Regards,

    Dave

    Jens>Hi Dave, you don't need HLB, other types will work as well http://technet.microsoft.com/en-us/library/jj219435.aspx#loadbalancer. In my lab I use DNS load balancing, but that's a lab :-)

  • Hi,

    Why do you use the "-AllowHttp:$true" parameter while building your HTTPS farm ?

    Jens>No special reason other than also allowing it for http.

  • When creating a farm - 2 nodes and you created farm with PS command:

    New-OfficeWebAppsFarm -InternalURL https://wac.contoso.dk -ExternalURL https://wacext.contoso.dk -CertificateName WacFarm -Verbose -AllowHttp:$true

    On the second node would i run PS command

    New-OfficeWebAppsMachine -MachineToJoin wac1.contoso.dk

    Why on URL wac1.contoso.dk and not on  the NLB name?

    Jens>The parameter name implies the machine and that is why I used that.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment