Lync Server 2013
With the October update Lync Server 2013 is now supported on Windows Server 2012 R2 according to Doug Deitterick’s blog http://blogs.technet.com/b/dodeitte/archive/2013/10/25/lync-server-2013-now-supported-on-windows-server-2012-r2.aspx.
We have now come to the step where we are going to install the Access Edge Servers.
In our topology, we are going to have two servers, which we have defined and created in an earlier post, but you can make use of the tips that I will come with in this post even though you are only installing a single Edge Server.
The Access Edge Servers is actually one of the parts that is often causing problems in a Lync installation, not because the servers is not function or the software is broken, but simply because it’s not set up correctly, and with that I mean the servers, but also the surrounding components like the firewalls, dns etc.
The servers is placed in two different DMZ zones, like in the below illustration: →']);" 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).
Microsoft has relased Lync Server 2013 CU3 (October 2013), which contains a number of fixes (one of them I reported to MSJ)
You can get the updates here: http://exchangepro.dk/updates/lync/lync-2013-updates/
The biggest update in the release seems to be to the Call Park Service, where it now possible to get transferred to a operator when pressing *0 in a dialin conference.
The other updates includes this:
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
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 seventh part of the series of installing a Lync 2013 HA, we have come to the point where we are ready to install the first frontend server in our Lync Server 2013 High Availability solution.
We are going to have three frontend servers, but for now we have only defined one frontend server in the Enterprise Pool. When Lync is up and run we will later on add the two other frontend servers and hardware load balancing.
When we are installing the Lync servers, the deployment wizard will read information from the central management store and thereby determines what needs to be installed on the server.
Start the Deployment Wizard on the first frontend server. →']);" class="more-link">Continue reading
Today I had very nice day together with my good colleague Rune, which is taking care of a big Lync 2013 environment at one of our customers.
We were making some changes of the frontend servers, which require that we should run the Enable-CScomputer.
However, that failed on two of the three frontend servers with this error:
Alter failed for Server ‘LYNCSERVERlynclocal’ →']);" class="more-link">Continue reading
In the sixths post in my series of installing a High Availability solution for Lync Server 2013 we are now going to create the Lync topology.
In the previous posts we have been making some of the fundamentals ready for the Lync installation, by creating a SQL 2012 mirroring cluster, a DFS file share and making a bunch of servers ready.
I will start by the drawing below, which will summarize how the servers is placed and how the servers is named.
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