One of our sales guys was kind enough to get me an NFR license for Loadbalancer.org VA (Virtual Appliance) for my lab. I started going through the Lync 2010 deployment guide and have to say, it wasn’t as massive as few documents I’ve seen recently, but something wasn’t right . Above all, the re-encryption and cookie persistence scenario required for Lync Mobility was not (at all) easy as ticking a few check boxes. Hence thought I’ll document the deployment as I’ve been awarded the gift of time by SouthWest trains My Lync 2013 infrastructure My current Lync Server 2013 infrastructure, hosted on a VMware ESXi 5.x, consists of 2 x FE servers part of an Enterprise Pool 1 x Back-end SQL server 1 x Office Web Apps server 1 x Edge server 1 x IIS ARR Reverse Proxy Note that I have neither deployed any director pool nor edge server as a pool and hence this can be classified as a simple Lync 2013 deployment. Load balancing requirements Lync Server 2010 introduced DNS load balancing to provide a native load balancing mechanism which can be quickly and easily configured and is extremely cost effective. DNS LB is used to balance SIP and media traffic which are unique to Lync servers. But if you have more than 1 server in a Front End pool, you would need a Hardware Load Balancer as well to load balance client-to-Server web traffic. What are the web services to be load balanced (again, based on my infrastructure detailed above) ? Lync External Web services (Externally resolvable, published through a reverse Proxy) Lync Internal Web services (Internal only) Simple URL’s (Internal and External – part of the first two) Mobility services (internal and external [...]
The post Deploying Loadbalancer.org VA for Lync 2013 Web Services appeared first on UnifiedMe.