Lync Server role required for External login

Lync Server role required for External login. 

Now day’s external login is very much required because peoples are login from different location, home, remote location etc. 

There are few roles which necessary for external logon. 

1.     Lync Edge:

Edge Server role is a Lync server designed to be connected to the Internet to extend Lync Services outside an internal network with no VPN or a dedicated connection. Lync Edge can be deployed in a pool for high availability. 

2.     Reverse proxy:

A reverse proxy is required for external access. Continuity for the services published with the reverse proxy requires a specific Hardware or software solution, depending on the kind of server we are using to Publish Lync.  Also, if there are existing deployments without a reverse proxy, publishing Lync services directly to the Internet will not be a supported solution.

You can see a high-level overview of the previously mentioned scenarios: 

 

To complete the list of Lync roles, we must also consider the following areas:

• Mediation: This can be deployed as a separate server or collocated on a Front End. It is used for IP-PBX, Gateway, and SBC interoperability to provide Enterprise Voice and dial-in conferencing. 

• Director: This server enhances the performance of user authentication and adds a security layer. 

• Persistent Chat Server: This server is used to create one or more "chat rooms" that can be moderated, and to retain the instant messages of the users for a defined amount of time. 

• Monitoring: This role, collocated on a Front End, collects data about the quality of the service with Enterprise Voice and audio/video conferencing. 

• Archiving: This role, collocated on a Front End, is used for compliance; it stores IM messages and conference contents. Persistent Chat Server requires a Back End Server role, and may include an additional role, Compliance Back End, to keep track of the messages published in Persistent Chat Server if required by local regulations or laws.  

From the planning point of view, we need to keep the following points in mind:

• Some roles (such as archiving and monitoring) are always collocated on the Front End, while other roles (such as Mediation server) can be collocated depending on the scenario. Edge, and Director always require a dedicated server.

• Archiving, monitoring, and Persistent Chat require a database for each one.

For this we could use a dedicated database or instance; collocate the databases on the SQL Express installation that is part of Front End, or collocate the databases on SQL Server that has the Back End role for an existing pool.

Enterprise Edition Front End, Mediation server, Director server, and Persistent

Chat Server can be configured in a pool (that is, a group of servers having the same features installed). Pools are an important feature for high availability and load balancing (usually, the mechanism used is DNS load balancing, but hardware load balancing is supported as well). 

The previously mentioned list does not include additional servers, such as Exchange and SharePoint. If these servers are present, they will be able to interact with Lync in a native manner to create an additional set of features. Well-known examples of the integration include the presence of indicators in the Outlook client and Lync meeting integration with calendar (if Exchange is present), or any skill-based search that enables us to search for a person in Lync using the professional expertise recorded in SharePoint as criteria.

 

Thank you.