Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

Now it's time for the for the fir Lync 2013 site. I'm following up with the Topology blog i released earlier. I prepare the first Enterprise Server Lync 2013. Just in the Test Lab, I don't have the Load Balance yet, so what I did was, I gave the only EE Server two IP addresses. The second one is for the POOLLEFT, this is a supported scenario if you only have single pool server in place. First we need all the Pre-Requisites for the new EE Server in place, which I have listed here: PowerShell 3.0 PowerShell 3.0 is not a standalone product, it's part of the Windows Framework 3.0 http://www.microsoft.com/en-us/download/details.aspx?id=34595 .Net Framework 4.5 http://www.microsoft.com/en-us/download/details.aspx?id=30653 Windows Identity Foundation http://www.microsoft.com/en-us/download/details.aspx?id=17331 IIS Windows Desktop Experience SilverLight 4 Visual C++ 11 x64 Active Directory Management tools IIS: Static Content Def...

Untitled Document Generally Load Balancer in Lync must be used along with DNS load balancing or in an entire configuration. If you make used of DNS load balancing, the HLB will be used for HTTP/ HTTPS traffic ( Pool Web Services ). Using DNS LB has both sites, an advantage and disadvantage. Positive is, you can scale a HLB much higher if you only use it for HTTP traffic. The HLB can fully be utilized for SSL offloading. Negative is, you are depending on availability of your DNS infrastructure. Other disadvantage is, DNS based load balancing will never consider the real load on a Lync Server, since the algorithm cannot be aware about the real load. The Client make the decision which server it will connect to. Other is, if you want to make use of PIC, you still need a Load Balancer. Sum: It depends all on your feature set, load calculation, the server count and sure your budget ;) ---------------------------- Gateway consideration (keep in mind): There are ...