MS UC 2013-1-Deploy Office Web Apps Server 2013

本文涉及的产品
云数据库 Redis 版,社区版 2GB
推荐场景:
搭建游戏排行榜
简介:
MS UC 2013-1-Deploy Office Web Apps Server 2013
《MS UC 2013 -系列》博文:
1) 以TechNet Library为技术资料原型。
2) 以0-《统一沟通-微软-实战》为基础。
3) 以1-《统一沟通-微软-技巧》为参照。
4) 以整个测试过程中图片为样板,再次标准化了操作流程,你看多了就会知道。
5) 不论你喜欢与不喜欢?
6) 不论你说啥!
7) 它都出现了!...它也将在你想不到的时间消失,因为有更好计划在实施中。
8) 目的:为了让大家更容易看懂TechNet Library,更容易看懂微软!
2 out of 3 rated this helpful -  Rate this topic
Updated: August 06, 2012
This documentation is preliminary and subject to change.
Summary: Deploy Office Web Apps Server Preview on-premises for use by SharePoint 2013 Preview, Lync Server 2013 Preview, and Exchange Server 2013 Preview.
Applies to: Office Web Apps Server Preview 
Audience: IT Professionals
To deploy Office Web Apps Server Preview, you install prerequisite software, server roles, services, and features, and then install Office Web Apps Server Preview. Next, you use Windows PowerShell to configure the Office Web Apps Server farm.
In this article:
Before you begin
We recommend that you review the requirements and guidelines that are described in  Plan Office Web Apps Server Preview  before you continue. We also recommend that you start with a fresh installation of Windows Server 2008 R2 Service Pack 1 or Windows Server 2012. A newly installed server, whether a physical server or virtual machine instance, reduces the possibility of configuration issues that are caused by earlier builds of Office Web Apps Server Preview.
clip_image001 Note:
You can complete tasks in this article by using a mouse, keyboard shortcuts, or touch. For more information, see the following resources:
Prepare servers to run Office Web Apps Server Preview
Perform the following procedures on all servers to run Office Web Apps Server Preview.
Step 1: Install prerequisite software for Office Web Apps Server Preview
Windows Server 2008 R2 and Windows Server 2012 have slightly different prerequisites. Be sure to install the correct prerequisites for your operating system.
To prepare a server that runs Windows Server 2008 R2
1. Install the following software:
Windows Server 2008 R2 Service Pack 1  and all required updates
clip_image003
clip_image005
clip_image007
clip_image009
KB2592525
clip_image011
2. Next, open the Windows PowerShell prompt as an administrator and run the following sample commands to install the required roles and services.
For Windows Server 2008 R2
Import-Module ServerManager
clip_image012
And then run:
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
clip_image014
To prepare a server that runs Windows Server 2012
  • Open the Windows PowerShell prompt as an administrator and run the following sample commands to install the required roles and services.
