It is Assuming that you already have a SharePoint farm Prepared with an Accessible Site Collection. This guide will not go through the SharePoint Server Deployment but only the Integration of Office Web Apps for SharePoint in order to allow your end users to open/edit their Office Documents within the Browser.
Steps:
1. Installing Prerequisites in OWA servers for Office Web apps 2. Creating DNS Host Records
3. Configuring Windows NLB for Load balancing and High Availability 4. Configuring SSL Certificates using Active Directory Certificate Services 5. Installing Office Web Apps
6. Configuring Office Web Apps Farm
7. Joining Member Servers to the Office Web Apps Farm 8. Integrating with SharePoint Farm
9. Testing Functionality
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com 1. Installing Office Web Apps Prerequisites
You must have a Domain User account (Such as SharePoint Farm Account) created in order to Install Office Web Apps.
After Creating your Virtual Machine, Login to the same and Prepare it with necessary Network and Domain Configurations such as defining IP addresses and joining it to the respective domain.
Then Login in to the server using local administrative credentials and add the User Account created for Office Web Apps in to the Local Administrators Group.
Run the following Scripts in Windows PowerShell in order to prepare your OWA servers with Prerequisites. You can define the SXS path to source files if your server doesn’t have the internet connectivity by simply passing the -Source Parameter (e.g. -Source D:\Sources\sxs)
It might prompt for restarting once finished.
For Windows Server 2008 R2 Install Following Software’s
o Windows Server 2008 R2 Service Pack 1 o .NET Framework 4.5
o Windows PowerShell 3.0
o Platform update for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB2670838)
Right Click on Windows PowerShell and Run it as Administrator. Then run the following Import-Module ServerManager
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com For Windows Server 2012 R2
Install - NET Framework 4.5.2
Then Run the following in PowerShell
Add-WindowsFeature
2. Creating DNS Host Records
Next to create the HostA Record for NLB Cluster Name (Which will be the ultimate Server Name of OWA Farm).
Direct to your DNS Server and Simply Create a Host AAA Record points to your Target NLB IP. You need a dedicated IP V4 address for this.
Open Up the DNS Manager Console in your DNS Server and Right Click on the Respective Zone and hit New Host (A or AAAA) to create a new Host record.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
Provide the Name and IP It points to (which is the desired NLB Cluster IP) and hit Add Host to create.
Record is ready for you now.
3. Configuring Windows NLB
Then the next step is to Install Windows NLB for both OWA Servers in order to configure the Load balancing
Open up Server Manager and Click Add Roles and Features from the top. This has to be done in both OWA servers.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com Just Click next on the first Screen
Leave the Default Selection here and hit Next
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com Default choice here too and hit Next to proceed
Select the Network Load Balancing from the Feature list and hit Next to Install the feature then restart the server if prompted.
That Installed NLB feature for us and now let’s Setup Load Balancing Cluster. Open up Windows NLB Console from the primary Machine (OWA1). Make sure both Nodes are now ready with IP, Host Names, NLB Feature.
Right Click on the top level and Create a New Cluster
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com Provide the Name or IP of the Primary Server which will host the Cluster (Local Server). It will automatically resolve the IP and display the interface for you. Simple hit Next to proceed.
Leave these settings as it is unless you need a specific configuration for IP and Network Interfaces
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com Next Step is to define the Cluster IP. At this scenario it will be 192.168.150.132
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
IP Address will be already selected and define the FQDN of the Cluster name here and choose Operation mode based on your network. This server only got a single Network Interface so it has to be Multicast.
If you have Multiple Interfaces, you may choose Unicast Mode to make it function properly.
Hit Next to go ahead
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
You can edit the Port Rules to customize Ports or Protocols but not really necessary to get this function. Leaving the defaults will bring us what we need in this case.
If all went well, you can see the Cluster is created with the defined name and settings and Primary Host is added/Started with green health status.
Let’s go ahead and Add the second node here. Right Click on the Cluster Name and Add Host to Cluster
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
Type the Host Name or IP of your Secondary OWA Machine (OWA2 at this Case). Make sure it can communicate with the primary host and Windows Firewall Exceptions are added or Switched off so nothing will block the communication at this point.
If all good, it will resolve the IP over Name and Name over IP as below. Just Hit next to proceed.
Leave the Priority to Default (2) and State as Started
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
And then the Port Rules. Load Left as Equal and you can define if you need. Leave it as Default for better load Sharing.
Give it a moment
And Both nodes will come online and appear as Healthy if you have configured it properly.
To Verify the Availability of the Cluster, lets ping the Name. do it from one of the SharePoint Machine so you can identify any issues in the network.
So the NLB Cluster is All Set for us. Next is to Prepare the OWA Servers with SSL Certificates.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com 4. Configure SSL Certificates for OWA HTTPS
We are using Active Directory Certificate Service to Issue Web Server Certificates for our OWA Farm which will only be trusted and validated within the domain Network. For External Networks Such as Internet you need to purchase a Genuine SSL Certificate from a Third party vendor such as Verisign.
If you use Internal Certificates (Such as the one used in this scenario) your OWA WOPI URL will not be Valid for External Access and It Will Prompt the security Message with critical warning of content. So for Production environments, always use a valid Certificate.
Setting UP SSL
Open up Active Directory Certificate Services from your AD. At this point, our NORTHWIND AD will be the ultimate Certification Authority.
If you do not have this feature in your AD. You can Get it installed via Server manager Roles and Feature Installation Wizard.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
This Server Already has it Installed so it’s just to go ahead. Expand the Server and hit Manage
Now the Certificate Templates Console will be Opened for you in Edit mode. Right Click on the Web Server Template and Direct to Properties.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
Add the Computer Accounts (OWA1.Northwind.Int |OWA2.Northwind.Int) of your OWA Servers and the Service Account which will be using to setup OWA Farm for following Permissions. This will enable the Web Server Certificate Template to Enroll from these Two Servers.
Change Object types to following types.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com Allow all three objects for Read and Enroll Permissions.
That’s all from the Active Directory Side. Let’s move back to the OWA Servers and Open up MMC.EXE to Obtain Certificates.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com From the Console Root, Add/Remove Snap-In
Select Certificates
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
Expand the Certificates Root and Drill down to Personal. Right click on Personal and Request a New Certificate
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com New Certificate Enrolment Wizard will be prompted for you. Just Hit next to proceed
Active Directory Enrollment Policy will be selected by Default here so nothing much to do/ Hit Next here.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
You will then see the Web Server Policy is highlighted with the Exclamation Mark. Click on the Message there.
That will bring you to the Certificate Properties where you will be providing all the details of this certificates. Select the Subject Name Type as “Common Name” and Alternative Name Type as
“DNS”. Value for both of these field can be the same which is our OWA Farm Name. Basically this Certificate will be dedicated to the OWA Farm. It won’t validate any other purposes. Yet this may depend on your scenario and Environment.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com Once Entered, Add them to the selection on the right side.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
Direct to the General Tab and Provide the same Value for Friendly Name. Friendly name is the Name that you will use to recognize this Certificate at later time when you are pointing this Certificate from other Applications. Description Could be any.
Hit Apply to Complete
Then the Exclamation Message will be gone as you have successfully completed the Indexing of Information of the Certificate. Simply Check the Web Server Check box and Hit Enroll to obtain the Cert.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
Give it a few seconds and If everything good, the certificate will be successfully enrolled. If you are getting an error here saying that “Server or Service Unavailable”, You might need to restart the Certificate Server Service at your AD Server.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com We can now see the Certificate at the Certificate Store
Repeat the same for secondary OWA (OWA2) Server as well and then it completes our SSL Certificate Configuration Part.
5. Installing Office Web Apps Server 2013
Here Comes the real thing. As we have completed almost all the Prerequisites and Background Preparations for OWA Farm, we can proceed to the Installation and Farm Deployment.
Log in to the OWA Servers using the domain Account (Northwind\sp_farm_svc) you have crated. In this case it’s going to be the SharePoint Farm Account which will be used to Install OWA.
Map the Office Web Apps Server 2013 ISO (With Service pack 1) and Run it.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com As Always, you have agree to the License terms and Continue to Proceed then.
The Success Message will be appeared in just Few Minutes If everything went well.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
Now the Most Important Steps. Configuring the OWA farm is done through PowerShell. Best Tool for this is PowerShell ISE. From the OWA1 Right click on PowerShell Icon and Run ISE as
-Verbose (This Switch is to display the status)
-InternalUrl (This is the Internal Url referred from SharePoint Later)
-EditingEnabled (This will allow your users to Edit Documents in Browser itself)
-CertificateName (You can Define your SSL Cert using this Parameter. Or you can do it yourself manually via IIS Later)
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
-ExternalUrl (Can be Defined in addition to InternalUrl Swith if you are setting up an External Scenario)
If all went well, you will see the Result as above. And under the Machines it will show the OWA1 which is our Primary OWA Server in this farm.
Check the IIS to verify the Web Applications Creation and SSL Certificate Assignment
Open IIS manage and Check if These Two Web Applications are created
Note the Certificate Binding under the Site Bindings on the Right Panel
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com 6. Joining Secondary OWA machine to the Farm
Next step is to Join our Second Machine to the OWA Farm. Login to the OWA2 Machine using the same Domain credentials you used to Setup OWA1.
Open the PowerShell ISE as Administrator and run the Following from OWA2.
New-OfficeWebAppsMachine -MachineToJoin OWA1
-MachineToJoin (This switch is to Define your Primary OWA Server Name). basically this is the Master Machine.
That’s all from the OWA Farm Side. Next step is to Integrate OWA Farm to SharePoint but before that Let’s test our setup.
7. Testing the OWA farm
Simply try the Hosting Discovery URL from a Different Server (SharePoint Server Will do) https://officeapps.northwind.int/hosting/discovery
If you are Retrieving this XML Page as below with the parameters. It means you are all good to go.
Discovery URL working Means that your OWA Farm is accessible and Functioning well. so the next step is to Integrate OWA for SharePoint. Sometimes the Hosting URL may not work within the OWA Servers itself due to the loopback checking, best thing is you can check it outside the OWA Servers
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
The URL will not show any Warnings about the Certificate or Trust because it is valid internally within our Northind.Int Domain Environment. It will not be valid for Outside access unless it’s a valid External Certificate from a Vendor.
8. Integrate Office Web Apps with SharePoint 2013
SharePoint Environment is already done with a Host Named Site Collection which is also using HTTPS. This Scenario is fully setup for HTTPS in order to test the production level functionality. If you are using HTTPS for OWA Your SharePoint Site must use HTTPS too otherwise there is no point of using HTTPS on OWA.
Note: Recommended Way to Deploy OWA is Using HTTPS with a Valid SSL Certificate. HTTP is not recommended and it meant only for testing and Developmental Environments only.
In this scenario, we are using https://intranet.Northwind.Int Host header Site Collection for Integration testing. Below is the Default SharePoint Site which has some Sample documents uploaded and all good to go in SharePoint Side.
This SharePoint Farm also has two WFE Servers with NLB configured and this URL is fully load balanced with NLB.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com
Login to Your SharePoint APP Server and Run the Following in SharePoint Shell or PowerShell ISE.
From SharePoint Shell
New-SPWOPIBinding -Server OFFICEAPPS.NORTHWIND.INT
From PowerShell ISE
Add-PSSnapin Microsoft.SharePoint.Powershell -EA 0 New-SPWOPIBinding -Server OFFICEAPPS.NORTHWIND.INT
-Server (This parameter to Define Your OWA Farm Name. Not the Name of any OWA Machines)
If all Went well, you will see the above result. With defined Inputs such as Zone, Server Name etc…
That’s all from the SharePoint Fram side.
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com Let’s test out the functionalities from SharePoint Side now.
Note: Do not use Farm Account to test OWA. You must use a Different user account to test this as SharePoint Farm account is not allowed to open Documents from browser for security reasons.
Preview of a Document in Browser in WOPI Frame
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com Opening a Document
Editing a Document in Brower
Manoj Viduranga Karunarathne | http://manojviduranga.wordpress.com 9. Glossary
Server Did Not Respond - Error when Adding WOPI Zone in SharePoint - If you already have some other WOPI Zones this could happen, Or else Due to an Invalid Certificate on OWA Server.
Hosting/discovery Doesn’t Load - Mostly this happens if you try to open it from the OWA server itself. Try from another server. Also try to add the secondary Server and then load the URL.
Issue the Certificate for the Relevant Name - IF OWA1 (OWA1) or if OfficeApps.Northwind.int:
Cert has to be for the same Name if it’s a SAN Cert.