Table of Contents

• Overview
  • Prerequisites for Installing Office Web Apps
  • Install Office Web Apps Server
• Create the Office Web Apps Server farm
  • Digital Certificate Installed
  • Configure URLs
  • Testing the Configuration
• Configure Servers to Use Office Web Apps
  • Configure Exchange Server
    • Digital Certificate OWA
    • Configure Office Web Apps URL
    • Verifying the Configuration
    • Enabling Web Ready
    • View Document
  • Configure Lync Server
    • Configure Fron End Server to use Office Web Apps Server
    • Verifying the configuration
    • Presentation Sharing
  • Configure SharePoint Server
    • Certificate installed on SharePoint Server
    • Create a Link Between SharePoint and Office Web Server
    • Testing access
  • Configuring Online Viewers
  • Other Languages
    • Brazilian Portuguese

Overview

In this paper I will show how to install the first Office Web Apps Server and create a server farm using HTTPS. After the farm configuration I will configure Exchange Server 2013, Lync Server 2013, SharePoint Server 2013 to use Office Web Apps Server to work with Office archives. 

Review the guidelines and feature in the article Understanding Office Web Apps 2013. 

All servers in this scenario are installed five virtual machines with Windows Server 2012 RTM, all server are member of the same Active Directory Domain Services home.intranet. In the picture below is showing the server and functions:
 


The DNS zone home.intranet is confiure with the records:

FQDN	IP	Server Role
Hm01.home.intranet	172.16.1.245	Domain controller and Enterprise Certificate Services
Hm02.home.intranet	172.16.1.246	Lync Server 2013
Hm03.home.intranet	172.16.1.247	Exchange Server 2013
Hm10.home.intranet	172.16.1.248	SharePoint Server 2013
Hm11.home.intranet	172.16.1.251	Office Web Apps Server 2013

The domain home.com.br  is configured as a Sip domain on Lync Server and a authoritative domain on Exchange Server. The following records are created for the zone:

FQDN	IP	Server Role
OfficeWeb.home.com.br	172.16.1.247	Office Web Apps Web Server
Correio.home.com.br	172.16.1.246	Exchange OWA
SharePoint.home.com.br	172.16.1.248	Public URL SharePoint

Prerequisites for Installing Office Web Apps

Install the following server roles and services

• Web Server
  • Common HTTP Features
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • Static Content
  • Health and Diagnostics
    • HTTP Logging
  • Performance
    • Static Content Compression
    • Dynamic Content Compression
  • Security
    • Request Filtering
    • Windows Authentication
  • Application Development
    • . 4.5 Net Extensibility
    • ASP.NET 4.5
    • ISAPI Extensions
    • ISAPI Filters
    • Server Side Includes
  • Management Tools
    • IIS Management Console

Install the following Feature Server on the server:

• Ink and Handwriting Services

After the shell complete restart the server. 

Install Office Web Apps Server

Download the from Microsoft portal and mont on the server.

Execute the server install and accept the license terms

Select the file location for the install 

The wizard install the files and services and click Close

Create the Office Web Apps Server farm

Digital Certificate Installed

For this scenario I will publish the services using only HTTPS.  
On the IIS is installed one digital certificate with following names. 


The  Friendly Name is configure as Office Web Certificate

Configure URLs

With the certificates installed execute the Power Shell. The -EditEnable parameter enable Office archives to be edit on Sharepoint 2013. 

New-OfficeWebAppsFarm -InternalUrl https://<Internal FQDN Name of Office Web Apps Server> -ExternalUrl <Public FQDN create for internet publication> –CertificateName "Certificate Friendly Name" -EditingEnabled

Testing the Configuration

To verify that the configuration was successful, access the configured URL https://<Server Name>/hosting/discovery. A page should be shown like the print

Configure Servers to Use Office Web Apps

Configure Exchange Server

This session demonstrates how to configure the integration of Office Web Apps 2013 with Exchange Server 2013.

Digital Certificate OWA

 The Exchange 2013 OWA is configured with the digital certificate with the following names:

Configure Office Web Apps URL

Start the Exchange Management Shell and use the cmdlet to configure the URL address of the Office Web Apps

Set-OrganizationConfig -WACDiscoveryEndPoint https://<Office Web Apps Server>/hosting/discovery

Verifying the Configuration

Use the cmdlet to verify URL 

Get-OrganizationConfig | Format-List WACDiscoveryEndPoint

After the setting a event ID 140 and 142 are created under Application on Exchange Server

Enabling Web Ready

By default the Web Ready feature is enable, the cmdlets Set-OwaVirtualDirectory to enable or disable functionality
Enable access to private computers: 

Set-OwaVirtualDirectory "Hm03\owa (Default Web Site)" -WacViewingOnPrivateComputersEnabled $true

To configure access on public computers:

Set-OwaVirtualDirectory "Hm03\owa (Default Web Site)"-WacViewingOnPublicComputersEnabled $ true

View Document

To view the document using the Office Web click Preview in any email attachment

The document should open in browser

Configure Lync Server

Configure Fron End Server to use Office Web Apps Server

Enable Lync Server 2013 to use Office Web Apps Server for Power Point presentation open the Topology Builder navigate to Shared Components, right click on Office Web Apps Servers and select New Office Web Apps Server...

Set up the publish name of the server and click OK.

On Tipology Builer right click on Front End Server and select Edit Properties... 

Check the box Associate pool with an Office Web Apps Server and configure the pool created. 

Verifying the configuration

After publishing the topology changes two events are created in the log in the Lync Server 
Logging stating that the Office Server was added to the list of trusted servers with ID 33022

And the log of the discovery of the URLs configured in Office Web Apps with ID 41032

Configure SharePoint Server

Certificate installed on SharePoint Server

For configuration SharePoint Server 2013 with external URL configured https://SharePoint.home.com.br. was installed on the server a digital certificate with all the names configured for access to the portal 


A caution to be taken is that the certificate must be trusted on the server of Office Web Apps

Create a Link Between SharePoint and Office Web Server

To create a link between Sharepoint Server and Office Web Apps Server execute Power Shell on the Sharepoint Server. Since the service will be internet publish the external FQDN name is used for configure the link. 

New-SPWOPIBinding -ServerName <Office Web Apps Server FQDN> 

And alter the zone to allow the internet publication 

Set-SPWOPIZone –zone “external-https”

Testing access

To check if the link is working properly login into the portal that contains any Office document published

Clicking on the document window opens to edit directly if you click next to the name of the document preview window is displayed


To edit the document click Edit 

The document is displayed in the browser

Configuring Online Viewers

To enable the feature Online Viewers execute the Power Shell in  Office Web Apps Server 

Set-OfficeWebAppsFarm -OpenFromUncEnabled:$True -OpenFromUrlEnabled:$True

Configure a Bind on the port 80 IIS
With the feature enable a portal is created on Office Web Apps Server. This portal helps to create the links for the files on a share folder. Access https://<Office Web Apps Server>/op/generate.aspx

To finish the configuration you need to change the NTFS permission on the file server and add the server account that running Office Web Apps right to read the archives
Using the link is possible to open the article 

Other Languages

 This article is also available in the following languages:

Brazilian Portuguese

• Instalação do Office Web Apps 2013 e Integração com o Lync, Exchange e SharePoint

This article was originally written by: 
Fernando Lugão Veltem 
blog:  http://flugaoveltem.blogspot.com/  
twitter:  @ flugaoveltem