First off, hello to everyone at the Lync Conference!

I really wanted to make it down, but it just didn’t happen. Makes me sad…lots of Lync announcements (and goodies) I’m missing out on!

If you want to follow the action (like me), check out these people on Twitter:
@LyncNewsTweets
@Matthewlandis
@whymicrosoft

Now, back to the Lync Server 2013 install process.

Last time, I mentioned that we had to upgrade Active Directory in order to acquire Certificate Services 2012. While we waited for it to install, Larry and I proceeded with building out Lync’s additional server roles: Mediation, Monitoring, Archiving, and Edge.

Mediation: In Place Already, SIP Trunk Needed

First up, Mediation. In Part 3 we’d selected the option to collocate the Mediation Server with the Front End pool. So it was already created. However, we needed to configure a SIP trunk for it.

We had already requested an IP for the SIP trunk; it came from a hosted SIP provider. To define it, we right-clicked “PSTN Gateway” in Topology Builder and selected “New IP/PSTN Gateway…”

Trunk Configuration steps are as follows:

  • Define the PSTN Gateway FQDN (The field will accept an IP address as well)
  • Enable IPv4 or IPv6. (We chose IPv4.)
    • Sub-Option: “Use all configured IP addresses” or “Limit Service Usage to selected IP addresses”. We chose Limit Service Usage, and entered an internal IP.
  • Define Root Trunk. We entered:
    • A Trunk Name (the same gateway IP)
    • A Listening port for gateway (the default is 5067; we changed it to 5068)
    • A SIP transport protocol (default is TLS; we changed to TCP)
    • Associated Mediation Server (we used the pre-set value)
    • Associated Mediation Server port (default is 5067; it changed to 5068 when we changed the listening port).

Click Finish. Trunk configured! We tested it (later) by making phone calls to a test number.

Install Monitoring & Archiving Servers

Since Monitoring & Archiving Servers are add-ons to Front End in Lync 2013, all we needed to do was create a new SQL database for them, and configure the servers in Topology Builder.

Larry had created a new SQL database already, so we proceeded with installing the Monitoring and Archiving add-ons.

(If you need assistance setting up SQL databases for Monitoring and Archiving, refer to the first half of this post:
Step by Step Installing Lync Server 2013 Monitoring Role Collocated on Standard Edition Front End – Part 2: Matt Landis Windows PBX & UC Report )

Right-click your Standard Edition Front End Pool in Topology Builder. Click Edit Properties.

The Properties window should open displaying General properties. Scroll down until you see the “Archiving” option. Check the box.

Click the “New…” button next to “Archiving SQL Server Store”. A new window will open.

We entered the SQL database name (formatted like this: sql01.domainname.dom). We chose a Named Instance, and labeled it “Archiving”. We left the mirroring values on defaults. Click OK and you’re done.

Below this on the Properties window is the “Monitoring (CDR and QoE metrics)” option. Click “New…” next to this as well. You’ll see the same new window as Archiving. We entered the same SQL database name, but labeled this one “Monitoring” to differentiate. All other values left on defaults.

Click OK to close the box. And OK again to close Properties!

(Don’t forget to Publish the topology once these changes are made.)

Installing Edge

Certificate Services 2012 still had not finished setup. So we logged into the designated Edge Server instead.

We ran Lync Setup. After specifying an install location, the core components installed, just like the main Lync install.

Next, the Deployment Wizard pops up. Like I said in Part 2, install Administration Tools first (for Topology Builder).

After that, click “Install/Update Lync Server” like before. We selected “Import from File” when prompted, and navigated to the saved topology file in C:Support.

1 Error: Prerequisite not satisfied.
Remember a few weeks ago, when I said to make sure Windows Identity Foundation” was installed? It wasn’t on this virtualized server. We opened Server Manager, added the “Windows Identity Foundation” service…and no more error.

Resuming Lync setup, I found that it auto-starts the prerequisite install. Plus it moves straight to “Install Edge Server”. You should see Installing Server.msi (Feature_Server_Edge) in the progress window.

Time to request a cert. We tried using the same cert as before (due to the multiple SANs listed within it). In the Certificate Assignment window, we deactivated “Edge Internal” for now (we’d need the local root from the new AD/Cert Services for that).

Right now, we’d just set up the External Edge certificate. We chose to “Import Certificate” from the saved text file; no problems. Then we clicked Assign.

Error! No certs appear in the list.

We tried this a few times with no change. Then Larry looked further into the cert structure. After many frustrating re-import attempts, he found the issue.

It turns out that the private key had not exported with the cert. Even though it was from the same server, we had to repair the key and re-export it before the Edge Server could see it.

*This was NOT a Lync-related error; it came from our own networking environment. I’m posting it in case you encounter the error as well.

Thing is, Lync Server 2013 DID give us an error right after this. A serious error that stopped us in our tracks.

I’ll devote the next “Moving to Lync Server 2013” post to it.

Until then, join me in following the Lync Conference!

Moving to Lync Server 2013: Build Out Mediation, Monitoring, Archiving and Edge (Part 6)
Facebooktwitterlinkedinmail

One thought on “Moving to Lync Server 2013: Build Out Mediation, Monitoring, Archiving and Edge (Part 6)

  • July 4, 2015 at 1:54 am
    Permalink

    When going through the Sub-Option: “Limit Service Usage to selected IP addresses”, shouldn’t an External IP be entered? The article says Internal.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.