Lync 2010 Standard Edition server
Standard Edition server with Monitoring Server and Archiving Server - will need a dedicated SQL server
Lync 2013 Standard Edition server
Monitoring and Archiving Roles can be collocated but it will need a separate SQL server
If you choose to deploy Persistent Chat Server on a Standard Edition server, you can collocate the Persistent chat database and the Persistent Chat Compliance database
on the same Standard Edition server.
New features in Lync 2013
Lync Web app web based Lync app to handle Audio and Video
Persistent Chat
WAC server (Office Web Apps Server) Lync 2013 for viewing PowerPoint broadcasts, SharePoint 2013 for viewing and editing Office documents, Exchange 2013 and OWA for previewing Office file attachments
XMPP
No longer hash-derived FE,
Routing Group -
Windows Fabric
Lazy Write (no realtime dependency on BackEnd SQL)
SQL mirroring and cluster
Backup registrar is now backup pool and provides full features in case of disaster because of Routing Group
MN trunking
OAuth, UCS - Unified contact store - The contact list can be migrated from Lync to Exchange 2013 and are retrieved using EWS, this allows for Hi-Res images.
MSMQ removed now it is (lync storage service, it’s a storage Framework) LYSS DB in the LyncLocal Instance (it temporarily holds the archiving/QoS, etc data from the client and then sends to SQL BE LCSLOG DB)
Centralized Logging Service – Till 2010 Lync server logging tool was used. But with 2013 scenario bases logging tool via shell is come tool uses TCP 50001, TCP 50002, and TCP 50003.
Routing Groups
Lync Server 2013 doesn't use hash algorithm to determine where a user is going to end up. Instead, when you provision a user, the user is immediately put into a particular routing group.
Each routing group will contain 3 replicas: primary, secondary, and backup secondary which together are called a replica set. User services for all users will be handled by their primary replica. All users in the same routing group will be homed on the primary replica. If the primary replica fails, all users in that Routing Group will failover to the same secondary replica.
Routing groups will get rebalanced when Front End servers are added or removed from the pool. If the primary replica goes down another will be promoted to primary. Depending on both user count and how the primary became unavailable will dictate when the Windows Fabric rebuilds another replica.
Each routing group is assigned to a particular Front End server until that server is rebooted or goes down.
Each routing group has a primary, secondary, and tertiary copy when at least three Front End servers are deployed.
Upgrade Domains
Upgrade Domains are logical groupings of servers on which software maintenance such as upgrades and updates are performed at the same time. If you don’t adhere to upgrade domain guidelines for server patching, you will impact routing groups and potentially the pool itself. A routing group will never have two of its three servers in a single upgrade domain.
Roles consolidation
monitoring and archiving collected in FE. Each front-end server communicates directly with the monitoring and/or archiving database, eliminating the need for a separate monitoring/archiving server.
You can no longer install the A/V conferencing server role separately. It is now always co-located with the front-end role.
Directors are now an optional role.
DR/High Availability Options
Lync 2010 introduced the concept of a Backup Registrar. When a user's home pool becomes unavailable, the client can automatically register with a pre-defined backup pool.
This maintains registrar and voice availability, but the client loses conferencing capabilities, and the user's contact list is unavailable. and metropolitan site resiliency,
i.e. the pool is stretched between two SITES i.e. site A and site A and each site had their own SQL and there will be a cluster between SQL of A and B
In Lync 2013, Backup Registrar name is changed to Backup Pool and users will maintain nearly all functionality in the event of a failed pool. This is made possible because all user data is now replicated between two other Lync servers (Routing Group) in the enterprise.
Each front-end server stores a complete copy of all the databases stored in the SQL back-end, so if the back-end SQL database server is unavailable, the front-end will still
function. (Lazy Write) Also, Lync 2013 supports SQL mirroring as well as clustering on the back-end databases.
Enterprise Voice
In Lync 2010, if you had multiple mediation servers connecting to the same PSTN gateway or SIP trunk, you had to fake the Topology Builder out by creating multiple
DNS A records pointing to the same IP. Lync 2013 now supports M-N trunk routing. This allows you to have multiple trunks to different gateways, and a gateway to
have multiple trunks to different Mediation Servers.
Lync 2013 includes support for inter-trunk routing. This feature allows Lync to act as an intermediary between two or more different phone systems. For example,
Lync can accept calls from one PBX, and pass the call through to another PBX. This can be very useful in larger environments and allows Lync to be the backbone of
a corporate telephone network.
In Lync 2010, you could use trunk translation rules to modify the CALLED phone number before passing it to the next hop. However, you couldn't make any changes to
the CALLING number (ie the person making the telephone call). Lync 2013 now allows you to make changes to both the called and calling number. This is very useful when
the PSTN provider does not accept E.164 formatted phone numbers. For example, in North America, many PSTN providers do not accept the country code 1 as part of the
number and only accepts 10-digit numbers. In the past, an external gateway would have to do the necessary manipulation, but with Lync 2013, all the number manipulation
can be done in Lync.
There are also several other new Enterprise Voice related enhancements. Delegates can setup simultaneous ringing to their mobile devices for incoming calls to their manager.
When a user has setup simultaneous ringing to a mobile phone, and the device is turned off or out of range, Lync 2013 can determine that an incoming call was immediately
routed to voicemail, and disconnect that endpoint so the call can continue to ring other endpoints. Caller ID presentation allows administrators to modify the Caller ID format
in a much more scalable way than in Lync 2010, which only allowed Caller ID changes based on the route.
Mobility
Mobile clients now support VOIP calls
Other New Features
Other features that don't fall into the above categories include:
- Full A/V capabilities on the Lync Web App client
- Full IPv6 support
- VDI plugin - allows full A/V support in virtual desktop environments
- H.264 SVC codec support
- Skype federation support
- Integration with Exchange 2013, 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.
No comments:
Post a Comment