Deploy Office Web Apps Server

Posted on 16/09/2013 by

To prepare a server that runs Windows Server 2008 R2

  1. Install the following software:
  2. Next, open the Windows PowerShell prompt as an administrator and run the following command examples to install the required roles and services.

    For Windows Server 2008 R2

    Import-Module ServerManager

    And then run the follow command examples:

    Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-Security,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Console,Ink-Handwriting,IH-Ink-Support

    If you are prompted, restart the server when the command finishes.

To prepare a server that runs Windows Server 2012

  1. Open the Windows PowerShell prompt as an administrator and run the following command examples to install the required roles and services.

    For Windows Server 2012

    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

    If you are prompted, restart the server when the command finishes.

Step 2: Install Office Web Apps Server

Complete the following steps on all servers that will run Office Web Apps Server.

To install Office Web Apps Server

  1. Download Office Web Apps Server from the Microsoft Download Center.
  2. Take one of the following actions:
    • For Windows Server 2012, open the .img file directly and run Setup.exe (double-click it).
    • For Windows Server 2008 R2 SP1, use a program that can mount or extract .img files. Then run Setup.exe (double-click it).
  3. In the Office Web Apps Server 2013 Wizard, on the Read the Microsoft Software License Terms page, select I accept the terms of this agreement and then select Continue.
  4. On the Choose a file location page, select the folder where you want the Office Web Apps Server files to be installed (for example, C:\Program Files\Microsoft Office Web Apps), and then select Install Now. Note that, if this folder does not exist, Setup will create it for you.
  5. When Setup finishes installing Office Web Apps Server, choose Close.
  6. Download and install the Office Web Apps Server update KB2810007.
    Check for the most current Office Web Apps Server updates by reviewing the 2013 list on the TechNet Update center for Office, Office servers, and related products.

Step 3: Install language packs for Office Web Apps Server

Office Web Apps Server 2013 Language Packs enable users to view web-based Office files in multiple languages from SharePoint 2013 document libraries, Outlook Web Access (as attachment previews), and Lync 2013 (as PowerPoint broadcasts). If you want to learn more about how the language packs work, see Planning language packs for Office Web Apps Server.

To install the language packs, follow these steps.

To install language packs for Office Web Apps Server

  1. Download the Office Web Apps Server Language Packs from the Microsoft Download Center.
  2. Run WebAppsServerLP_en-us_x64.exe (double-click it).
  3. In the Office Web Apps Server Language Pack 2013 Wizard, on the Read the Microsoft Software License Terms page, select I accept the terms of this agreement and then select Continue.
  4. When Setup finishes installing Office Web Apps Server, choose Close.
Important Important:
  • To install language packs after the Office Web Apps Server farm is created, you must remove a server from the farm, install the language pack on it, and then add the server back to the farm.
  • All servers in the farm must have the language pack installed.

 

Deploy a single-server Office Web Apps Server farm in a test environment

The information here will help you install a single-server Office Web Apps Server farm that uses HTTP in a test environment. You don’t need a certificate or load balancer, but you do need a dedicated physical server or virtual machine instance that is not running any other server application. You can use this Office Web Apps Server farm to provide Office Web Apps functionality to SharePoint 2013 and Exchange Server 2013, but be aware of the following limitations:

  • The environment can be accessed only by internal users. No external URL is configured.
  • The environment can’t be used with Lync Server 2013, which requires HTTPS.

Step 1: Create the Office Web Apps Server farm

The code in the following example creates a new Office Web Apps Server farm that consists of a single server. The URL you specify for –InternalURL is the name of the server that runs Office Web Apps Server, such as http://servername. The –AllowHttp parameter configures the farm to use HTTP, and the –EditingEnabled parameter enables editing in Office Web Apps when it is used together with SharePoint 2013. The –EditingEnabled parameter is not used by Lync Server 2013 or Exchange Server 2013 because those hosts don’t support editing.

New-OfficeWebAppsFarm –InternalURL "http://servername" –AllowHttp -EditingEnabled

Additional parameters that configure translation services, proxy servers, clipart support, and Online Viewers are described in New-OfficeWebAppsFarm. You can find additional information about how to obtain licenses that allow users to edit files by using Office Web Apps Server in Plan Office Web Apps (Used with SharePoint 2013). To learn about how these licenses are used in SharePoint Server 2013, see Configure licensing in SharePoint Server 2013.

noteNote:
If components of the .NET Framework 3.5 were installed and then removed, you might see “500 Web Service Exceptions” or “500.21 – Internal Server Error” messages when you run OfficeWebApps cmdlets. To fix this, run the following sample commands from an elevated command prompt to clean up settings that could prevent Office Web Apps Server from functioning correctly:

