So, we run our own Infrastructure where I work, that includes our own hosted Lync Environment. Now let me say this up front: I HATE OUTSOURCING! you never get the same quality as if you had your own environment and I don’t see the point of paying someone else to save a little bit when I can have it myself and the Return on Investment is much bigger and I save more over the course of a year.
Anyway, ranting aside, this multipart series describes how to implement KEMP Loadbalancers for Lync. We got a good deal and they are recommended by Microsoft, plus their documentation on their website is good… until you need to use it.
So the Kemps arrive (we bought 2 to do High availability), and the initial setup turns out that they had 2 different versions of Loadmaster 7 OS. Great, except that the two were VERY VERY different. So, I had to contact support to get the laters firmware and update them both because they were actually BOTH out of date. Oh well, updating went smooth and is easy, that I have to give them.
Now we had both running and configured properly (I will post the configuration of it actually in Part 2) and off I went to fetch the Lync 2013 Templates from Kemp. They are great because you can easily set the Lync 2013 services up without setting all the nitty gritty details.
Now, When you upload the templates they appear in a list and Kemp has really good documentation describing each template and setup. Except that the documentation does not match the templates… like AT ALL! you have to guess most of it. The templates are named differently AND described differently than in the documentation and deployment guide.
Not fun…. but in the end we prevailed. Watch for Part 2 in a day or two…
PS: great devices… I have to give them that.