Welcome to the last post in our series on the Lync Server 2013 install process. At this point, all of our primary Lync services are running – IM/Presence, Voice, Conferencing, Persistent Chat.
We used two testing methods to verify the services:
–Creating a dummy account to IM others (from two different workstations), AND
–Calling to & from this account, both to existing Lync users and to non-Lync numbers.
Everything’s behaving as it should.
So…let’s change it!
Or rather, add to it. There are two remaining services we want to add in: Mobility Services and Web Apps Server.
Installing Mobility Services
Mobility Services essentially allows you to use Lync on mobile devices (phones and tablets). It’s built into the Lync 2013 Front End Server, like Monitoring and Archiving were.
Which means its components are already installed! All you’d need to do is configure it.
You’ll find the deployment process for Mobility Services here: Deployment Process for Mobility – Microsoft TechNet
We also used 2 additional reference URLs:
Mobility for Lync 2013 – Lync Server 2013 TechNet Forums
Deploying the Lync 2010 Mobility Service – Jeff Schertz’s Blog
In fact, the Schertz article is so comprehensive that I will point you to it for configuration purposes.
There’s only one notation I can make. Our Mobility autodiscovery URL was lync.yourdomain.com. Thing is, we had this same URL as the Edge URL. Mobile autodiscovery didn’t work.
So we changed to lyncdiscover.yourdomain.com in DNS.
This caused a cert error, but that was related to our original firewall routing issue (which is NOT a Lync 2013 error). Bill, our networking expert, changed our routing paths to fix it.
Once you follow the Mobility Services configuration process, use the Powershell cmdlet Test-CsMcxP2PIM to test mobility service.
I grabbed my iPhone, and signed onto Lync. Test successful!
Installing Web Apps Server
Since we have conferencing enabled, the boss wanted Web Apps Server running as well. Web Apps Server is a new service in Lync Server 2013, intended to support using PowerPoint presentations while in Online Meetings. (It will also support presenting with the other main Office applications – Word, Excel, OneNote).
The Reference URL we used was:
Installing Office Web Apps Server for Lync Server 2013 – Microsoft UC and other stuff Blog
**Web Apps Server needs its own cert, and has to be trusted on Edge so discovery works. Bear this in mind.**
For Windows 2012, run the following PowerShell cmdlet:
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
As you can see, this installs some required Windows components.
Next, download & run the Office Web App Server Program here:
Microsoft Office Web Apps Server – Microsoft Download Center
When you run it, you’ll be prompted for an install location. We kept the default, “C:Program FilesMicrosoft Office Web Apps”.
Click “Install Now” to run the install. When it’s done, click Close. Then we can proceed with configuration.
**NOTE** After installing program you must REBOOT in order to run the New-officewebappsfarm cmdlet. Otherwise the cmdlet is not recognized.
Before moving forward, create a local certificate for the WebAppServer or External Certificate. Our example uses the internal certificate:
New-OfficeWebAppsFarm -InternalURL “https://localhostnameofappserver.whateversuffixused” –CertificateName “Office Web Apps”
When using the above cmdlet, the certificate name must match the friendly name of the certificate. Otherwise you’ll run into a problem. Like this!
You can confirm the discovery URL for the OfficeWebApp server by going to the designated URL you defined (for instance, https://localhostnameofappserver.suffixused/hosting/discovery ).
An XML screen will appear.
Configuring Lync Topology for Web App Server
Open Topology builder and go to Site – Shared Components – Office Web Apps Servers. Right-click and select “New Office Web Apps Server…”
Type in the FQDN of the newly deployed Office Web App server. The Discovery URL field should auto-fill with the proper Office Web Apps Server URL.
(If you typed the web address rather than the FQDN, it will not auto-fill as expected. You’ll either have to cancel and redo the process, or type in the appropriate information as below.)
FQDN Format: webapp02.yourdomain.dom
Discovery URL Format: webapp02.yourdomain.dom/hosting/discovery
Click OK. Once that’s complete, you’ll need to associate the Office Web App Server to the Front-End server.
Right-click your Front End server and select “Edit Properties”. Under Properties –> General, scroll down to the File Store field. Choose “Associate pool with an Office Web Apps Server”. Then click the drop-down box, and select your newly built Office Web App Server.
Click OK. Then Publish your Topology again.
You can validate the Web App Server by reviewing the Lync Front-End server’s Event Viewer. You’ll have to look at the Lync Server logs. You’re looking for two event IDs: 41032 and 41034, to confirm a successful implementation.
When you see both of these, you’ll know Web Apps Server is up and running!
And that’s the last of our “Moving to Lync Server 2013″ post series! I’ll gather up all the links into a comprehensive guide later on.
Hope you’ve found these posts useful. As always, I like feedback from readers – what you’re working on with Lync, any issues you might run into, and so on.
See you next time, with more Lync Server content!