r10oww.netlify.com

The requirement for Office web Server was introduced in Lync Server 2013 to support the use of PowerPoint presentations in Lync Online Meetings. Without Office Web App Server (Formerly known as Office Web App companion server - WAC) users using Lync 2013 Client connected to Lync 2013 Servers won’t be able to do PowerPoint sharing.

1. Office Web Apps Server 2013 Prerequisites
2. Office Web Apps Server 2013 Cu
3. Office Web Apps Server 2013 Latest Update

The purpose of this post is to show step by step Installation and Configuration of Office Web App Server and its Integration with Lync Server 2013.

There are lot of blogs and articles on this, right from how to install Office Web App Server till integrating with Lync Server 2013, but I thought I would simplify each configurations step by step with screenshots so that even a beginner would be able to configure this and get it working just by following the steps.

The requirement for Office web Server was introduced in Lync Server 2013 to support the use of PowerPoint presentations in Lync Online Meetings. Without Office Web App Server (Formerly known as Office Web App companion server – WAC) users using Lync 2013 Client connected to Lync 2013 Servers won’t be able to do PowerPoint sharing. Microsoft Office Web Apps Server Service Pack 1 (SP1) provides the latest updates for Office Web Apps Server. This service pack includes two kinds of fixes: Previously unreleased fixes that are included in this service pack. In addition to general product fixes, these fixes include improvements to stability, performance, and security. Office web apps server 2013 allows us to view and edit office documents (Word, Excel, PowerPoint and OneNote) directly in browser without needing Microsoft Office installed on Client machine. OWA is considered as LITE version of Microsoft Office Client.

There are multiple things involved in making Lync server to be able to use Office Web App Server to provide PowerPoint sharing feature for Lync 2013 clients, if we divide those into simpler steps, below are the step by step configuration procedure.

1. Installing Office Web App Server 2013 Application.

2. Generating Certificate for office web app server.

3. Creating Office Web App Server farm.

4. Integrating Office Web App Server with Lync Server 2013.

In this article we are going to use a simple lab setup with single Office Web App Server and Lync Standard Edition Server as shown below:

Without much ado, Let’s get started!

1. Installing Office Web App Server 2013:

Before running setup, we need to Install Prerequisites on machine with supported operating system for Office Web Server 2013.

(you can refer here for information on supported Operating system and additional software required)

Install bellow additional software which are prerequisites for Installation of Office Web App Server.

Installation of Office Web Server Application is straight forward, Run Setup file and follow below steps to complete the installation.

At this point we have completed the installation of Office Web App Server.

2. Generate Certificate for use in Office Web App Server

Next step is to get a valid certificate generated so that it can be used with Office Web App Server farm, there are different ways to generate the certificate, directly from certification Authority, using different applications and etc, however simpler way is to use IIS which was installed as one of the prerequisites earlier.

We will use one of the Web Server component called ‘Server Certificates’ to generate the certificate request, below are the steps:

From the Office Wep App Server Launch IIS Manager -> Select the Server name -> in features pane, select ‘Server Certificates’

Select ‘Create Certificate Request’ from Actions page.

Fill in the details, Common name is nothing but the Actual URL you are going to use for Office web app server (Issued to name)

Select RSA and you can Select either 1024 or 2048 for Bit Length

Now we have certificate Request file like below.

Now that we have generated certificate request, we could proceed with getting issued by an internal certification authority or you can go for public Certificate, Decision is purely based on whether you want users to access WAC Internally only or from external machine as well.

If we are to allow Ppt sharing with external folks or federated contacts or from different machines that doesn't contain Internal Root CA Certificate, it’s good to go for third party certificate as its by default trusted on most of the machines.

In our scenario, we are going to use internal Certification Authority to issue the certificate.

To Issue the Certificate, Go to Certification authority Certsrv Webpage using http://Dc.contoso.com/certsrv or https://Dc.contoso.com/Certsrv -> Select 'Request a Certificate' option.

Select 'Advanced Certificate Request'

Select 'Submit a certificate request by using base-64-encoded cmc' as we already have request file.

Copy the content of Certificate request file generated earlier using IIS and pasted it in the box as shown below -> Select 'Web Server' Template -> Click on Submit

On successful issue of certificate we would get below option to download the certificate; Select Base 64 Encoded -> download Certificate.

Now that we have certificate issued, we can go ahead and install it on Office Web App Server.

