What about SharePoint: Configuring Office Web Apps for SharePoint 2013

http://technet.microsoft.com/en-us/library/jj219455.aspx#prerequisites or watch the video on: http://technet.microsoft.com/en-us/library/ff431685.aspx#BKMK_Video

On the server that runs Office Web Apps Server;

Step 1: Install prerequisite software for Office Web Apps Server

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:
o Windows Server 2008 R2 Service Pack 1
o .NET Framework 4.5
o Windows PowerShell 3.0
o KB2592525
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

· 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:
o For Windows Server 2012, open the .img file directly and run Setup.exe (double-click it).
o 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 selectContinue.
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

Step 3: Create the Office Web Apps Server farm

Step 3a: 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.

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.

note

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:

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 3b: 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.

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

%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 4: 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"

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..

Step 5: Configure SharePoint 2013 to use Office Web Apps

To configure SharePoint 2013 to use Office Web Apps Server, you must run one or more Windows PowerShell cmdlets from SharePoint 2013. After you run the necessary cmdlets, users can open Office files from SharePoint 2013 document libraries in a browser.

Prepare to configure SharePoint 2013 to use Office Web Apps Server

Certain conditions must be met before you can successfully configure SharePoint 2013 to use Office Web Apps Server. Review the following requirements before you continue.

Verify that all SharePoint 2013 web applications use claims-based authentication. Office Web Apps rendering and editing will not work on SharePoint 2013 web applications that use classic mode authentication. Learn more in SharePoint authentication requirements for Office Web Apps.
To enable users to edit (not just read) Office documents in a web browser, verify that you have the necessary editing licenses and that you have enabled editing on the Office Web Apps Server farm. You can learn more about licensing requirements in Licensing Office Web Apps for editing Office files.
If you log into SharePoint 2013 by using the System Account, you will be unable to test the connection between SharePoint 2013 and Office Web Apps Server. You will have to log on by using a different account to test the connection.
Low memory conditions can cause Office document previews to fail in Office Web Apps. Verify that the server or servers that run Office Web Apps Server have sufficient memory by reviewing the Hardware requirements—web servers, application servers, and single server installations for SharePoint 2013, which are the same requirements that Office Web Apps Server uses.

Configure SharePoint 2013 to use Office Web Apps Server by using HTTPS

Before you start the following procedures, make sure that you have set up Office Web Apps Server by following the steps in Deploy a single-server Office Web Apps Server farm that uses HTTPS or Deploy a multi-server, load-balanced Office Web Apps Server farm that uses HTTPS .
On the server that runs SharePoint 2013

Step 1: Open the SharePoint 2013 Management Shell

Choose the procedure that corresponds to your server operating system.

To open an elevated SharePoint 2013 Management Shell in Windows Server 2008 R2

On the Start menu, choose All Programs.
Choose Microsoft SharePoint 2013 Products.
Choose (right-click) SharePoint 2013 Management Shell to display the shortcut menu.
In the shortcut menu, choose Run as administrator.

To open an elevated SharePoint 2013 Management Shell in Windows Server 2012

Swipe in from the edge of the screen to show the charms and then choose Search to see all the applications that are installed on the computer.
Choose (right-click) SharePoint 2013 Management Shell to display the app bar.
In the app bar, choose Run as administrator.

Step 2: Create the binding between SharePoint 2013 and Office Web Apps Server

Run the following command, where <WacServerName> is the FQDN of the URL that you set for the internal URL. This is the point of entry for Office Web Apps Server traffic.

New-SPWOPIBinding -ServerName <WacServerName>

Need help? See New-SPWOPIBinding.

Step 3: View the WOPI zone of SharePoint 2013

Office Web Apps Server uses the concept of zones to determine which URL (internal or external) and which protocol (HTTP or HTTPS) to use when it communicates with the host, which in this case is SharePoint 2013. By default, SharePoint Server 2013 uses the internal-https zone. Verify that this is the current zone by running the following command:

Get-SPWOPIZone

After you run this command, you should see the WOPI zone displayed. Take note of the WOPI zone that is displayed.

Need help? See Get-SPWOPIZone.

Step 4: Change the WOPI zone if it is necessary

Depending on your environment, you might have to change the WOPI zone. If you have a SharePoint farm that's internal and external, specify external. If you have a SharePoint farm that's internal only, specify internal.
If the results from Step 3 show internal-https and the SharePoint farm is internal only, you can skip this step. If you have a SharePoint farm that’s internal and external, you must run the following command to change the zone to external-https.

Set-SPWOPIZone –zone “external-https”

Need help? See Set-SPWOPIZone.

Step 5: Verify that Office Web Apps is working

In SharePoint 2013, make sure that you are not logged in as System Account. (Whenever the currently logged on user name appears as sharepoint\system, that user can’t edit or view the documents by using Office Web Apps.) Go to a SharePoint 2013 document library that contains Office documents and view a Word, PowerPoint, Excel, or OneNote file. The document should open in a browser that displays the file by using Office Web Apps.

What about SharePoint

Tuesday, March 26, 2013

Configuring Office Web Apps for SharePoint 2013