Monthly Archives: September 2013
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
Today I had a case at a customer where the PSTN users, which dial in to a Lync Conference, was only shown as “Guest Guest” like below:
The number which is normally shown on mobile users wasn’t there. →']);" class="more-link">Continue reading
If you experience problems when you try to sign in to Lync Phone Edition, with this error:
“An account matching this phone number cannot be found. Please contact your support team.”
The new September update for the Lync 2013 reveals new features besides bug fixes that it also contains.
The first new feature is Spell checking in the Lync Client, which is a feature that many users will love.
Hopeful this can help remove all the spelling errors when using IM J but time will show.
The spell check follow the language on your computer – In my case its Danish, so my spell check is in Danish. →']);" 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
This is my fourth post in the series of deploying a Lync 2013 HA environment.
In the previous article, we have been deploying SQL Server 2012, which we are going to use for a mirroring cluster in Lync 2013.
Before starting the Lync installation, we need to deploy a Lync file store. A Lync file store is a file share where Lync stores replication data, the address book, Conference content etc.
Because we are deploying a HA solution the file store should be deployed on a DFS share which replicates the data between two or more file servers. You could also deploy a File Server cluster.
I this post I will use a DFS share.
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
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