Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant Migration Specialist)

Even if this article comes a bit late. Yes Lync Server 2013 is supported on Windows Server 2012 R2. You must have installed Lync 2013 CU 3 from October 2013. Please refer: http://technet.microsoft.com/en-us/library/gg398588.aspx Windows Server 2008 R2 SP1 or latest service pack Windows Server 2012 Windows Server 2012 R2 The Active Directory Servers are also supported with Windows Server 2012 R2 AD. Please feel free to deploy 2012 R2 AD. Beside this, Exchange 2013 will only run on W2k12 R2 Servers, if SP1 is used for installation. Refer: http://blogs.technet.com/b/rmilne/archive/2013/09/17/exchange-support-for-windows-server-2012-r2.aspx NOTE: If you encounter errors in the event log, ID 32402 and ID 61045 the is  work around to solve this issue. Refer: http://support.microsoft.com/kb/2901554 QUESTION: If you ask for an server in-place upgrade from Windows Server 2012 to 2012 R2. Microsoft did not stated any information regarding this. Windows in-place u...

Lync 2013 Topology with High Availability (POOLs, DNS LB vs HLB) © 2014 - Thomas Pött, MVP Lync (modified 2015.08.18) Download PDF: here The most misunderstood topic in Lync is the high availability. This is regardless of server count, positioning or DNS versus hardware load balancing. Note: This document is neither a sizing nor a configuration guide. You should use this document only for your environment planning’s purposes. In my first chapter I need to drive into the different understandings of high availability. Client-to-Server and Server-to-Server traffic high availability: First I need to explain some generic settings bout load balancing. And one word before you read this article: My personal recommended opinion is the DNS+HLB 1-armed solution, this makes trouble shooting much more simplified and do not require so much network knowledge for the Lync admins. On the Edge server recommend only 1-armed and purely HLB.   Client-to-Server The o...