For Windows Server 2008 R2

%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
iisreset /restart /noforce

For Windows Server 2012

dism /online /enable-feature /featurename:IIS-ASPNET45

Step 2: Verify that the Office Web Apps Server farm was created successfully

After the farm is created, details about the farm are displayed in the Windows PowerShell prompt. To verify that Office Web Apps Server is installed and configured correctly, use a web browser to access the Office Web Apps Server discovery URL, as shown in the following example. The discovery URL is composed of the value that you assigned to the InternalUrl parameter when you configured your Office Web Apps Server farm, and it is followed by /hosting/discovery.

http://servername/hosting/discovery

If Office Web Apps Server works as expected, you should see a Web app Open Platform Interface (WOPI)-discovery XML file in your web browser. The first few lines of that file should resemble the following example:

<?xml version="1.0" encoding="utf-8" ?> 
- <wopi-discovery>
- <net-zone name="internal-http">
- <app name="Excel" favIconUrl="http://servername/x/_layouts/images/FavIcon_Excel.ico" checkLicense="true">
<action name="view" ext="ods" default="true" urlsrc="http://servername/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" /> 
<action name="view" ext="xls" default="true" urlsrc="http://servername/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" /> 
<action name="view" ext="xlsb" default="true" urlsrc="http://servername/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" /> 
<action name="view" ext="xlsm" default="true" urlsrc="http://servername/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" />

Step 3: Configure the host

The farm is now ready to provide Office Web Apps functionality to hosts over HTTP. Visit the following articles for more information about how to configure hosts.

Deploy a single-server Office Web Apps Server farm that uses HTTPS

The information here will help you install a single-server Office Web Apps Server farm that uses HTTPS. You must have a certificate installed on the server as described in Securing Office Web Apps Server communications by using HTTPS . You can use this Office Web Apps Server farm to provide Office Web Apps functionality to SharePoint 2013, Lync Server 2013, and Exchange Server 2013.

Step 1: Create the Office Web Apps Server farm

The code in the following example creates a new Office Web Apps Server farm that consists of a single server. The URL that you specify for –InternalURL is the FQDN name of the server that runs Office Web Apps Server, such as http://servername.contoso.com. The URL that you specify for –ExternalURL is the FQDN name that can be accessed on the Internet. You must specify the friendly name of the certificate by using the –CertificateName parameter. The –EditingEnabled parameter is optional and enables editing in Office Web Apps when it is used together with SharePoint 2013. The –EditingEnabled parameter is not used by Lync Server 2013 or Exchange Server 2013 because those hosts do not support editing.

New-OfficeWebAppsFarm -InternalUrl "https://server.contoso.com" -ExternalUrl "https://wacweb01.contoso.com" -CertificateName "OfficeWebApps Certificate" -EditingEnabled

Additional parameters that configure translation services, proxy servers, clipart support, and Online Viewers are described in New-OfficeWebAppsFarm. You can find additional information about how to obtain licenses that allow users to edit files by using Office Web Apps Server in Plan Office Web Apps (Used with SharePoint 2013). To learn about how these licenses are used in SharePoint Server 2013, see Configure licensing in SharePoint Server 2013.

noteNote:
If components of the .NET Framework 3.5 were installed and then removed, you might see “500 Web Service Exceptions” or “500.21 – Internal Server Error” messages when you run OfficeWebApps cmdlets. To fix this, run the following sample commands from an elevated command prompt to clean up settings that could prevent Office Web Apps Server from functioning correctly:

For Windows Server 2008 R2

%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
iisreset /restart /noforce

For Windows Server 2012

dism /online /enable-feature /featurename:IIS-ASPNET45

Step 2: Verify that the Office Web Apps Server farm was created successfully

After the farm is created, details about the farm are displayed in the Windows PowerShell prompt. To verify that Office Web Apps Server is installed and configured correctly, use a web browser to access the Office Web Apps Server discovery URL, as shown in the following example. The discovery URL is composed of the value that you assigned to the InternalUrl parameter when you configured your Office Web Apps Server farm, and it is followed by /hosting/discovery.

https://server.contoso.com/hosting/discovery

If Office Web Apps Server works as expected, you should see a Web app Open Platform Interface (WOPI)-discovery XML file in your web browser. The first few lines of that file should resemble the following example:

<?xml version="1.0" encoding="UTF-8"?>
<wopi-discovery><net-zone 
name="internal-https"><app name="Excel" checkLicense="true" 
favIconUrl="https://wac.contoso.com/x/_layouts/images/FavIcon_Excel.ico"><action 
name="view" 
urlsrc="https://wac.contoso.com/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" 
default="true" ext="ods"/><action name="view" 
urlsrc="https://wac.contoso.com/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" 
default="true" ext="xls"/><action name="view"
noteNote:
Depending on the security settings of your web browser, you might see a message that prompts you to select Show all content before the contents of the discovery XML file are displayed..

