Starting with Lync Server 2010, some significant changes to how the deployment is managed have been made. Instead of individually installing and configuring servers, the deployment is managed centrally through a tool called Topology Builder. This shift in management helps make administration easier for organizations and limits the potential for mistakes.
For those familiar with Office Communications Server 2007 R2, administrators had to log on to each server in the topology and manually configure options such as next hops, monitoring associations, and service ports. With Lync Server 2013, the configuration is completed in advance and then published to the Central Management Store (CMS).
When a server is deployed, ...
No credit card required