Tuesday, January 22, 2013

Install prerequisite software for Office Web Apps Server
Open the Windows PowerShell prompt as an administrator and run the following example commands to install the required roles and services.
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,NET-Framework-Features, NET-Framework-Core, NET-HTTP-Activation, NET-Non-HTTP-Activ, NET-WCF-HTTP-Activation45 -source D:\sources\sxs
If you are prompted, restart the server when the command finishes.

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
Download Office Web Apps Server from the Microsoft Download Center.
For Windows Server 2012, open the .img file directly and run Setup.exe (double-click it).
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 select Continue.
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.
When Setup finishes installing Office Web Apps Server, choose Close.
Create a certificate

Like most Lync services, you’re required to assign a certificate to this service as well.
We’ll use the IIS Manager to do that:
Launch the IIS Manager and scroll down to “Server Certificates”:

In the “Server Certificates” window, click on “Create Domain Certificate” in the Action pane:

In the “Create Certificate” window, fill the details of your server and organization. Note that the “Common Name” must be in the “Server.Domain.Local” format:

In the next window, choose you CA, and give your certificate a friendly display name – We’ll use that name later:

When you click “Finish”, you’ll see you have a new certificate:

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, 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
Add more servers to the farm
After the first server is running Office Web Apps Server, run the following command on the other servers to add them to the farm:
New-OfficeWebAppsMachine –MachineToJoin <nameofmachinetojoin
Add the Server to Lync Topology

Open the Lync Server Topology Builder, expand “Shared Components”,right click “Office Web Apps Servers”, and choose “New Office Web Apps Server…”:

In the new window, type your server’s FQDN. the wizard will fill-in the discovery address:

Press OK, and the server is in your topology:

Associate your Front-End pools with your Office Web Apps Server, publish the topology,

To check that, open a web browser and go to https://LyncWAC.YourDomain.Local/hosting/discovery, you should get this result:

If you get an error, try fixing your .Net Framework 3.5 components with this command:
%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru,
Then, run iisreset /restart /noforce.

Please Note that you have to bypass th mydomain.local in the IE proxy setting on the WAC servers and the Frontend servers otherwise you will get this error message "Some sharing features are unavailable due to server connectivity issues" or "Sorry, we can't open this presentation because we ran into a proble, To view or edit this presentation, open it in Microsoft Power Point" when you share Powepoint presentation between lync 2013 clients

No comments:

Post a Comment