Step 3: Configure the host

The farm is now ready to provide Office Web Apps functionality to hosts over HTTPS. Visit the following articles for more information about how to configure hosts.

Deploy a multi-server, load-balanced Office Web Apps Server farm that uses HTTPS

The information here will help you install a multi-server Office Web Apps Server farm that uses a load balancer and HTTPS. Before you begin these steps, you must have your load balancer configured as described in Load balancer requirements for Office Web Apps Server, and you must have a certificate installed on the load balancer as described in Securing Office Web Apps Server communications by using HTTPS . You can use this Office Web Apps Server farm to provide Office Web Apps functionality to SharePoint 2013, Lync Server 2013, and Exchange Server 2013.

Step 1: Create the Office Web Apps Server farm on the first server

The code in the following example creates a new Office Web Apps Server farm on the first server. The URL that you specify for –InternalURL is the FQDN name of the server that runs Office Web Apps Server, such as http://servername.contoso.com. The URL that you specify for –ExternalURL is the FQDN name that can be accessed on the Internet. The SSLOffloaded parameter enables offloading SSL termination to the load balancer. The –EditingEnabled parameter is optional and enables editing in Office Web Apps when it is used together with SharePoint 2013. The –EditingEnabled parameter is not used by Lync Server 2013 or Exchange Server 2013 because those hosts don’t support editing.

New-OfficeWebAppsFarm -InternalUrl "https://server.contoso.com" -ExternalUrl "https://wacweb01.contoso.com" -SSLOffloaded -EditingEnabled

Additional parameters that configure translation services, proxy servers, clipart support, and Online Viewers are described in New-OfficeWebAppsFarm. You can find additional information about how to obtain licenses that allow users to edit files by using Office Web Apps Server in Plan Office Web Apps (Used with SharePoint 2013). To learn about how these licenses are used in SharePoint Server 2013, see Configure licensing in SharePoint Server 2013.

noteNote:
If components of the .NET Framework 3.5 were installed and then removed, you might see “500 Web Service Exceptions” or “500.21 – Internal Server Error” messages when you run OfficeWebApps cmdlets. To fix this, run the following sample commands from an elevated command prompt to clean up settings that could prevent Office Web Apps Server from functioning correctly:

For Windows Server 2008 R2

%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
iisreset /restart /noforce

For Windows Server 2012

dism /online /enable-feature /featurename:IIS-ASPNET45

Step 2: Add more servers to the farm

After the first server is running Office Web Apps Server, run the following command on each server that you want to add to the Office Web Apps Server farm. The –MachineToJoin parameter adds the current server to an existing Office Web Apps Server farm, so use the computer name of one of the servers that’s already in the Office Web Apps Server farm.

New-OfficeWebAppsMachine –MachineToJoin "server1.contoso.com"

Want more information about these parameters? You can find them in New-OfficeWebAppsMachine.

Step 3: Verify that the Office Web Apps Server farm was created successfully

After the farm is created, details about the farm are displayed in the Windows PowerShell prompt. To verify that Office Web Apps Server is installed and configured correctly, use a web browser to access the Office Web Apps Server discovery URL, as shown in the following example. The discovery URL is composed of the value that you assigned to the InternalUrl parameter when you configured your Office Web Apps Server farm, and it is followed by /hosting/discovery.

https://server.contoso.com/hosting/discovery

If Office Web Apps Server works as expected, you should see a Web app Open Platform Interface (WOPI)-discovery XML file in your web browser. The first few lines of that file should resemble the following example:

<?xml version="1.0" encoding="UTF-8"?>
<wopi-discovery><net-zone name="internal-https"><app name="Excel" checkLicense="true" favIconUrl="https://officewebapps.contoso.com/x/_layouts/images/FavIcon_Excel.ico"><action name="view" urlsrc="https://officewebapps.contoso.com/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" default="true" ext="ods"/><action name="view" urlsrc="https://officewebapps.contoso.com/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" default="true" ext="xls"/><action name="view" urlsrc="https://officewebapps.contoso.com/x/_layouts/xlviewerinternal.aspx?<ui=UI_LLCC&><rs=DC_LLCC&>" default="true" ext="xlsb"/>
noteNote:
Depending on the security settings of your web browser, you might see a message that prompts you to select Show all content before the contents of the discovery XML file are displayed.

Posted in Office Web Apps 2013 | No Comments »

Leave a Reply