Deploying Office Web Apps Server 2013

to deploy Office Web appsserver 2013 in a test environment, you install the prerequisite software, server roles, services, and features, and then you install Office Web Apps Server 2013. Next, you can use Windows PowerShell to create a single-server office Web Apps server farm.

Before you start

We recommend that you review the requirements and guidelines that are described in office Web Apps Server 2013 before you continue. We also recommend that you start a fresh installation of WINDOWSSERVER2008R2 Service Pack 1 or WindowsServer2012. Whether a physical server or virtual machine instance on a newly installed server reduces the likelihood of a configuration issue that is caused by an earlier version of Office Web Apps Server 2013. Even if you remove the existing Office Web Appserver Farm and uninstall the previous version of Office Web Apps Server 2013, when you install the new version, you may still have a problem if you do not start with a newly installed server.

Single-server Office WEB Apps server farm deployed in a test environment

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

The environment can be accessed only by internal users. The configuration does not have an external URL. The environment cannot be used with Lync Server 2013, which requires HTTPS.

Other deployment scenarios, such as those that use HTTPS, load balancing, and internal and external URLs, will provide updates to this article in the future.

1th Step: Prepare a test server to run Office Web appsserver 2013

1. Install the software prerequisites for Office Web Apps Server 2013

2. Install Office Web Apps Server 2013

3. Configure the Windows Power Shell and import the Office Web Apps module

Step 2: Create an 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 name of the server that is running Office Web Apps Server 2013, such as http://ServerName. The –allowhttp parameter configures the farm to use HTTP, and the –editingenabled parameter to make SharePoint 2013 and use it when editing in office Web Apps.

New-officewebappsfarm-internalurl http://wac–allowhttp–editingenabled

New-officewebappsfarm–verbose-internalurl http://wac–editingenabled–allowhttp

3rd Step: Verify that the office Web Apps Server Farm was created successfully

After the farm is created, the Windowspower Shell hints show detailed information about the farm. To verify that Office Web Apps Server 2013 is installed and configured correctly, use a Web browser to access the URL for Office Web Apps Server 2013 discovery, as shown in the following example. When you configure your office Web Apps Server Farm, it follows the discovery URL that is composed of the values that are assigned to the InternalUrl parameter/hosting/discovery.

Http://servername/hosting/discovery

If Office Web Apps Server 2013 will work as expected, you should see a web App open platform Connection (WOPI)-an XML file found in your Web browser. The first few lines of the file should resemble the following example:

-

-

-

Attention:

If the component. NETFramework3.5 is installed, and then removed, when you run the Office Web Apps cmdlet, you may see a "Web Service exception" 500.21--Internal server error message. To resolve this issue, clean the settings from the elevated command prompt to prevent Office Web Apps Server from running the following sample command:

%systemroot%\microsoft.net\framework64\v4.0.30319\aspnet_regiis.exe-iru

Iisreset/restart/noforce

Step 4: Configure the Host

Now ready for the host to provide Office Web Apps functionality via HTTP on the farm. Tasks: Reference

These programs are referenced in the deployment scenario described earlier in this article. For deployment scenarios to ensure that your server is configured correctly, see.

Install the software prerequisites for Office Web Apps Server 2013

Perform the following steps on all servers that you want to run Office Web Apps Server 2013

The server that is ready to run WINDOWSSERVER2008R2 has the following software installed: WINDOWSSERVER2008R2 Service 1 Pack and all required updates. NET Framework 4.5 rc Windows Power Shell 3.0 Next, open the Windows Power Shell prompt as an administrator, and run the following example command to install the required roles and services.

To WINDOWSSERVER2008R2

Import-module Servermanager

And then run:

Add-windowsfeatureweb-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

Prepare the server running WindowsServer2012 you need to import the Windows Power Shell's Office Web application module on the server running Office Web Apps server. To do this, open the Windows Power Shell prompt as an administrator, type the following command, and then press ENTER.

To WindowsServer2012

Import-module Servermanager

And then run:

Add-windowsfeatureweb-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

And then run:

Import-module Officewebapps

The import module loads Officewebservercmdlet into an instance of your Windows PowerShell. To verify that you have loaded the Cmdlet,powershell prompt, type the following command, and then press ENTER:

Get-command "*office*"

A list of all cmdlets in the Office Web Apps module is displayed. To get any help with the cmdlet, type the following command:

Get-help Cmdletname

Set Openfromurl to True

Set-officewebappsfarmopenfromurlenabled

This article is from the "Yun Hao Technology" blog, please be sure to keep this source http://yunhao.blog.51cto.com/8544825/1761911

Deploying Office Web Apps Server 2013