Windows
Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 have slightly
different prerequisites, so select the appropriate procedure below to install
the correct ones for your operating system.
On Windows Server 2008
R2
1.
Install the following software:
o
2.
Open the Windows PowerShell prompt as an administrator and run
these commands to install the required roles and services.
3. Import-Module ServerManager
Then, run this command:
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,NET-Framework,NET-Framework-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-Win-CFAC
If prompted, restart the
server.
On Windows Server 2012
1.
Open the Windows PowerShell prompt as an administrator and run
this command to install the required roles and services.
2. 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
If prompted, restart the
server.
On Windows Server 2012
R2
1.
Install the following software:
2.
Open the Windows PowerShell prompt as an administrator and run
this command to install the required roles and services.
3. 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
4.
If prompted, restart the
server.
Step 2: Install Office Web Apps
Server and related updates
Complete
these steps on any servers that will run Office Web Apps Server.
1.
Download Office Web Apps Server from the Volume
Licensing Service Center (VLSC). To download Office Web Apps Server
you must have a license, under a Volume Licensing agreement, for Office
Professional Plus 2013, Office Standard 2013, or Office for Mac 2011. The
download is located under those Office products on the VLSC portal.
2.
Do one of the following:
o
For Windows Server 2012 or Windows Server 2012 R2, open the .img
file directly and run Setup.exe.
o
For Windows Server 2008 R2 SP1, use a program that can mount or
extract .img files, then run Setup.exe.
3.
On the Read the
Microsoft Software License Terms page, select I accept the terms of this
agreement and
click 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 select Install Now. If
the folder you specified doesn’t exist, Setup creates it for you.
5.
When Setup finishes installing Office Web Apps Server, choose Close.
Step 3: Install language packs for
Office Web Apps Server
Office
Web Apps Server 2013 Language Packs let users view web-based Office files in
multiple languages, whether they’re opened from SharePoint 2013 document
libraries, Outlook Web Access (as attachment previews), and Lync 2013 (as
PowerPoint broadcasts). Learn more about how the language packs work in Planning language packs for Office Web Apps Server.
To
install the language packs, follow these steps.
2.
Run WebAppsServerLP_en-us_x64.exe.
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
agreementand select Continue.
4.
When Setup finishes installing Office Web Apps Server, choose Close.
Deploy the Office Web Apps Server
farm
Follow
the procedures in one of the following three sections, based on what kind of
Office Web Apps Server farm you want to create.
Deploy a single-server Office Web
Apps Server farm that uses HTTP
If
you’re only deploying Office Web Apps Server for testing or internal use, and
you don’t need to provide Office Web Apps Server functionality to Lync Server
2013, this procedure is for you. Here, you’ll install a single-server Office
Web Apps Server farm that uses HTTP. You won’t need a certificate or load
balancer, but you will need a dedicated physical server or virtual machine
instance that isn’t 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.
Figure:
The steps to deploy Office Web Apps Server
Step 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.
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.
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 the InternalUrl parameter you specified when you
configured your Office Web Apps Server farm, followed by /hosting/discovery, for
example:
http://servername/hosting/discovery
If
Office Web Apps Server is working as expected, you should see a Web Application
Open Platform Interface Protocol (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
For most
production environments, strongly recommend is using HTTPS for its security
features. Also, HTTPS is required if you want to provide Office Web Apps Server
functionality to Lync Server 2013, which lets users view PowerPoint broadcasts
in a browser. Here’s how to install a single-server Office Web Apps Server farm
that uses HTTPS. You'll need to install a certificate on the server as
described below.
Securing Office Web Apps Server
communications by using HTTPS
Office
Web Apps Server can communicate with SharePoint 2013, Lync Server 2013, and
Exchange Server 2013 by using the HTTPS protocol. In production environments,
we strongly recommend that you use HTTPS. You’ll have to install an Internet
Server certificate that can be assigned to the server that runs Office Web Apps
Server (if you are using a single server) or to the load balancer (if you are
using multiple servers that run Office Web Apps Server).
In
test environments that contain no user data, you can use HTTP for SharePoint
2013 and Exchange Server 2013 and skip the certificate requirement. Lync Server
2013 supports only HTTPS.
Certificates
used by Office Web Apps Server need to meet the following requirements:
·
The certificate must come from a trusted Certificate Authority
and include the fully qualified domain name (FQDN) of your Office Web Apps
Server farm in the SAN (Subject Alternative Name) field. (If the FQDN is not in
the SAN when you try to use the certificate, the browser will either show
security warnings or won’t process the response.)
·
The certificate must have an exportable private key. On
single-server farms, this option is selected by default when you use the
Internet Information Services (IIS) Manager snap-in to import the certificate.
·
The Friendly name field must be unique within the Trusted Root
Certificate Authorities store. If you have multiple certificates that share a
Friendly Name field, farm creation will fail because the New-OfficeWebAppsFarm
cmdlet won’t know which of those certificates to use.
·
The FQDN in the SAN field can’t begin with an asterisk (*).
·
Office Web Apps Server doesn’t require any special certificate
properties or extensions. For example, Client Enhanced Key Usage (EKU)
extensions or Server EKU extensions are not required.
·
On Windows Server 2012 or Windows Server 2012 R2, you must
install the "Allow HTTP Activation" Windows Communication Foundation
(WCF) feature.
The
certificate must be imported as follows:
·
For single-server farms You
must import the certificate directly on the server that runs Office Web Apps
Server. Don’t bind the certificate manually. The New-OfficeWebAppsFarm cmdlet
you run later will do this for you. If you bind the certificate manually, it’ll
be deleted every time the server restarts.
·
For load-balanced farms If
you’re offloading SSL, the certificate must be imported on the hardware load
balancer. If you’re not offloading SSL, you’ll need to install the certificate
on each server in the Office Web Apps Server farm.
This
Office Web Apps Server farm will provide Office Web Apps functionality to
SharePoint 2013, Lync Server 2013, and Exchange Server 2013.
Figure:
The steps to deploy Office Web Apps Server
Step 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.
New-OfficeWebAppsFarm -InternalUrl "https://server.contoso.com" -ExternalUrl "https://wacweb01.contoso.com" -CertificateName "OfficeWebApps Certificate" –EditingEnabled
Parameters
·
–InternalURL is the fully qualified domain name (FQDN)
of the server that runs Office Web Apps Server, such as http://servername.contoso.com.
·
–ExternalURL is the FQDN that can be accessed on the
Internet.
·
–CertificateName is the friendly name of the certificate.
·
–EditingEnabled is optional and 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.
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 the InternalUrl parameter you specified when you
configured your Office Web Apps Server farm, followed by /hosting/discovery, for
example:
https://server.contoso.com/hosting/discovery
If
Office Web Apps Server works as expected, you should see a Web Application Open
Platform Interface Protocol (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"
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
If you
anticipate lots of traffic to your Office Web Apps Server farm, and you want it
to be available over the Internet as well as on your internal network, this
type of topology is the way to go. This section shows how to install a
multi-server Office Web Apps Server farm that uses a load balancer and HTTPS.
If you’re interested
Before
you begin, make sure your load balancer is configured as described in Load balancer requirements for Office Web Apps Server.
Also, you'll need to install a certificate on the load balancer as described. This
Office Web Apps Server farm will provide Office Web Apps functionality to
SharePoint 2013, Lync Server 2013, and Exchange Server 2013.
Figure:
The steps to deploy Office Web Apps Server
Step 1: Create the Office Web Apps
Server farm on the first server
Use
the New-OfficeWebAppsFarm command to create a new Office Web Apps
Server farm on the first server, as shown in the following example.
New-OfficeWebAppsFarm -InternalUrl "https://server.contoso.com" -ExternalUrl "https://wacweb01.contoso.com" -SSLOffloaded –EditingEnabled
Parameters
·
–InternalURL is the fully qualified domain name (FQDN)
of the server that runs Office Web Apps Server, such as http://servername.contoso.com.
·
–ExternalURL is the FQDN name that can be accessed on
the Internet.
·
-SSLOffloaded enables offloading SSL termination to the
load balancer.
·
–EditingEnabled is optional and 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.
Step 2: Add more servers to the farm
After
the first server is running Office Web Apps Server, run the New-OfficeWebAppsMachine command on each server you want to add to
the Office Web Apps Server farm. For the –MachineToJoin parameter, use the computer name of a
server that's already in the Office Web Apps Server farm. For example, if
server1.contoso.com is already in the farm, use the following:
New-OfficeWebAppsMachine -MachineToJoin "server1.contoso.com"
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 the InternalUrl parameter you specified when you
configured your Office Web Apps Server farm, followed by /hosting/discovery. For
example:
https://server.contoso.com/hosting/discovery
If
Office Web Apps Server works as expected, you should see a Web Application Open
Platform Interface Protocol (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"/>
Step 4: 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.
If
features 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 or Windows Server 2012 R2
dism /online /enable-feature /featurename:IIS-ASPNET45
