Installing Office Web Apps 2013 and Integrating with Lync, Exchange, SharePoint and Online Viewers
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 as five virtual machines with Windows Server 2012 RTM. All servers are member of the same Active Directory Domain Services home.intranet. The picture below shows the servers and functions:
http://1.bp.blogspot.com/-CKmDDcUXPDU/URzTykUcaoI/AAAAAAAAE70/F6QCjxGdD78/s400/Office2013.jpg
The DNS zone home.intranet is configured with these 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
- Common HTTP Features
Install the following Feature Server on the server:
- Ink and Handwriting Services
Execute the following command in Windows PowerShell
| Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-Framework-Features, NET-Framework-Core, NET-HTTP-Activation, NET-Non-HTTP-Activ, NET-WCF-HTTP-Activation45 -source D:\sources\sxs |
http://3.bp.blogspot.com/-5IXJnGoZs0Q/UJldbP-rh2I/AAAAAAAAExg/7znMRjSfQk8/s640/ps01.png
After the command complete, restart the server.
Install Office Web Apps Server
Download the disk image from Microsoft licensing portal and mount on the server.
http://1.bp.blogspot.com/-vbOL65hKGGQ/UJRlCHDXChI/AAAAAAAAEos/dm25yrtDr5g/s320/OffWeb02.png
Execute the server install and accept the license terms
http://3.bp.blogspot.com/-OTCLpjAR-pU/UJRlD8_UG_I/AAAAAAAAEo0/us_dtpck9Cs/s320/OffWeb03.png
Select the file location for the install
http://1.bp.blogspot.com/-K_esgju__zA/UJRlExRTAiI/AAAAAAAAEo8/S3Ko8G9qtT4/s320/OffWeb04.png
The wizard installs the files and services, then click Close
http://4.bp.blogspot.com/-E3lr_krODv0/UJRlFi-BblI/AAAAAAAAEpE/RSWrOSfgNsQ/s320/OffWeb05.png
http://3.bp.blogspot.com/-casWaWwRncw/UJRlHKFc9PI/AAAAAAAAEpM/RyoYX-GdCdI/s320/OffWeb06.png
Create the Office Web Apps Server farm
Digital Certificate Installed
For this scenario I will publish the services using only HTTPS.
Once IIS is installed, one digital certificate with following names.
| http://3.bp.blogspot.com/-0XDjRMgccsw/UJRlIDjzwEI/AAAAAAAAEpU/cv67L6UPD34/s320/OffWeb07.png | http://4.bp.blogspot.com/-rQtYI3WJOHU/UJRlJNrfrBI/AAAAAAAAEpc/KV4B8zgemT8/s320/OffWeb08.png |
The Friendly Name is configure as Office Web Certificate
http://1.bp.blogspot.com/-ytr4Whke-AM/UJRoJ3xbfqI/AAAAAAAAEqE/jZOjmmZawSo/s320/OffWeb09.png
Configure URLs
With the certificates installed. execute the following in PowerShell. The -EditEnable parameter enables Office archives to be edited 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
http://2.bp.blogspot.com/-VsPf1IiG81g/UJRt-wuu3FI/AAAAAAAAEqs/7mtWAIBHpeg/s400/OffWeb10.png
Testing the Configuration
To verify that the configuration was successful, access the configured URL https://<Server Name>/hosting/discovery. A page containing XML should be shown like the image below.
http://4.bp.blogspot.com/-hF0Wa_hTI7s/UJRuw3ypzJI/AAAAAAAAEq0/ihrHJ25UIF8/s400/OffWeb11.png
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:
| http://1.bp.blogspot.com/-tbdIfklWRkw/UJpRo2_GjPI/AAAAAAAAE18/om9IcuhvKEc/s320/Offw40.png | http://1.bp.blogspot.com/-QNH-3lH_6F8/UJpRpvRFlhI/AAAAAAAAE2E/P1rp_Pu0oAA/s320/Offw41.png |
The certificate was created by the same certificate server that generated the certificate for Office Web Apps Server.
http://4.bp.blogspot.com/-nUMK60LSocw/UJpRqzzE6LI/AAAAAAAAE2M/ctlhr7dImNw/s320/Offw42.png
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
http://3.bp.blogspot.com/-sKviohd4ZP4/UJVpshOAinI/AAAAAAAAEsM/hCIoCeCP58w/s640/OffWeb12.png
Verifying the Configuration
Use the Get-OrganizationConfig cmdlet to verify URL
Get-OrganizationConfig | Format-List WACDiscoveryEndPoint
http://2.bp.blogspot.com/-Sre0xtIyBgA/UJVpIsaH3dI/AAAAAAAAErc/kT1DdqHgiTc/s640/OffWeb13.png
After the setting, an event ID 140 and 142 are created in the Application event log on Exchange Server
http://4.bp.blogspot.com/-oxbFsISIUcg/UJVpN2XUjrI/AAAAAAAAErs/jxnGR1GNBQc/s320/OffWeb15.png
http://2.bp.blogspot.com/-t5yFieyNSnY/UJVpO4C4ZvI/AAAAAAAAEr0/DIEswl3ll3g/s320/OffWeb16.png
Enabling Web Ready
By default, the Web Ready feature is enabled. The cmdlet Set-OwaVirtualDirectory is used 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
*
http://1.bp.blogspot.com/-rFb0qULp9F4/UJV_PdNha3I/AAAAAAAAEs0/XeKtmVRce0M/s400/OffWeb19.png
View Document
To view the document using the Office Web click Preview in any email attachment
http://2.bp.blogspot.com/-lBoUEfQVZxM/UJVpPr2KvJI/AAAAAAAAEr8/U7sJIiZt1wU/s320/OffWeb17.png
The document should open in browser
http://2.bp.blogspot.com/-Mquo8S8Tmt4/UJVpRHe_srI/AAAAAAAAEsE/PrGkMW5nOjQ/s320/OffWeb18.png
Configure Lync Server
Configure Front End Server to use Office Web Apps Server
Enable Lync Server 2013 to use Office Web Apps Server for PowerPoint presentation. Open the Topology Builder and navigate to Shared Components, right click on Office Web Apps Servers and select New Office Web Apps Server.
http://1.bp.blogspot.com/-7XZOThXQSc4/UJmwACCpzeI/AAAAAAAAEy4/VQn3RorIPS4/s320/OffWeb21.png
Set up the publish name of the server and click OK.
http://2.bp.blogspot.com/-sBEMTyDNStk/UJmwBXyXoWI/AAAAAAAAEzA/ISnMXD9ShE4/s320/OffWeb22.png
In Topology Builder, right click on Front End Server and select *Edit Properties... *
http://4.bp.blogspot.com/-jctSkQgv-fg/UJmwDJldJII/AAAAAAAAEzI/o_Ps8T7Lh4g/s320/OffWeb23.png
Check the box Associate pool with an Office Web Apps Server and choose the pool created.
http://3.bp.blogspot.com/-aCtmBaPZ-rg/UJmwEYQppCI/AAAAAAAAEzQ/j18X7mcM1l4/s320/OffWeb24.png
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
http://2.bp.blogspot.com/-C-QY_kfshgo/UJmwFnwIMYI/AAAAAAAAEzY/mUdLWyGy5p8/s320/OffWeb25.png
And the log of the discovery of the URLs configured in Office Web Apps with ID 41032
http://4.bp.blogspot.com/-X14NRxA-l_A/UJmwGo_-mCI/AAAAAAAAEzg/zaOtqz3nuRw/s320/OffWeb26.png
Presentation Sharing
Share a presentation between the clients to see if the servers are working
http://4.bp.blogspot.com/-VIAiV-ab9aE/UJmjyPH-ALI/AAAAAAAAEyM/BclYFdRqicM/s320/OffWeb20.png
The person who is sharing the presentation needs a minimum of PowerPoint and Office Shared Features installed on the machine.
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
| http://3.bp.blogspot.com/-rlONAe_g7ws/UJfGIGpznMI/AAAAAAAAEtg/uI1il5Y1yKA/s320/offish01.png | http://2.bp.blogspot.com/-ucQUbeCEH5s/UJfGJDH9PbI/AAAAAAAAEto/2vynOqra720/s320/offish02.png |
A caution to be taken is that the certificate must be trusted on the server of Office Web Apps
http://2.bp.blogspot.com/-rpo0lzfGkjo/UJfGJs2XuiI/AAAAAAAAEtw/DLGvjkbs_6c/s320/offish03.png
Create a Link Between SharePoint and Office Web Server
To create a link between SharePoint Server and Office Web Apps Server, execute PowerShell on the SharePoint Server. Since the service will be Internet published, the external FQDN name is used to configure the link.
*New-SPWOPIBinding -ServerName <Office Web Apps Server FQDN> *
http://1.bp.blogspot.com/-j-sLYlAcLjY/UJfHpkBXLuI/AAAAAAAAEt4/_8CHussSwXQ/s400/offish04.png
Additionally, alter the zone to allow the internet publication
Set-SPWOPIZone –zone “external-https”
http://4.bp.blogspot.com/-6USFmJ4c8_o/UJfHqQ4PjsI/AAAAAAAAEuA/I53MwQx1akk/s400/offish05.png
Testing access
To check if the link is working properly, login into the portal that contains any Office document published
http://3.bp.blogspot.com/-ekYoqiX3cmw/UJfLABaT01I/AAAAAAAAEus/UDS1mn-0BwQ/s320/offish06.png
Clicking on the document window opens to edit directly if you click next to the name of the document preview window is displayed
http://3.bp.blogspot.com/-a2E-Zu2jQOE/UJfLAQfGKuI/AAAAAAAAEuw/GmhsHAW13B8/s320/offish07.png
http://2.bp.blogspot.com/-ZWSJx6RGLTc/UJfLA-Wrz2I/AAAAAAAAEu4/iOXTGPoRR-U/s320/offish08.png
http://4.bp.blogspot.com/-waJQfhEGd7s/UJfLBkJu_7I/AAAAAAAAEvE/yRzlQQjeNVI/s320/offish09.png
To edit the document click *Edit *
http://1.bp.blogspot.com/-26PRqkYsPxs/UJfLCAX1R7I/AAAAAAAAEvM/81WK2CxyZyM/s320/offish10.png
The document is displayed in the browser
http://3.bp.blogspot.com/-AOLJsL227q0/UJfLClq8G3I/AAAAAAAAEvU/0YmZaamvYZo/s320/offish11.png
Configuring Online Viewers
To enable the feature Online Viewers execute the PowerShell in Office Web Apps Server
Set-OfficeWebAppsFarm -OpenFromUncEnabled -OpenFromUrlEnabled
http://1.bp.blogspot.com/-nTZWlEf4NMA/UJnBHlgElxI/AAAAAAAAE0M/0feQgMLC1a8/s320/OffWeb30.png
Configure a Bind on port 80 in IIS
http://1.bp.blogspot.com/-XZGKcn8yXVY/UJnBJWUqXCI/AAAAAAAAE0U/jYWjwlU7QMI/s320/OffWeb31.png
http://3.bp.blogspot.com/-zlrm69P4sAQ/UJnBKjeRNlI/AAAAAAAAE0c/s3xJs9kwG9g/s320/OffWeb32.png
With the features enabled, a portal is created on Office Web Apps Server. This portal helps to create the links for the files in a shared folder. Access https://<Office Web Apps Server>/op/generate.aspx
http://1.bp.blogspot.com/-y2YUC3-lCes/UJkPerdLd_I/AAAAAAAAEws/MOwMrrCmrCY/s320/OffVw01.png
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
http://1.bp.blogspot.com/-z7YScdotDtM/UJnD7GiT1jI/AAAAAAAAE1Q/txPw4GVcnmU/s320/OffWeb34.png
Using the link it is possible to open the article
http://2.bp.blogspot.com/-DuC7HjAO0V4/UJkPfeHvrYI/AAAAAAAAEw0/lCEttNBuNk0/s320/OffVw02.png
Other Languages
This article is also available in the following languages:
Brazilian Portuguese
This article was originally written by:
**Fernando Lugão Veltem **
**blog: ** http://flugaoveltem.blogspot.com/
**twitter: ** @ flugaoveltem