![]() ![]() ![]() In the event that you're performing maintenance or patching Lync 2013 Front End servers and you bring more than the appropriate number of Front End servers down, you'll get an error message in the Event viewer stating "Local Pool Manager has been disconnected from Pool Manager." If the number of remaining running servers is still below the threshold level, the remaining servers Lync services in the pool will stop, making the pool inoperable.įront End servers in an Enterprise Edition pool are organized into upgrade domains. Table 1: Lync Server 2013 Front End Quorum Reference Number of Servers that Must Be Running for Pool to Be Functional Total Number of Front End Servers in the Pool ![]() Table 1 shows the minimum number of servers that are required to be online and available in order for the Lync 2013 pool to be in a functioning state. In order for a Lync 2013 Front End pool to be considered in a functional state (which is a good thing), a certain number of Front End servers in the pool need to be up and running. A basic understanding of how quorums work with clustering is now coming into play for Lync 2013 administrators, not necessarily on the SQL Server Back End server side but on the Front End servers. Microsoft Office Communications Server (OCS) 2007 R2 introduced SQL Server clustering with Back End servers for the Front End pool. Lync Server 2013 introduced the concept of a quorum, which is a major change from previous editions of Lync. ![]() I'll cover the following areas related to Lync Server 2013 Front End maintenance: With the release of the first update to Lync Server 2013, there are some items I wanted to cover so that you aren't taken by surprise when performing maintenance or patching of the Lync 2013 Front End servers. The first cumulative update for Microsoft Lync Server 2013 was released in February 2013. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |