How to Install Office Web App 2013

Installation guide

The process step of installing Office Web App 2013 are as follows:

  1. Identity the server that will install Office Web App has meet the hardware, OS and software requirements (For more details read section 1, 2, 3 & 4 below)
  2. Check that the server has met the firewall requirements (For more details read section 5)
  3. Download the Office Web App installation file, any SP and other software for the appropriate OS of the server (See section 6 below)

1. Software, hardware, and configuration requirements for Office Web Apps Server

You can install Office Web Apps Server as a:
  • single-server Office Web Apps Server farm, or as
  • a multi-server, load-balanced Office Web Apps Server farm.
  •  physical servers or virtual machine instances, but can’t install other server applications (such as SharePoint 2013 or SQL Server) on the same server as Office Web Apps Server.

In environments that contain actual user data, we always recommend that you use HTTPS, for which you’ll have to obtain a certificate. If you’re using multiple servers in your farm, you’ll have to configure a hardware or software load-balancing solution. You can learn more about these scenarios in the following sections.


2. Hardware requirements

Office Web Apps Server uses the same minimum hardware requirements as SharePoint Server 2013. You can find the full set of SharePoint 2013 requirements in Hardware requirements—web servers, application servers, and single server installations.


3. Operating System requirements

Can run Office Web Apps Server on the following operating systems:

  • The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter with the Update for Windows Server 2008 R2 x64 Edition installed
  • The 64-bit edition of Windows Server 2012 Standard or Datacenter
  • The 64-bit edition of Windows Server 2012 R2. To use this operating system, you must use Office Web Apps Server Service Pack 1 (SP1).

4. Other software requirements

  • Don’t install any other server applications on the server that’s running Office Web Apps Server. This includes Exchange Server, SharePoint Server, Lync Server, and SQL Server. If you have a shortage of servers, consider running Office Web Apps Server in a virtual machine instance on one of the servers you have.
  • Don’t install any services or roles that depend on the Web Server (IIS) role on port 80, 443, or 809 because Office Web Apps Server periodically removes web applications on these ports.
  • Don’t install any version of Office. If it’s already installed, you’ll need to uninstall it before you install Office Web Apps Server.
  • Don’t install Office Web Apps Server on a domain controller. It won’t run on a server with Active Directory Domain Services (AD DS)

Install bellow additional software which are prerequisites for Installation of Office Web App Server.


5. Firewall requirements

Make sure the following ports aren’t blocked by firewalls on either the server that runs Office Web Apps Server or the load balancer:

      • Port 443 for HTTPS traffic
      • Port 80 for HTTP traffic
      • Port 809 for private traffic between the servers that run Office Web Apps Server (if you’re setting up a multi-server farm)

6. Downloads, server roles, and features that are required for Office Web Apps Server

From this blog, Office Web App server installer file is no longer availiable as a FREE download from Microsoft site. Instead it is availiable for download from Volume Licensing Service Center (VLSC) below:

Download, server role, or feature If you’re installing on Windows Server 2008 R2 If you’re installing on Windows Server 2012 If you’re installing on Windows Server 2012 R2
Download: Office Web Apps Server Office Web Apps Server Office Web Apps Server Office Web Apps Server
Download: Office Web Apps Server SP1 Recommended Recommended Office Web Apps Server SP1
Download: Correct version of .NET Framework .NET Framework 4.5 .NET framework 4.5 is already installed .NET Framework 4.5.2
Download: Update for Windows Server 2008 R2 x64 Edition Update for Windows Server 2008 R2 x64 Edition Not applicable Not applicable
Download: Windows PowerShell 3.0 Windows PowerShell 3.0 Already installed Already installed
Server role: Web Server (IIS) Here are the minimum role services required for the Web Server (IIS) server role.

Common HTTP Features

  • Static Content
  • Default Document

Application Development

  • ASP.NET
  • .NET Extensibility
  • ISAPI Extensions
  • ISAPI Filters
  • Server Side Includes

Security

  • Windows Authentication
  • Request Filtering

Management Tools

  • IIS Management Console

The following options are recommended but not required:

Performance

  • Static Content Compression
  • Dynamic Content Compression
Here are the minimum role services required for the Web Server (IIS) server role.

Management Tools

  • IIS Management Console

Web Server

  • Common HTTP Features
  • Default Document
  • Static Content

Security

  • Request Filtering
  • Windows Authentication

Application Development

  • .NET Extensibility 4.5
  • ASP.NET 4.5
  • ISAPI Extensions
  • ISAPI Filters
  • Server Side Includes

The following services are recommended but not required:

