Post on 13-Feb-2016
description
transcript
New Features Lync 2013
Peter Imhof
Integrated System
Persistent ChatAccess through unified Lync clientIntegrated in Lync Server ArchitectureHighly availableCompliant
Unified client Connects anywhere to persistent chat roomsLarge rooms supportUnified Lync administrationDisaster recovery supportCompliance database option available
Registration, presence (SIP)persistent chat (XCCOS)
Registration, presence (SIP)persistent chat (XCCOS)
Lync persistent chat pool
Lync edge
Reverse proxy
Lync FE pool
AD
Mirrored SQL
Persistent chat (XCCOS)
SQL
SQL SQL
Video ConferencingPrime time video conferencingBuilt-in Front-End componentSoftware based reducing the cost of conferencingInteroperable for investment protection
High-definition qualityMultiple video streamsSwitched or pinned contactsSmart croppingActive speaker detection and indicationSupport of H.264 and VC-1 for third party videoconferencing and telepresence interoperability
How is SVC Different?Lync 2010/Office Communications
ServerLync
A/V MCUActiveSpeaker
PreviousSpeaker
Other Attendees
Traditional Video Conferencing
VC MCU
How is SVC Different?1
2
3
4
5
6User 2 puts User 1 in full screen
User 1’s Lync client sends low + high res streamsMCU sends full stream to
User 2
MCU continues to send low resolution streams to all other users
Initially, all users are sending a single stream of video and receiving streams of up to 5 other participants
Web ConferencingImmersive virtual meetingInnovation through softwareReduce cost of the networkImprove scale and reachLync 2013 Web App for web based meeting.
Application sharing, audio/video through browser plug-in
Microsoft Office Web Application Companion Server
One-click Lync meeting scheduling from Exchange OWA
Reverse proxy
Edge server
AD
WAC
EE pool
SQL
*New in Lync Server 2013 and Office 2013
SIP and Media traffic traffichttp
Lync Edge server required to enable inbound/outbound SIP traffic – the same edge server enables remote work for employees and Lync Meetings with external parties Domain activated via MicrosoftAll media and signaling encrypted over public internetCan also be enabled for Lync Online
SQL
ADLyncEdge Server
Audio Gateway
MSNPGateway(IM/P, Contacts)
SIP - TLS
G.722 RTP
MSNP
LyncFederationServiceEdge
On-Premises Lync Server Deployment
Microsoft Cloud
Skype Federation
Step 1:
PROVISIONStep 3:
CONFIGURE CONNECTIVITY AND POLICIES
Step 2:
EDGE SET UP
Provision for Skype ConnectivityGo to https://pic.lync.com and provision your domainThis tells our service where to send inbound messages and informs Skype & Messenger that your Lync domain is available for connectivity
Skype connectivity capabilities by edition
1. Skype end users must have a Microsoft account associated with their Skype ID2. Update of cloud service to enable audio calling may not release concurrently with
Skype 6.x 3. Carryover from Windows Live Messenger (WLM). Functional but not supported. As
part of the migration from WLM to Skype, Skype 6.0 allows signing in with a Microsoft Account (i.e., the same credentials as WLM). After simply signing in to Skype with a Microsoft Account, associated WLM buddy lists automatically populate into Skype. This includes any WLM users’ federated Lync contacts. Lync customers do not need to do anything to enable this continuity of service.
Lync 2013Lync (Windows Store App)Lync 2013 for Windows Phone 8Lync 2013 for iOSLync 2013 for AndroidLync 2010
Skype for Windows 6.3+ Skype for Mac 6.3+
Supported clients
https://support.skype.com/en/faq/FA12124/what-happens-when-i-sign-in-to-skype-with-my-microsoft-account
Demo
Skype Federation
Skype – Lync Authentication and Contacts• LiveID account types and SIP addresses
• Microsoft Accounts: msn.com, hotmail.com, live.com, outlook.com, etc…
• EASI ID (The Acronym “EASI” stands for “email as sign in” as per KB2566829)For example, a user having a mailbox in your organization can have an EASI ID joe@fonstone.com
• The EADI ID is NOT a SIP or SMTP address… It is used only for authentication.
• If it has to be used for IM and presence, its corresponding SIP address is joe(fonstone.com)@msn.com
• Remember the Skype – Lync Federation only works if the Skype account is signed in with the Microsoft account (LiveID)
MobileExtend Lync mobile reach with UC Web AccessMobile Enterprise grade unified communicationSingle client and user identity
Built-in Front-End web services based on REST APIsSingle client for Online and On-premise, reducing the complexity of deploymentActive Directory based authenticationOptimized for battery and bandwidth usageVOIP, Video over IP or PSTN callbacks.
Media for callbackSIPhttps (XML)Push notification for Windows Phone
Voice/Video over IP
VOIP App notifications for iOS
Media gateway
Media server
Lync server
Reverse proxy
DMZ
GSM
WiFi
Internet
Lync push notification
services
Edgeserver
Enterprise Voice• Enterprise grade
telephony.• Built-in
component, no other server required.
• Scale with voice like other workloads
• Centralized management, distributed.
New in Lync 2013
Inter-Trunk RoutingM:N Trunk RoutingCaller ID TranslationUnassigned Number Range handlingE.911 ImprovementsNew Conference PSTN Dial-Out policiesResponse Group Managers RolesNew Call Forwarding and Simultaneous Ringing optionsVoicemail escape Delegates Simul-RingVoice Services resiliency through HA/DR
Introduction to Lync Topologies
Single Server SystemStandard Edition server runs all workloadsNo other server required to additional functionalitiesAll in one box deploymentIdeal for proof of concept, pilot, small and medium businessesFunctionality: IM, Presence, Voice, Video, Conferencing, MobilityPSTN access with Gateway, Direct SIP or SIP TrunkHA/DR if paired with another SE server
AD
Standard edition
Optional backup Standard editionPairing
Scalable Server PoolsEnterprise Edition Front End poolBack End Server with SQL Server
Ideal for large and medium size businesses, regional deployment.Scale up by adding up to 12 FE servers in a poolCollocate Archiving DB, Monitoring DB, PChat DBs on Back End ServersHigh Availability by FE failover and Mirrored Back End Servers
Enterprise edition front end servers
SQL
AD
Lync 2010 pool8 Front-Ends, tightly coupled back end
Lync 2013 pool12 Front-Ends, loosely coupled store
Higher Scale ArchitectureNew loosely coupled architecture and SQL MirroringData, Presence stored and synchronized across Front-endDistributed users and services across the Front-EndsBuilt-in pool high-availability
SQL DBbusiness logic
SQL
DB used for presence updates,
subscriptions
Dynamic data: presence updates handled on FEs
SQL
Storage
1..8 FE
1..12FE
Lync 2013 HA Model10 FE + tightly coupled back end
Capacity: 10 servers/pool 80,000 concurrent users/pool
Capacity: TBD – Will be published at product release
Evaluating 12-20 servers per pool
Lync 2013 Preview (FE s+ loosely coupled Back-end store)
SQL® Server database (DB) bottleneck –
business logic
Blob StorageDB used for storing “Blobs” – persisted store
DB used for presence updates and subscriptions
Dynamic data: Presence updates handles on FEs
Lync 2010 Pool Lync 2013 Preview Brick Pool
1-10 Front End Servers 1-N Front End Servers
19
High Availability
User Group
1
User Group
2
Group 1Group 3Fabric
node
Group 2
Fabric node
Group 1
Fabric node
Group 3
Fabric node
Group 3
Fabric node
Group 1
Fabric node
Group 2
Group 2
20
Front End
Windows Fabric is installed on each Front End
Users are provisioned to a pool in Routing Groups
Via fabric, three replicas of routing group data are kept updated
High Availability - Architecture• Lync Users are automatically mapped to “Groups”• Each “Group” is dynamically assigned to 3 Front-end servers within a
Pool (a Primary, a Secondary and a Tertiary).• When a user logs in, the Primary server will start servicing all of the
user’s requests. • Changes to the user’s data (such as Contact list changes) will be
synchronously replicated to secondary/tertiary as well (3 replicas).• If a primary server dies, then this group would fail over to the
secondary. (No data loss)• Writes to the back-end database occur periodically (not synchronous).• When a server dies, all the “Groups” assigned to that server as will
failover to different servers (load balancing).
High Availability – How does it work?
• Bob is homed on FE1 (primary) • There are 3 copies of this user’s
data: 1 primary (FE1), 2 backups (replicas in FE2, FE3)
• User is signed in to primary• User’s activities, data are
replicated
Pool Back-end
FE1FE2 FE3
• Primary goes down• User re-signs to one of the backups• Replicated data is available on FE2.
UserBob
Site FailurePool Failure
Disaster Recovery
Two pools can be “paired”
Backup agent on a Front End writes deltas to a DFS share
DFS replicates share content between Lync pools
Same as “pool failure”, but applied to geographically distinct pools
Disaster Recovery – Data Replication
Pool 1 Pool 2
Disaster Recovery – Pool FailoverPool pairing in Lync 2013:Enables Active-Active mode for two properly sized pools within the same datacenter
Provides real-time persistent data replication between paired pools via Backup Service
Failover and Failback are not automated
Disaster Recovery“Pool pairing” enables Active-Active mode for two properly sized pools within the same datacenter
Backup Service provides real-time persistent data replication between paired pools
Pool Failure
Same support as for pool failure as above for Lync 2013 pools but with pools in geographically distributed data centers
Supported for Lync 2013 pools only
Site Failure
Edge signaling independent of media
Contoso
US EU
User homed in
EU
User will always use this pool for AV Edge
Also for meetings
created by user
Edge Federation flows
Contoso
US EU EU
Litwareinc
Edge Pool used for
Federation
User homed in
EU
User will always use this pool for AV Edge
Edge Pool used for
Federation
Migration
Legacy pool
SQL
Legacy director
Legacy edge
Production Pilot
Legacy and latest remote access.
Legacy and latest federation.
ADLatest pool
SQL
Latest director
Latest edge
Latest remote access.Install new server or new client first,
your choice.Multiple version of Lync server in the same infrastructure.Move users across pool with no users loss of data.Allows seamless migration for users.
Redeploy Survivable Branch Appliances• Move branch users to another pool• Remove Lync Server 2010 SBA from
topology• Add Lync Server 2013 SBA to topology and
configure FE pool as Backup Registrar• Move users back to the new SBA
Mobility CoexistenceLync Server 2010
with Mobility Service
Lync Server 2013 (prior to CU1 update)
Lync Server 2013, CU1 –
Mobility Enabled
Lync Server 2013, CU1 –
Mobility Disabled
Lync 2010 mobile clients
Notification to upgrade to the latest version of
the mobility client.
Error: “Can’t sign in because you are not setup to use
Lync 2013. Please contact your
support team.””
Lync 2013 mobile clients
Error: “You can't sign in with this version of Lync.
Please install Lync 2010.”
Error: “You can't sign in with this version of Lync. Please install Lync 2010.”
Error: “Can’t sign in because you are not setup to use
Lync 2013. Please contact your
support team.””
Deployment Choices
Lync Server
Lync Online
Hybrid
Lync On-PremiseBenefits from all Lync Server functionalities
Maximum flexibility
Interoperate with other on-premise investments
Works with Exchange and SharePoint Online
Lync Server
Lync Online
Hybrid
Hybrid DeploymentThe cloud on your terms
No radical changes
Less complexity
Leveraging on-premise investments