Topology changes: Rather than having separate server roles for monitoring and archiving (as Lync 2010 did), Microsoft has moved both roles into the Front End Server role as optional features. The A/V Conferencing Server is always located with the Front End role as well, and the Director role is no longer “recommended” but optional; Microsoft says you can “safely exclude the Director with confidence that the Front End Servers will provide the same services in their place.”
Persistent chat: Formerly known as group chat, this new server role has several components: PresistentChatService, PersistentChatStore, and PersistentChatComplianceStore. “Persistent” means a history of the chat session is retained, so users can jump into a chat room and get up to speed with the conversation that has already taken place. Some people suspect this could be a replacement for email distribution lists by providing a constant, updated message repository (like a wiki). The administration tools are integrated with the Lync Server control panel and include PowerShell cmdlets.
Lync Web app: A new version of Lync Web app has full conference support. Stephen McCassey, a Lync instructor at New Horizons Computer Learning Centers, says this is one of his favorite features because it makes it easier for users without the Lync client to join meetings via their browsers, with support for both audio and video. As a result, the Lync Attendee client is gone, which means there’s one fewer client for IT to manage.
RBAC additions: The role-based administrator console adds the Persistent Chat Manager role to support the new persistent chat capability. RBAC also reintroduces the Response Group Manager role for managing response group queues — a feature found in Office Communication Server 2007 R2 but dropped in Lync 2010.
Enterprise voice features: Lync Server 2013 has many new routing features designed to improve enterprise voice, such as support for multiple trunks between mediation servers and gateways, as well as intertrunk routing to let Lync Server act as a go-between among different phone systems, such as to connect an IP-PBX and a PSTN gateway. Other enterprise voice features include manager/delegate simultaneous ringing (multiple designated phones ring at the same time), voicemail escape (which lets business calls on personal lines pass through to corporate voicemail), and caller ID presentation.
Disaster recovery and high-availability improvements: Server pools with redundant roles running are still the primary method for providing high availability of Lync services, just as in Lync 2010. However, you can now pair front-end pools in different data centers; if one pool goes down, the administrator can fail over to the other pool. Likewise, you can provide back-end server availability through SQL mirroring for the Lync databases.
New conferencing features: Lync 2013 expands its client compatibility to include IE10, Windows 8, Windows Phone, iOS, and Android. PowerPoint sharing has been improved to allow for higher-resolution displays. Users with the proper permissions can scroll through a PowerPoint presentation independently of what slide the presenter is currently showing. The gallery view shows video windows of participants, organized by participation levels. The archiving features have been enhanced to include anything shared in a conference, such as PowerPoint presentations, file attachments, whiteboards, and polls.
Other features in and improvements to Lync Server 2013 include:
- Support for HD resolution up to 1080p. Also, the H.264 video codec is the default for video encoding, which brings with it greater flexibility for resolutions, frame rates, and scalability.
- IPv6 is fully supported, in addition to support for IPv4. You can go dual-stack (IPv4 and IPv6) if you like.
- Hybrid deployment support for on-premise and hosted (cloud-based) Lync is supported.
- There’s a unified contact store with Exchange Server 2013, as well as the ability to use high-resolution photos for your contacts.
- Archiving integration lets Lync works with the Legal Hold feature in Exchange for compliance and e-discovery needs.
Thanks to J. Peter Bruzzese