Deploy Office Web Apps Server
Deploying Office Web Apps Server involves installing some prerequisite software and running a few
Windows PowerShell commands, but overall the process is designed to be pretty
straightforward. This article walks you through the procedures to get your
servers ready, then gives you the Windows PowerShell commands to configure the
Office Web Apps Server farm.
Perform these
procedures on all servers that will run Office Web Apps Server.
Figure: The steps to
prepare servers for Office Web Apps Server
Windows Server 2008 R2
and Windows Server 2012 have slightly different prerequisites, so select the appropriate
procedure below to install the correct ones for your operating system.
- Install the following software:
1. Open the Windows PowerShell prompt as an
administrator and run these commands to install the required roles and
services.
Import-Module
ServerManager
Then, run these commands:
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 prompted, restart the server.
Complete these steps
on any servers that will run Office Web Apps Server.
- Download Office Web Apps Server from the Microsoft
Download Center.
- Do one of the following:
- For Windows Server 2012, open the .img file directly
and run Setup.exe.
- For Windows Server 2008 R2 SP1, use a program that can
mount or extract .img files, then run Setup.exe.
- On the Read the Microsoft Software License
Terms page, select I accept the terms of this agreement and
click Continue.
- 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.
- When Setup finishes installing Office Web Apps Server,
choose Close.
- 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.
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.
in Planning
language packs for Office Web Apps Server.
To install the
language packs, follow these steps.
- Download the Office Web Apps Server Language Packs from
the Microsoft
Download Center.
- Run WebAppsServerLP_en-us_x64.exe.
- 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
select Continue.
- When Setup finishes installing Office Web Apps Server,
choose Close.
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
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
For
HTTP and HTTPS
New-OfficeWebAppsFarm -InternalUrl
"https://server.contoso.com" -ExternalUrl
"https://wacweb01.contoso.com" -CertificateName "OfficeWebApps
Certificate" -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.
Additional parameters
that configure translation services, proxy servers, ClipArt support, and Online
Viewers are described in New-OfficeWebAppsFarm.
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.
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.
- Configure
Office Web Apps for SharePoint 2013
- Office
Web Apps Server Integration (Exchange Server 2013)
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
dism /online
/enable-feature /featurename:IIS-ASPNET45
Choose one of the
following sections depending on whether you want to use HTTP or HTTPS. HTTP is
generally recommended only for test environments. In production environments,
the more secure HTTPS protocol is the better choice.
Run the following
command, where <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.
New-SPWOPIBinding
-ServerName <WacServerName> -AllowHTTP
After running this
command, you should see a list of bindings displayed at the Windows PowerShell
command prompt.
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.
Run the following command to see what your current zone is.
Get-SPWOPIZone
The WOPI zone
displayed by this command should be internal-http. If it’s displayed
correctly, skip to step 5. If it isn’t, see the next step.
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.
Set-SPWOPIZone –zone
“internal-http”
If you have a SharePoint farm that’s
internal and external, you need to run the following command to change the zone
to external-https.
Set-SPWOPIZone –zone
“external-https”
Verify that the new
zone is internal-http by running Get-SPWOPIZone again.
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 following commands 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
Verify the documents with office web app features
No comments:
Post a Comment