To do that, Load Certificate console start -> run -> mmc -> Add/Remove Snap in -> Certificates -> Add -> Computer Account -> Local Computer -> Finish -> OK

Go to personal store as shown below and import the certificate that we just got.

We are not done yet, just one last step. By Default certificate created using above method will not have the friendly name, however we would need Friendly name to be present which will later be used to associate this certificate with Office Web App Server.

Select the certificate -> Go to properties

Add a Valid Friendly Name (just a name for later use) -> click Apply -> OK

Now we have the valid Certificate Ready to be used for Office Web App Server Application.

3. Create new Office Web App Server Farm:

Installation of Office Web App Server itself isn’t sufficient for it to be functional it only installed the bits and components of Office web app server, Further we need to create a Office Web App Server Farm and associate certificate.

Using Windows PowerShell, we can run below command to create the Office Web App Server Farm:

New-OfficeWebAppsFarm -InternalUrl Https://wac.Contoso.com -ExternalUrl Https://Wac.Contoso.com -CertificateName WacCert -AllowHttp

In the above command, wac.contoso.com would be the Office Web App URL that we will be using (using same for internal and external, however this can be changed as per requirement)

InternalURL Refers to URL that will be used by Lync 2013 Clients connected to Lync server internally.

ExternalURL Refers to URL that will be used by Lync 2013 Clients connected to Lync server Externally.

CertificateName is set to ‘WacCert’ which is the friendly name of the certificate that we created earlier.

Verify if Office Web App Server Farm is functional by browsing the discovery URL Https://Wac.Contoso.com/Hosting/Discovery , we should get below response.

At the end of this step, we have installed office web app server, created a Office Web App Server Farm and have associated valid certificate that was created earlier, Office Web App Server is now Ready.

4. Integrating Office Web App Server with Lync 2013 Server

Now we are in the last step of this article. To Integrate Office Web App Server with Lync 2013 Server perform below steps:

Use Topology Builder and Define New Office Web App Server as below:

Associate Front End Pool with Office Web App Server by performing below actions:

Office Web Apps Server 2013 Prerequisites

Using Topology Builder -> Select FE Pool -> Edit Properties -> Select the checkbox ‘Associate pool with Office Web App Server’ -> dropdown and select WAC Server -> Publish Topology

To confirm the successful office Web App Server Integration, Monitor the Lync Server Application Log to see below Entry, this Even suggests that Lync Server has discovered the Office Web App Server URLs.

Now that we have installed and configured Office Web App Server and also integrated with Lync server 2013, Lync 2013 clients can make use of this to use PowerPoint sharing feature.

Hope the above information helps!

Pragathi Raj S

Support Engineer – Microsoft iGTSC

PS : In my Next Blog I am going to write on Troubleshooting Office Web App Server Integration with Lync Server 2013.

Applies to: Office Web Apps Server

Summary: Explains how to deploy Office Web Apps Server on-premises for use by SharePoint 2013 and Lync Server 2013.

Audience: IT Professionals

Note that this article covers installing Office Web Apps Server for your business. If you're looking for help with your personal copy of Office or Office Web Apps, see https://support.office.com.

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.

In this article:

• Watch a video to see how it’s done

• Review these resources before you begin

• Prepare servers to run Office Web Apps Server

• Deploy the Office Web Apps Server farm

  Software for flashing android phones. Apr 23, 2018  This software program is the latest version to root your android mobile phones pattern lock. Android flashing latest software is released and here we share the direct download link to free download without waiting. The latest version of android flashing software has been given here to free download. If you were looking a strong tool for mobile. Cell phone flashing software free download - Cell Phone Video Converter, Flashing Phone Premium, Cell Phone Image Converter, and many more programs. Some chinse old mobile phones got the compatibility issue with the tool, because of their Old Android versions. If you are interested in Flashing of your mobile phone, tap the Flash button, it will restart several times, while flashing, you just bear with and wait sometimes. Android Flash tool can also be used to remove the lock of your phone.

• If you see “500 Web Service Exceptions” or “500.21 – Internal Server Error” messages

Watch a video to see how it’s done

Watch the following video to see how to set up Office Web Apps Server in a test environment. You’ll also see a preview of how to configure SharePoint 2013 to use Office Web Apps Server.

Set up Office Web Apps Server in a test environment

Review these resources before you begin

Make sure you’ve taken a look at these resources before getting started:

• For details about hardware and software requirements, take a look at the planning guidelines.

• By default, Office Web Apps Server lets you view Office files but not edit them. To edit files, you'll need an editing license, which you can learn about in Plan Office Web Apps (Used with SharePoint 2013) and Configure licensing in SharePoint Server 2013.

Note

You can complete tasks in all Office 2013 suites by using a mouse, keyboard shortcuts, or touch. For information about how to use keyboard shortcuts and touch with Office products and services, see Keyboard shortcuts and Office Touch Guide.

Prepare servers to run Office Web Apps Server

Perform these procedures on all servers that will run Office Web Apps Server.

Figure: The steps to prepare servers for Office Web Apps Server

Step 1: Install prerequisite software for Office Web Apps Server

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:

2. Open the Windows PowerShell prompt as an administrator and run these commands to install the required roles and services.

   Then, run this command:

   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.

   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.

   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.

Office Web Apps Server 2013 Cu

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:

   • For Windows Server 2012 or Windows Server 2012 R2, 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.

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 FilesMicrosoft Office Web Apps) and select Install Now. If the folder you specified doesn’t exist, Setup creates it for you.

   We recommend that you install Office Web Apps Server on the system drive.

5. When Setup finishes installing Office Web Apps Server, choose Close.

6. Download and install Office Web Apps Server SP1 (Recommended for Windows Server 2012 and Windows Server 2008 R2 SP1. Required for Windows Server 2012 R2.)

   Note

   If you are applying Office Web Apps Server SP1 at a later time, follow the directions in Apply software updates to Office Web Apps Server.

7. Check for the most current Office Web Apps Server updates by reviewing the list on the TechNet Update center for Office, Office servers, and related products.

   Note

   If you did not install Office Web Apps Server SP1, apply KB2810007.

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.

1. Download the Office Web Apps Server Language Packs from the Microsoft Download Center.

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 agreement and select Continue.

4. When Setup finishes installing Office Web Apps Server, choose Close.

Important

• To install language packs after the Office Web Apps Server farm is created, you must remove a server from the farm, install the language pack on it, and then add the server back to the farm.

• For a language pack to work correctly, you’ll need to install it on all servers in the farm.

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.

Tip

If Windows PowerShell doesn’t recognize the New-OfficeWebAppsFarm cmdlet when you run it, you may need to import the OfficeWebApps module. Use this command:
Import-Module -Name OfficeWebApps

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.

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.

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 because that host doesn't support editing.

Additional parameters that configure translation services, proxy servers, ClipArt support, and Online Viewers are described in New-OfficeWebAppsFarm.

If you see “500 Web Service Exceptions” or “500.21 – Internal Server Error” messages

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:

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.

Step 3: Configure the host

The farm is now ready to provide Office Web Apps functionality to hosts over HTTP. Visit Configure Office Web Apps for SharePoint 2013 for more information about how to configure hosts.

Deploy a single-server Office Web Apps Server farm that uses HTTPS

For most production environments, we strongly recommend the use of 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 in Securing Office Web Apps Server communications by using HTTPS.

This Office Web Apps Server farm will provide Office Web Apps functionality to SharePoint 2013 and Lync 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.

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 because that host doesn't support editing.

Additional parameters that configure translation services, proxy servers, ClipArt support, and Online Viewers are described in New-OfficeWebAppsFarm.

If you see “500 Web Service Exceptions” or “500.21 – Internal Server Error” messages

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:

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:

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

Office Web Apps Server 2013 Latest Update

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, read more about this topology.

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 in Securing Office Web Apps Server communications by using HTTPS. This Office Web Apps Server farm will provide Office Web Apps functionality to SharePoint 2013 andLync 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.

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 because that host doesn't support editing.

Other parameters that configure translation services, proxy servers, ClipArt support, and Online Viewers are described in New-OfficeWebAppsFarm.

If you see “500 Web Service Exceptions” or “500.21 – Internal Server Error” messages

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:

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

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:

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 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 you see “500 Web Service Exceptions” or “500.21 – Internal Server Error” messages

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

For Windows Server 2012 or Windows Server 2012 R2

See also

New-OfficeWebAppsFarm
New-OfficeWebAppsMachine

Content roadmap for Office Web Apps Server
Plan Office Web Apps Server
Configure Office Web Apps for SharePoint 2013