Wednesday, May 29, 2013

New in Lync Server 2013 Server & Client Side


Server Side Changes from Lync Server 2010

Management and Administration Changes Changes in RBAC for Persistent Chat Manager and Response Group Manager roles, Persistent Rooms Management now manageable from within Lync Control Panel and PowerShell, Lync Administration through Office group Policy Templates
Server Roles Consolidation – Only 3 server roles –  Front-End, Edge & Persistent Chat Server.
Archiving and Monitoring Roles now part of Front-End Servers – No more separate role or server. A/V Conferencing Server is also now always collocated with Front-End Server Role.
Better High Availability and Disaster Recovery Architecture with Pool-Pairing providing Active-Active Failover – Metropolitan Area Resiliency and Active-Passive Pool Pairing no more supported. Instead 2 pools are always paired in an Active-Active mode.
Support for SQL Mirroring for Back-end Databases – Now supported on SQL Server 2008 R2 and 2012 for Database Mirroring (AlwaysOn feature not supported)
Tighter Exchange Integration Unified Contact Store (UCS) with Exchange 2013 as Backend Contact Store. Lync Server 2013 also supports archiving user data on Exchange 2013 in place of SQL archiving.
Improved Conferencing Features and PowerPoint Sharing  Join Launchers now supported on Windows Phone 7, Android devices, Apple iOS devices, Windows 8 and Internet Explorer 10. Now higher image quality with Office Web Server as rendering engine in background, independent slide browsing from mobile devices and web browsers.
Enhanced Video Conferencing Features – All New Gallery view now support up to 5 concurrent video streams, conferencing resolution supported up to 720p (1080p for Peer-to-Peer communication), H.264 SVC now default video encoding standard
Chat Room Integration with Lync Client – Merged with Lync Client (no separate client needed)
Enterprise Voice Changes
Multiple trunks between Mediation Servers and gateways, Enhanced call authorization for call forwarding and simultaneous ringing, Policy restrictions, Manager/Delegate simultaneous ringing, Voicemail escape , Caller ID manipulation, Conference dial-out for users not enabled for Enterprise Voice.

Client Side Changes from Lync Server 2010

Integration with Office Setup, Customization and Meeting Controls
Client and the Online Meeting Add-in for Lync 2013 Preview included in Office 2013 Preview,
Customize the organization’s meeting invitations by adding a custom logo, a support URL, legal disclaimers, etc..
Access Chat Rooms from within Lync Client, Tabbed Conversations, Favorites for frequent contacts, Video Preview
New attendee mute controls allow meeting organizers to mute participants
Better and Enhanced Lync Web App – Lync Web App allows PC and Mac users to join a Lync Meeting from within a web browser and now delivers a full Lync Meeting experience, including HD video, Voice over IP (VoIP), Instant messaging and Desktop, application, and PowerPoint sharing. Lync Web App plug-in is now a 7MB downloadable (from the earlier 54 MB).
Lync for mobile clients Lync for mobile clients enables you to maintain your presence wherever you are through your Windows Phone, iPhone, iPad, or Android device.
Virtual Desktop Infrastructure Plug-in – Support for all Lync modalities, including IM, audio, video, application sharing, desktop sharing, PowerPoint sharing, whiteboard, and file transfer. Location and emergency services support as well.
Conferencing Updates
Users can now mute the audience and allow or block video sharing when scheduling the meeting
Easy to use audio controls in the meeting room, content and participant views.
When sharing programs, users can select multiple programs to share
upload presentations that contain video clips by uploading the PowerPoint file.


 

Lync-Skype connectivity



Enabling Lync and Skype to connect to one another, enterprise IT can continue to manage a unified communications infrastructure without constraining the reach of end users. 
Lync Server supports connectivity with Skype. This connectivity allows Skype users and Lync users to add each other as contacts, exchange instant messages and make audio calls. Skype connectivity allows your Lync Server users to add Skype contacts using the Skype user’s Microsoft Account (MSA). Skype clients can add Lync users to their contact list. Based on policies administratively set in Lync Server, Lync and Skype users will be able to communicate using instant messaging, see each other’s presence, and initiate audio calls.

What do Lync administrators need to do to get started?
1.       To connect their Lync users with the Skype community, Lync administrators first need to enable Lync-Skype connectivity. 
2.       For Lync Online, connectivity can be turned on from the Lync admin center within the Office 365 portal. 
3.       If you already have Windows Live Messenger federation working, no additional steps are necessary to enable Lync-Skype connectivity.
4.       If you have Office 365 Small Business Premium, sign in to Office 365, and go to Admin > Service Settings > Instant messaging, meetings and conferencing.  Turn on External communications.

What about end users?
Lync users can connect to Skype from Lync 2010 or Lync 2013, including any of the 2013 mobile clients.
1.       Skype users will need the latest Skype client available from Skype.com
2.       Lync-Skype connectivity is supported from the Windows and Mac desktop clients with more options coming soon as other clients are updated.
3.       Skype users must sign in to Skype with a Microsoft account (formerly Windows Live ID) to communicate with Lync contacts

As per Microsoft the Lync - Skype provisioning process can take up to 30 days to complete.
To provision Lync - Skype connectivity, you need the following information:
Ø  Microsoft Agreement Number
Ø  Access Edge service fully qualified domain name (FQDN)
Ø  Session Initiation Protocol (SIP) domain(s)
Ø  Any additional Access Edge service FQDNs
Ø  Contact information
To initiate the provisioning process for Lync - Skype connectivity:
Ø  Sign in to the website, https://pic.lync.com, using your Microsoft Windows Live ID.
Ø  Select the Microsoft licensing agreement type.
Ø  Check the box verifying that you have read and accept the Product Use Rights for Lync Server.
Ø  On the Initiate a Provisioning Request page, click the appropriate link to initiate a provisioning request
Ø  On the Specify Provisioning Information page, enter the Access Edge service FQDN.  For example, accessedge.contoso.com.
Ø  Enter at least one or more SIP domain names, and click Add.
Ø  In the list of Public IM Service providers, select Skype and click Next to add Contact information, and submit the provisioning request.
Once the provisioning request has been submitted, it can take up to 30 days for the account to activate and users are enabled for public IM connectivity.


Configure federation and PIC
Federation is required to enable Skype users to communicate with Lync users in organization. Public Instant Messaging Connectivity (PIC) is a class of federation, and must also be configured to allow your Lync users to communicate with Skype users. Federation and PIC are configured using the Lync Server Control Panel, shown below.


Configure at least one policy to support federated user access
Using the Lync Server Control Panel, an administrator must configure one or more external user access policies to control whether Skype users can collaborate with internal Lync Server users.


 Reference :TeamBlog