For Windows Server 2012
Import-Module ServerManager
And then run:
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
Step 2: Install Office Web Apps Server Preview
Complete the following steps on all servers that will run Office Web Apps Server Preview.
To install Office Web Apps Server Preview
1. Download Office Web Apps Server Preview from the  Microsoft Download Center .
2. In the Office Web Apps Server download package, Run Setup.exe (double-click it).
clip_image016
3. In the Office Web Apps Server Setup Wizard, on the Read the Microsoft Software License Terms page, select I accept the terms of this agreement and then select Continue.
clip_image018
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.
clip_image020
5. When Setup finishes installing Office Web Apps Server, choose Close
clip_image022
clip_image024
Step 3: Configure Windows PowerShell and import the OfficeWebApps module
You’ll have to import the Office Web Application module into Windows PowerShell for all servers that will run Office Web Apps Server Preview. To do so, open the Windows PowerShell prompt as an administrator, type the following command, and then press ENTER.
Import-Module OfficeWebApps
clip_image025
The Import-Module loads the Office Web Server cmdlets into your instance of Windows PowerShell. To verify that the cmdlets were loaded, type the following command at the PowerShell prompt and then press ENTER:
Get-Command "*Office*"
clip_image027
A list of all cmdlets in the OfficeWebApps module is displayed. To get help with any of the cmdlets, type the following command:
Get-Help cmdletname
clip_image029
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 Preview functionality to SharePoint 2013 Preview and Exchange Server 2013 Preview, 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 Preview, 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 Preview, such as http://servername. The –AllowHttp parameter configures the farm to use HTTP, and the –EditingEnabled parameter enables editing in Office Web Apps Preview when it is used together with SharePoint 2013 Preview.
New-OfficeWebAppsFarm –InternalURL http://servername –AllowHttp -EditingEnabled
Want more information about these parameters? You can find them 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 Preview in  Plan Office Web Apps Preview (Used with SharePoint 2013 Preview Products) . To learn about how these licenses are used in SharePoint Server 2013 Preview, see  Configure licensing in SharePoint Server 2013 Preview .
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 Preview is installed and configured correctly, use a web browser to access the Office Web Apps Server Preview 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 Preview 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&>" />
clip_image001[1] Note:
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:
%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
iisreset /restart /noforce
Step 3: Configure the host
The farm is now ready to provide Office Web Apps Preview 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 Preview communications by using HTTPS  . You can use this Office Web Apps Server farm to provide Office Web Apps Preview functionality to SharePoint 2013 Preview, Lync Server 2013 Preview, and Exchange Server 2013 Preview.
Request a Certificate:
clip_image031
clip_image033
clip_image035
clip_image036
clip_image037
clip_image038
clip_image040
clip_image041
clip_image042
clip_image044
clip_image046
clip_image048
clip_image050
clip_image052
clip_image053
clip_image055
clip_image056
clip_image058
clip_image059
clip_image061
clip_image062
clip_image064
clip_image066
clip_image067
clip_image068
clip_image070
clip_image072
clip_image074
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 Preview, 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 Preview when it is used together with SharePoint 2013 Preview.
New-OfficeWebAppsFarm -InternalUrl "https://server.contoso.com" -ExternalUrl "https://wacweb01.contoso.com" –CertificateName "OfficeWebApps Certificate" –EditingEnabled
New-OfficeWebAppsFarm -InternalUrl "https://WebApps-2013.uc-cn.net" -ExternalUrl "https://WebApps-2013.uc-cn.net" -CertificateName "WebApps-2013.uc-cn.net" –EditingEnabled
clip_image076
clip_image078
Want more information about these parameters? You can find them in  New-OfficeWebAppsFarm .
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 Preview is installed and configured correctly, use a web browser to access the Office Web Apps Server Preview 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.
clip_image080
If Office Web Apps Server Preview 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"?>
@namespace html url(http://www.w3.org/1999/xhtml); :root { font:small Verdana; font-weight: bold; padding: 2em; padding-left:4em; } * { display: block; padding-left: 2em; } html|style { display: none; } html|span, html|a { padding: 0; font-weight: normal; text-decoration: none; } html|span.block { display: block; } *[html|hidden], span.block[html|hidden] { display: none; } .expand { display: block; } .expand:before { content: '+'; color: red; position: absolute; left: -1em; } .collapse { display: block; } .collapse:before { content: '-'; color: red; position: absolute; left:-1em; } <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"
clip_image001[2] Note:
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..
clip_image001[3] Note:
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:
%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –iru
clip_image082
iisreset /restart /noforce
clip_image084
clip_image086
Step 3: Configure the host
The farm is now ready to provide Office Web Apps Preview 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 Preview , and you must have a certificate installed on the load balancer as described in  Securing Office Web Apps Server Preview communications by using HTTPS  . You can use this Office Web Apps Server farm to provide Office Web Apps Preview functionality to SharePoint 2013 Preview, Lync Server 2013 Preview, and Exchange Server 2013 Preview.
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 Preview, 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 Preview when it is used together with SharePoint 2013 Preview.
New-OfficeWebAppsFarm -InternalUrl "https://server.contoso.com" -ExternalUrl "https://wacweb01.contoso.com" -SSLOffloaded -EditingEnabled
Want more information about these parameters? You can find them in  New-OfficeWebAppsFarm .
Step 2: Add more servers to the farm
After the first server is running Office Web Apps Server Preview, run the following command on the other servers to add them to the farm:
New-OfficeWebAppsMachine –MachineToJoin <nameofmachinetojoin>
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 Preview is installed and configured correctly, use a web browser to access the Office Web Apps Server Preview 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 Preview 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"/>
clip_image001[4] Note:
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.
clip_image001[5] Note:
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:
%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
iisreset /restart /noforce
Step 4: Configure the host
The farm is now ready to provide Office Web Apps Preview functionality to hosts over HTTPS. Visit the following articles for more information about how to configure hosts.
Change History
Date
Description
August 06, 2012
Added two new sections: Deploy a single-server Office Web Apps Server farm that uses HTTPS and Deploy a multi-server, load-balanced Office Web Apps Server farm that uses HTTPS.
July 16, 2012
Initial publication




本文转自 CTO_LiuJinFeng 51CTO博客,原文链接:http://blog.51cto.com/dynamic/1071548,如需转载请自行联系原作者

目录
相关文章
|
25天前
|
IDE Linux 开发工具
如何在Linux运行RStudio Server并实现Web浏览器远程访问
如何在Linux运行RStudio Server并实现Web浏览器远程访问
37 0
|
1月前
|
算法 前端开发 JavaScript
什么是 Web 开发的 Server Side Model
什么是 Web 开发的 Server Side Model
19 0
|
22天前
|
应用服务中间件 nginx
【报错】Failed to start A high performance web server and a reverse proxy server.
【报错】Failed to start A high performance web server and a reverse proxy server.
|
1月前
|
Linux
【web server】基于升序链表的定时器
【web server】基于升序链表的定时器
|
1月前
|
XML C++ 数据格式
C++使用gSoap写Web Server和Web Client
C++使用gSoap写Web Server和Web Client
17 1
|
1月前
【web server】HTTP协议如何解析or封装
【web server】HTTP协议如何解析or封装
|
1月前
|
Java
【web server】整体流程解析
【web server】整体流程解析
|
1月前
|
消息中间件
【web server】日志系统
【web server】日志系统
|
1月前
|
C语言
【web server】项目中的一些小点
【web server】项目中的一些小点
|
1月前
|
应用服务中间件
Web开发:关于Tomcat出现The origin server did not find a current representation for the target resourc...的问题
Web开发:关于Tomcat出现The origin server did not find a current representation for the target resourc...的问题

相关产品

  • 云迁移中心