Firewall port requirements of the Lync 2013 internal clients. A table to configure and manage firewall rules requires to enable Lync features to the clients
Chapter 6, Deploying Persistent Chat Server, introduces Persistent Chat, which is a new
feature of Lync 2013, that enables the creation of a knowledge base for your users and
the construction of “private” spaces, where a selected groups of our users are able to
communicate. Here we will see how it works and how it is implemented.
The changes in the Lync 2013 client autodiscover process (and also in the Lync 2010 client, as I will explain later) and the possibility to use mismatched domains between the SRV and Host (A) records open an interesting opportunity to downsize the required SAN names to a total of six (S I X).
“Lync is now the fastest growing business at Microsoft” “The productivity workload offerings of Exchange, Lync and SharePoint each experienced double digit growth this quarter, and Office 365 continued […]
Design and commercial logics of Lync 2013, related to the company’s scenario, that is important to understand, keeping a keen eye to the online solution.
Lync Online Hybrid Deployment with Split Domain
This scenario requires and on-premises deployment of Lync and an agreement with an Office 365 / Lync 2013 online multi-tenant.
This solution allows enabling our Lync users to Lync online or to Lync on-premises, leaving to the Lync administrator the capability to migrate them from one situation to the other one and vice-versa smoothly.