Performance

  • Static Content Compression
  • Dynamic Content Compression
Here are the minimum role services required for the Web Server (IIS) server role.

Management Tools

  • IIS Management Console

Web Server

  • Common HTTP Features
  • Default Document
  • Static Content

Security

  • Request Filtering
  • Windows Authentication

Application Development

  • .NET Extensibility 4.5
  • ASP.NET 4.5
  • ISAPI Extensions
  • ISAPI Filters
  • Server Side Includes

The following services are recommended but not required:

Performance

  • Static Content Compression
  • Dynamic Content Compression
Feature: Ink and Handwriting Services Ink and Handwriting Services

  • Ink Support
Ink and Handwriting Services

  • Ink Support is not required.
Ink and Handwriting Services

  • Ink Support is not required.

7.Installing Office Web App Server

Perform these procedures on all servers that will run Office Web Apps Server.

Figure: The steps to prepare servers for Office Web Apps Server

The three main steps to prepare servers for Office Web Apps Server.

7.1 Follow instructions about running PowerShell commands at “Prepare servers to run Office Web Apps Server” on the OS that is relevant for the server.

7.2 Restart the server after running the PowerShell cmdlet.

7.3 Run the setup.exe file of the download Office Web App Server file that was downloaded in step 6

7.4 After install of Office web apps  and before creating the new Office web apps server, then apply the following patch update MUST be done in the following order to be completely current with updates. Patched SP1 > April 2014 PU > May 2014 PU > June 2014 CU:

For the complete list of patch CU, see below table:

Build Number Build Name Information Link Download Link
15.0.4420.1007 RTM Download
15.0.4481.1005 March 2013 PU KB2760445 Download
15.0.4481.1508 April 2013 CU KB2810007 Download
15.0.4505.1001 April 9 2013 Hotfix KB2799821 Download
15.0.4517.1003 June 2013 CU KB2817350 Download
15.0.4535.1000 August 2013 CU KB2817521 Download
15.0.4551.1003 October 2013 CU KB2825686 Download
15.0.4551.1508 December 2013 CU KB2850013 Download
15.0.4551.1515 MS14-001 Security Update KB2863879 Download
15.0.4569.1000 Service Pack 1 KB2817431 Download
15.0.4569.1000 Service Pack 1 – Mark 2 Re-release KB2880558 Download
15.0.4605.1001 April 2014 CU (hot fix) KB2863899 Download
15.0.4615.1001 May 2014 KB2880453 Links in KB
15.0.4623.1001 June 2014 CU KB2881051 Download
15.0.4631.1000 July 2014 CU KB2883003 Download
15.0.4641.1001 August 2014 CU KB2883093 Download
15.0.4659.1001 October 2014 CU KB2889898 Download
November 2014 CU None None
15.0.4673.1000 December 2014 CU KB2899574 Download
January 2015 CU None None
15.0.4693.1001 February 2015 CU KB2956101 Download
15.0.4701.1001 March 2015 CU KB2956158 Download
15.0.4711.1000 April 2015 CU KB2965306 Download
15.0.4719.1002 May 2015 CU KB3039748 Download
15.0.4727.1001 June 2015 CU KB3054863 Download
15.0.4737.1001 July 2015 CU KB3054930 Download
15.0.4745.1001 August 2015 CU KB3055003 Download
15.0.4753.1001 September 2015 CU KB3085487 Download
15.0.4763.1000 October 2015 CU KB3085571 Download
15.0.4771.1000 November 2015 CU KB3101367 Download
December 2015 CU No Updates
January 2016 CU No Updates
15.0.4797.1001 February 2016 CU KB3114338 Download
15.0.4805.1000 March 2016 CU KB3114821 Download
15.0.4815.1000 April 2016 CU KB3114934 Download
15.0.4823.1003 May 2016 CU KB3115022 Download
15.0.4833.1003 June 2016 CU KB3115170 Download
15.0.4841.1000 July 2016 CU KB3115289 Download
15.0.4849.1000 August 2016 CU KB3115446 Download

7.5 Download and install language packs for Office Web Apps Server.


8. Deploy Office Webs Server Farm

The next step is to create Office Web Apps Server farm that uses either HTTP or HTTPS with certification.

NOTE: Use HTTP if the farm is a test\development server. Otherwise always use HTTPS on production server farm with certificate install.

The steps are below assuming that certificates has been installed, deployed and configure.

  • Create Office Web Apps Server Farm (See section 8.1)
  • Verify Farm is working OK (See section 8.2)
  • Configure the host

