![]() ![]() This applies to Front End Servers, Edge Servers, Mediation Servers, and Directors. If a server running a certain server role fails, the other servers in the pool running the same role will take the load of that server. ![]() You can create custom roles that have privileges to run a specified set of Windows PowerShell cmdlets or specified PowerShell scripts in the Lync Server Management Shell.ĭisaster Recovery, High Availability, and Archiving ChangesĪs in Lync Server 2010, Lync Server 2013's main high availability approach is based on server redundancy through pooling. The second enhancement is the ability to create custom roles. Members of the Persistent Chat Manager role can manage specific Persistent Chat rooms. Members of the Response Group Manager role can manage specific Response Group queues. First, there are two new predefined roles: Response Group Manager and Persistent Chat Manager. In Lync Server 2013, Microsoft enhanced the RBAC feature in two major ways. Organizations that have specific security requirements for allowing external traffic through the perimeter network to the Lync servers inside the network might consider deploying this role. The Director role is no longer presented as a recommended role but rather an optional role. Persistent Chat will be discussed in more detail in the "Lync 2013 Client Enhancements" section.) (Persistent Chat is the new name for Group Chat. The Persistent Chat Server is a new server role. The A/V Conferencing Server role is now part of the Front End Server role. Monitoring is an optional feature available on all Front End Servers. Lync Server 2013 no longer has a separate Monitoring Server role. ![]() Archiving is an optional feature available on all Front End Servers. Lync Server 2013 no longer has a separate Archiving Server role. There are many changes to the server roles in Lync Server 2013. It also provides scalability within the pool and eliminates the single point of failure (i.e., the single Back End Server). This distribution of data storage improves performance because the Back End Server no longer has to render the up-to-the-second transactions for users regarding presence, contacts, and conferencing information. Those responsibilities have been transferred to the Lync 2013 Front End Servers. In the Lync Server 2013 architecture, the back-end Microsoft SQL Server database is no longer the point of reference for the real-time data store in the Lync pool that contains the updated presence information, permissions, and user contacts. In Lync Server 2013 Enterprise Edition, the architecture of the Front End pools has been changed to provide a more distributed systems architecture, as Figure 1 shows. One of the most important topology changes deals with the Front End pools. The topology changes in Lync Server 2013 bring about many rich enhancements that will affect how administrators design and ultimately deploy their Lync environments and approach upgrades. The Lync topology consists of multiple server roles that work together to provide IM, presence, conferencing, and VoIP functionality. The Lync topology is the overall layout of the Lync environment, including Front End Servers, Edge Servers, and Mediation Servers. VoIP functionality, which is called Enterprise Voice I'll also discuss other noteworthy enhancements made to the:ĭisaster recovery, high availability, and archiving features I'll discuss the server role changes as well as other changes to Lync Server 2013's topology. There are several significant architectural changes that simplify the deployment of Lync Server 2013, with one of the biggest being server role consolidation. (In case you're unfamiliar with Lync, presence is a feature that displays a user's availability, willingness to communicate, and contact information.) Like its predecessor, Lync Server 2013 provides support for enterprise IM, presence, and conferencing, with direct integration to the Microsoft Office suite of applications. Microsoft Lync Server 2013 does a commendable job building on the features introduced in Lync Server 2010, making the transition to this new version compelling for IT managers and unified communications (UC) implementers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |