• Office Web Apps Server 2013 Unhealthy
• Microsoft Office Web Apps Server 2013 Download
• Office Web Apps Server 2013 Cu

.UPDATE 12/5 2017. We had a previous known issue below that always made the OOS server show an unhealthy status, this was fixed in the release of OOS. We are now seeing a new issue in the November 2017 CU for Office Online Server. Office Web Apps 2013. The Office Web Apps server can be used to render Microsoft Word, Excel and Powerpoint file types. Other than this the Office Web Apps server is used by Exchange Server 2013 to provide the Web Ready Document Viewing, something that was made available by Exchange Server 2010 natively (although a non-Microsoft engine was used to achieve this).

Summary

Because of the Microsoft Software License Terms for Office Web Apps and Office for the web Server, the server hosting Office for the web Server must be dedicated to the customer, which excludes any IaaS (Infrastructure as a Service) providers that would not meet this requirement.
The software that is currently supported on IaaS can be found at Microsoft server software support for Microsoft Azure virtual machines.

More Information

For more information, see Volume Licensing for Microsoft Products and Online Services.
On the reference page, under Product Terms, choose the Language and Download. Open the Word document that contains the Product terms. Office for the web Server is listed under Office Desktop Applications. The relevant section is under Software Assurance: 'License Mobility: N/A.'
Then, review what License Mobility means: License Mobility through Microsoft Software Assurance
This concerns the applications that are allowed to run on IaaS.

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.

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.

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.

Office Web Apps Server 2013 Unhealthy

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 propertiesT25 alpha cardio video free software.

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:

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

Microsoft Office Web Apps Server 2013 Download

Support Engineer – Microsoft iGTSC

Office Web Apps Server 2013 Cu

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