A Unified Communication Blog
Get Adobe Flash player


In my series about using Lync and Exchange better together, we will in this post, be looking at integrating Lync and Exchange so that we can use Exchange as a unified contact store.


What is Unified Contact store you might ask?

Before we got Lync 2013 and Exchange 2013, both products have there own way of storing the users contacts.

Lync can store contacts in Exchange or actually in Outlook in a Lync Contact folder, which is synchronized, and this sometimes can cause problems if they get out of sync. →']);" class="more-link">Continue reading

In my new series we started by looking at integrating Lync and Exchange so that we could use Chat and Presence in Outlook Web Access and get a more rich experience when these great products is used together.

Setup Voicemail

In this post we will have a look at the Voicemail capabilities in Exchange Unified Messaging and how to set it up.

I will be using Exchange 2013 and Lync 2013, but the process for using Exchange 2010 is almost the same.

As you might know, in Exchange 2013 the Unified Messaging role is installed on all servers as default whereas in Exchange 2010 it was a role you need to install, either separate or together with some of the other roles. →']);" class="more-link">Continue reading

Windows Server 2012 R2 contains a new feature called Web Application Proxy. WAP is a very simple reverse proxy which can be used to publish the Simple URLs in Lync Server 2013.

In this post, I will guide you through how to setup and use it as a reverse proxy for Lync and the Office Web Apps Server.


I have in my setup defined these public DNS names:

  • Csweb.exchangepro.dk (Frontend Server external name)
  • Cswebapp.exchangepro.dk (Office Web App External name)
  • Cswebdir.exchangepro.dk (Director Server external name)
  • Lyncdiscover.exchangepro.dk (Lync Discover url) →']);" class="more-link">Continue reading

We now have our backend servers up and running and one of the frontend servers, so in this post we will install the two WAC servers in a farm. (see the topology in http://exchangepro.dk/2013/09/21/creating-the-lync-server-2013-ha-topology-part-6/).


The Office Web Apps Servers or WAC is used in Lync Server 2013 for streaming PowerPoint content from Lync meetings to the participates. This means that the participants can see the nice features like animations, sounds, videos that might be inside the presentations.

When a presenter starts a presentation from a Lync meeting the content is uploaded to the Lync FileStore. From there the WAC servers will access the content, and begin to stream the PowerPoint to the participants.

The same WAC servers that we use in Lync can also be used by Exchange 2013 and SharePoint 2013, to provide an web experience for the Office applications. For now, I will only use them for Lync. (but keep coming back and I will show you how to use them with Exchange 2013).

→']);" class="more-link">Continue reading

Windows Server 2012 R2 is soon reaching the GA state, so I decided that I would test how Lync Server 2013 behave on a Windows Server 2012 R2 RTM Server.


So this guide will take you though on how to install Lync Server 2013 on a Windows Server 2012 R2 Server, RTM.

I have created a virtual server in my HyperV lab with these specs:

  • 3 vCPU
  • 8 GB RAM
  • 100 GB Disk space

→']);" class="more-link">Continue reading

I my prevoius post we installed the first frontend server and started the services for the first time.

As with all new Lync Servers it’s very important to keep the updated with the latest fix from Microsoft

So lets start by updating the first frontend server with CU2 (http://exchangepro.dk/updates/lync/lync-2013-updates/).

Download the “LyncServerUpdateInstaller.exe”

Right click on the file and select “Run as administrator” →']);" class="more-link">Continue reading


In the Fifth post in my little series of deploying a Lync Server 2013 High Availability environment, we have now come to the fun part were we almost can begin to deploy Lync.

In the previous post we have been setting up a SQL Server 2012 mirroring cluster and a DFS file share.


As a prerequisite to use Lync, you should have deployed an internal PKI infrastructure, because Lync uses certificates to secure its communications. You could in theory use public certificates if you have a lot of money, but I will not recommend it.


As a start, we need to create the servers, which we are going to be used in the installation of Lync, which will include →']);" class="more-link">Continue reading

In Lync 2013 Enterprise users is allowed to make PSTN dial out from a Lync conference without a plus CAL license.

This feature is controlled, in the Conference Policy for the user

→']);" class="more-link">Continue reading


In the third post of the series of creating a High Availability solution for Lync, we will be looking on how to configure the SQL 2012 mirroring cluster which has been installed in Part 1 and Part 2.


I like to use windows firewall on my servers – many disable it, but I will rather use a little bit more time to figure out to configure it, so the first part is to add exceptions to the default rules, so that the SQL cluster will work.

I will run the below cmdlets on all three SQL servers (you could get more restrictive on the witness server).

Before running it on the servers you should adjust the IP ranges so it fit your environment and subnets.


New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQLServer)” -Direction Inbound –Protocol TCP –LocalPort 1433 -RemoteAddress LocalSubnet -Action Allow →']);" class="more-link">Continue reading

Below is a powershell cmdlet you can use to enable AD users in an OU for Lync.

Get-CsAdUser -filter {Enabled -ne $True} -OU “OU=Lync Users,DC=exchangepro,DC=dk” | Enable-CsUser -RegistrarPool frontend.exchangepro.local -SipAddressType Emailaddress


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 77 other subscribers

Follow me on Twitter