8.1 Create the Office Web Apps Server Farm
Use the New-OfficeWebAppsFarm command to create a new Office Web Apps Server farm that consists of a single server, as shown in the following example for HTTP for a test/dev server:

New-OfficeWebAppsFarm -InternalURL “http://servername” -AllowHttp -EditingEnabled

Parameters

  • –InternalURL is the name of the server that runs Office Web Apps Server, such as http://servername.
  • –AllowHttp configures the farm to use HTTP.
  • –EditingEnabled enables editing in Office Web Apps when used with SharePoint 2013. This parameter isn’t used by Lync Server 2013 or Exchange Server 2013 because those hosts don’t support editing.

The PowerShell cmdlet for creating new Office Web Apps server farm using HTTPS on production server with trusted certificate already installed and configured on the farm:

New-OfficeWebAppsFarm -InternalUrl Https://wac.Contoso.com -ExternalUrl Https://Wac.Contoso.com -CertificateName WacCert -AllowHttp

Parameters

In the above command, wac.contoso.com would be the Office Web App URL that we will be using (using same for internal and external, however this can be changed as per requirement)

  • InternalURL Refers to URL that will be used by Lync 2013 Clients connected to Lync server internally.
  • ExternalURL Refers to URL that will be used by Lync 2013 Clients connected to Lync server externally.
  • CertificateName is set to ‘WacCert’ which is the friendly name of the certificate that we created earlier.

8.2 Verify Office Web Apps Server farm was created successfully
To verify Office Web Apps server was created in step 3.2.1, open IE browser and go to: http://servername/hosting/discovery , where servername is the name of the server farm that had office Web App installed.

At the end of this step, we have installed office web app server, created an Office Web App Server Farm and have associated valid certificate that was created earlier, Office Web App Server is now ready to be used with SharePoint 2013 host.


9. Configure the SharePoint host

The farm is now ready to provide Office Web Apps functionality to host over HTTP. To configure Office Web apps for hosting SharePoint 2013, follow the steps below. For more information, go to: https://technet.microsoft.com/en-au/library/ff431687.aspx

  1. Logged into the SharePoint 2013 server farm
  2. Right-click SharePoint 2013 Management Shell to display the app bar.
  3. In the app bar, click Run as administrator.
  4. Create the binding between SharePoint 2013 and Office Web Apps Server:

4a . In a test SharePoint environment that uses HTTP, type the following:

New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP

4b. In a production SharePoint environment that uses HTTPS, type the following:

New-SPWOPIBinding -ServerName <WacServerName>

<WacServerName> is the fully qualified domain name (FQDN) of the URL that you set for the internal URL. This is the point of entry for Office Web Apps Server traffic. For this test environment, you need to specify the –AllowHTTP parameter to allow SharePoint 2013 to receive discovery information from the Office Web Apps Server farm by using HTTP. If you don’t specify –AllowHTTP, SharePoint 2013 will try to use HTTPS to communicate with the Office Web Apps Server farm, and this command won’t work.

5. View the WOPI zone for SharePoint bindings, by typing the following PowerShell cmdlet: Get-SPWOPIZone

Office Web Apps Server uses zones to determine which URL (internal or external) and which protocol (HTTP or HTTPS) to use when it communicates with the host, in this case, SharePoint 2013. By default, SharePoint Server 2013 uses the internal-https zone.If SharePoint was configured to use externally, then you use internal-https. If SharePoint was configured to be used internally, then you use internal-http. The WOPI zone displayed by this cmdlet should be internal-http. So if it’s displayed wrongly go to step 6. Otherwise go to step 7.

6. Change the WOPI zone to internal-http – If the result from Step 3 was internal-https, run the following command to change the zone to internal-http. You need to make this change because the zone of SharePoint 2013 must match the zone of the Office Web Apps Server farm. Type this PowerShell cmdlet:  Set-SPWOPIZone -zone “internal-http”

Verify that the new zone is internal-http by running Get-SPWOPIZone again.

7. Change the AllowOAuthOverHttp settings in SharePoint to True – To use Office Web Apps with SharePoint 2013 over HTTP in a test environment, you need to set AllowOAuthOverHttp to True. Otherwise Office Web Apps won’t work. You can check the current status by running the following example: (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

If this command returns false, run the cmdlet below to set this to true:

$config = (Get-SPSecurityTokenServiceConfig)

$config.AllowOAuthOverHttp = $true

$config.Update()

Run the following command again to verify that the AllowOAuthOverHttp setting is now set to True: (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

9.1  Verify that Office Web Apps is Working


Further Information

For more information, read the following resources in this order:

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s