What features are required? FeatureLync ServerLync Online Rich presence Peer-to-Peer Audio/Video...
-
Upload
sarah-marshall -
Category
Documents
-
view
216 -
download
0
Transcript of What features are required? FeatureLync ServerLync Online Rich presence Peer-to-Peer Audio/Video...
Microsoft Lync Server 2013 TopologyChristopher WallickCommunications Architect Enterprise Communications Center of Excellence
OFC-B346
AgendaLync Features ComparisonInitial Planning Considerations Lync topologiesWhat are they and why does it matter?
Single or Multitenant On-Premises vs. Hosted or Managed Service
Hybrid Topology Service Providers O365 Multi-TenantTopology Choice Q&ASummary
Lync FeaturesWhat features are required?
Lync Server, Lync Online: IM/Presence
Feature Lync Server
Lync Online
Rich presence ü ü
Peer-to-Peer Audio/Video Calling ü ü
Click to Communicate—Office integration ü ü
Mobility Clients—Windows Phone, Android, iOS
ü ü
MAC Client ü ü
Federation with Lync/Lync Online ü ü
Skype Interop ü ü
XMPP Gateway ü
Persistent Chat ü
Federation with Yahoo/AOL ü
Lync Server, Lync Online: Meetings Feature Lync
ServerLync Online
Multi-Party PC Audio/Video ü ü
Ad-hoc meetings, Scheduled Meetings ü ü
Desktop Sharing, Application Sharing, Power Point
ü ü
Rich Client for Meetings ü ü
Mobile Clients for Meetings ü ü
Rich Client for Meetings ü ü
Reach Client for Meetings ü ü
PSTN Dial-in in Meetings ü With ACP Partners
Meeting Size 1000 250
Lync Server, Lync Online: VoiceFeature Lync Server
/ Lync Split domain on-premise users
Lync Split domain- Online Users
Peer-to-Peer & PSTN calling, Emergency Dialing, Voice Mail
ü
Call hold, Transfer, Forwarding, Delegation & Team Calling
ü
IP Phones, USB Peripherals & Mobile call via work ü
Direct SIP Interoperability with on-premises PBX ü
Private Line, Common Area Phones ü
Analog Devices, Enhanced 911 ü
Call Parking, Unassigned Number Handling ü
Call Center Integration & Response Groups ü
Network Resiliency, Call Admission Control ü
Where do we go from here? Most deployments are not “greenfield” OCS 2007 R2 Lync 2010 Migrations
Most deployments will have some sort of integration with ancillary communications systems Third party telephony systems Messaging or Exchange UM considerations
Initial Planning DecisionsOn-premises or online deployment? When should I choose an "On-Premises" solution?
Physical or virtualized topology?Lync Server performance on virtual topologies can vary greatly depending on the workloads being used, the number of users, and the host hardware.
Conferencing? Web conferencing, A/V conferencing, Dial-in conferencing
High availability?Enterprise Edition pools make it possible for Lync Server to continue functioning even if a server is unavailable. Standard Edition servers can be paired for high availability
Disaster Recovery?Pool pairing enables the servers at one datacenter to pair with a corresponding pool at another datacenter. If one datacenter goes down, the other pool in the pair can service users in both pools with minimum interruption of services.
Initial Planning DecisionsCommunicate and collaborate with external users? Whether with corporate users who are connecting externally or federated partners & customers
Enterprise Voice?EV provided a viable alternative to traditional PBX-based telephony systems where users will be able to place calls from their computer or desk phone
Persistent chat?Enable users to have real time conversations that can persist over time.
Microsoft Exchange deployed? Synergistically enhancing features (Exchange UM) enable users to receive/listen to voicemail, and integrate the personal contact stores (requires Exchange 2013)
branch offices in your organization? Ensure service resiliency for voice
This Slide can be found at http://go.microsoft.com/fwlink/p/?LinkID=391837
Lync topologies
Topology – What does that Mean?Webster’s Dictionary
Topology is defined as a branch of mathematics concerned with those properties of geometric configurations unaltered by elastic deformationsTopology is defined as the configuration or “design” of an organism or system
WikipediaTopology is defined as the arrangement of various elements (links, nodes, etc…) of a computer network.
Microsoft The configuration formed by the connections between devices on a local area network (LAN) or between two or more LANs.
Deployment Options
Microsoft Office 365, Lync OnlinePartner-hosted multi-tenant
Single domain and directory Users split – server / online
Lync Server 2013 PreviewPrivate cloud / dedicated
CloudHybrid On-Premises
Enabling gradual migration and coexistence between Lync private and public cloud
13
Lync On-PremisesWhen should I consider an on-premises deployment?
An on-premises deployment is best when… Full Enterprise Voice Capabilities
An on-premises Lync Server deployment is required if you are planning to replace your PBX or which uses advanced calling features.
Media Quality ControlsRequired for full range of media quality assurance features, (i.e. Call Admission Control (CAC) Quality of Service (QoS) )
Persistent Chat On-premises required
An on-premises deployment is best when… 3rd-Party Server Applications
Required to work with trusted 3rd-party applications that use the Microsoft Unified Communications Managed API (UCMA).
Multi-National/Multi-Regional Companies Needing Regional Support
Datacenters in multiple countries or regions and need servers to be deployed and managed on a regional basis
Complete control over policies, reports, and upgrades
full set of server & client policies, Monitoring reports, and control of upgrades.
Lync On-Premises Forest Models
Self managed Lync configuration Deploy and configure any and all workloads and features
Multiple AD topologies supportedLync in a single AD forestLync in a resource forest scenario + 1 user forestLync in a resource forest scenario + multiple user forest
Fully supported topologies:Lync onprem + Exchange onpremLync onprem + Exchange online
Single AD Forest ModelUsers and resources are in the same Forest.
On-premises
Active Directory
Single Resource and User Forest Scenario Users objects
are homed in a separate Forest One way Forest Trust from user forest to resource ForestDirectory SynchronizationFIM server
AD user forest
AD Resource forest
Lync Server
FIM Server
Directory Syncronization
Considerations & Guidance Can be used to provide a shared infrastructure for services in organizations that manage multiple forests or to separate the administration of Active Directory objects from other administration. Companies that need to isolate Active Directory administration for security reasons.
Single Resource Forest and Two User Forest ScenarioThe resource forest scenario with multiple user forests
AD user forest
AD Resource forest
Lync Server
FIM Server
Directory Syncronization
AD user forest
Considerations & Guidance Similar to Single user Forest model Additional Complexity around multiple Forests
Companies that need to isolate Active Directory administration for security reasons.I.E. regulatory requirements for information management & segregation Additional Complexity around multiple Required
Lync onprem + Exchange onlineSingle AD forest
AD user forest
Lync Server
Exchange Server Voice Mail
Dirsync ADFS
Internet
Lync onlineWhen should I consider an online deployment?
An online deployment is best when… Full Enterprise Voice Capabilities are NOT required
An on-premises Lync Server deployment is required if you are planning to replace your PBX or which uses advanced calling features.
Media Quality Controls are NOT requiredRequired for full range of media quality assurance features, (i.e. Call Admission Control (CAC) Quality of Service (QoS) )
Persistent Chat is NOT requiredOn-premises required
Lync onlineLync Online Multitenant (Office 365-S) is the Microsoft public cloud offering for LyncLync online topologies:
Lync online + Exchange online -> limited functionalitiesLync online + Exchange onprem -> UM and Exchange archiving not supported
Voice in the cloud:Business Voice -> Enterprise Voice in the Office 365-S cloudSyndication partners -> Previously called Lync to phone
Lync onlineA unique tenant can only exists in one Microsoft datacenterDoesn’t provide QoS or CACComplex topologies Lync online:Single user forest + multiple Office 365 tenants (per region)Multiple user forest + multiple Office 365 tenants
Not supported scenarios with Lync online: Multiple onprem user forest + single Office 365 tenant
Lync online
Subscription
On-premises
Windows Azure Active Directory Tenant
Lync Online
Windows Azure
Active Directory
Directory synchronization
Lync hybridWhen should I consider a hybrid deployment?
Lync onprem + Lync online = hybrid
AD user forest
Lync Server
Dirsync ADFS
Lync Server
Internet
Lync 2013 Hybrid Deployment Requirements
Component Description NotesOffice 365 DirSync Synchronization of on-premises Active Directory
with Office 365Common requirement with Exchange
Active Directory Federation Services (AD FS)
Single sign-in (SSO) authentication infrastructure; end users get Office 365 services with on-premises credentials
Common requirement with Exchange
Lync 2010+ Federation Edge
Interoperability between online and on-premises is built on the federation framework
Coexistence between online and on-premises IM/Presence Conferencing
Lync 2013 admin interface
Cross-premise migration is available through Lync Management Shell
Admin interface can be used to move 2010 or 2013 users directly to online
Lync 2013 pool for Hybrid Voice features
Hybrid Voice with E911 and Media Bypass require that a Lync 2013 pool/server be deployed on-premises
Only required for these two specific hybrid voice features
Server Deployment
31
Multi-TenantPublic Cloud
Unified Communications
Single tenant
Onprem / Private cloud
Lync hybrid or split domain
Hybrid / Split Domain
Hybrid or Split domain
Multitenant
Office 365 Public Cloud
Enabling gradual migration and coexistence between Lync private and public cloud
Lync hybrid or split domainIt is a configuration, not a topologyOnly works with Office 365 multitenant
Doesn’t work between onprem and Office 365-DDoesn’t work between onprem and Service provider clouds Doesn’t work between Service provider clouds
Hybrid as a permanent state:Enterprise customers onlyPart of the user population only needs basic featuresOnline customers that need to enable UC applications for online usersVideo interoperability for online users through hybrid setup
Lync hybrid ConsiderationsHybrid as a temporal state
Migration scenario to the cloudPart of the user population only needs basic features
To setup hybrid customer needs to start onprem first and then move users to the cloudHybrid voice was discontinued, no split workloads allowed
“Jajah Voice”, the Lync-to-phone service provider for Office 365, was discontinued August 31, 2013.
Service providersO365 Multi-Tenant
Service Provider HostedSingle tenant private cloud (SIs, Telcos, SPs, but also government agencies)Current challenges for the Service providers:
AD topology. Resource forest scenario is beneficial for the SP but leads to 3 forest and the necessity of split domain
No split domain with a service providerNo guidance from Microsoft
Customers that require full EV capabilities and want to go cloud today have the option to go to a service provider
Lync resource forest + Exchange online
The three forest topology limitationsExchange UM will not workTwo resource forest that don’t know anything about each otherManually keep the UM dial plan in sync with the Lync dial planTwo versions of the directory synchronization toolNo trust between the Lync and the Exchange forests
Service Provider Hosted
How do I choose my service provider:Geographical presentSLA/SLTService description3rd party applications enabledGlobal/Local support
Lync online Office 365-D
Lync Online DedicatedLync Online Dedicated (Office 365-D) is the Microsoft single tenant private cloud offering for LyncOnly targets customers over 30K seatsLync Online Dedicated tenant can expand multiple Microsoft datacentersOffice 365-dedicated known limitations:
No SBA/SBS supportNo CAC allowedNo interconnection with onprem PBX (only via onprem SBC)No split domain with customer onprem deployment
Lync Online DedicatedTopologies supported with Exchange Server:
Lync online dedicated + Exchange onpremLync online dedicated + Exchange online dedicated
Topologies not supported with Exchange Server:
Lync online dedicated + Exchange online Office 365-S
Lync online dedicated + Exchange hosted by a SP
Lync Online Dedicated – PSTN Connectivity options
Hybrid – Mix of SP & SBCCloud – SIP Provider On-premises - SBC
Lync Online Dedicated – EV Enabled
SIP Carrier PSTN Access
MSFT Carrier Peer Point
Conf Number -1-800 111 2222
Customer Site
PBX
SBCCustomer Site
PSTN Access
Choose the right topology
Supported topologies2 FOREST TOPOLOGIES
AD TOPOLOGY LYNC EXCHANGE MIGRATION PATH FROM ONPREM TO HOSTED
NOTES
TOPOLOGY 1 CUSTOMER’S AD IS EXTENDED TO SP CLOUD (HOSTER 1)
PHYSICALLY DEPLOYED IN SP DATACENTER
LOGICALLY DEPLOYED IN CUSTOMER’S AD
OFFICE 365 SHARED
SUPPORTED FULLY SUPPORTED BY MICROSOFT
TOPOLOGY 2 CUSTOMER AD EXTENDED TO SP CLOUD (HOSTER 1)
PHYSICALLY DEPLOYED IN SP DATACENTER
LOGICALLY DEPLOYED IN CUSTOMER’S AD
OFFICE 365 DEDICATED
SUPPORTED FULLY SUPPORTED BY MICROSOFT
TOPOLOGY 3 CUSTOMER AD EXTENDED TO SP CLOUD (HOSTER 1)
PHYSICALLY DEPLOYED IN SP DATACENTER
LOGICALLY DEPLOYED IN CUSTOMER’S AD
EXCHANGE IN A 3RD PARTY SERVICE PROVIDER (HOSTER 2)
SUPPORTED FULLY SUPPORTED BY MICROSOFT
TOPOLOGY 4 SP CREATES A DEDICATES RESOURCE FOREST IN THE SP CLOUD TO HOST LYNC (HOSTER 1)
PHYSICALLY DEPLOYED IN SP DATACENTER
LOGICALLY DEPLOYED IN A DEDICATED RESOURCE FOREST
EXCHANGE IS DEPLOYED IN THE SAME FOREST AS LYNC (HOSTER 1)
NOT SUPPORTED. BIG BANG MIGRATION APPROACH WILL BE NEEDED DUE TO THE LACK OF SPLIT DOMAIN
FULLY SUPPORTED BY MICROSOFT
Choose the right topology
Customer size (SMB vs Enterprise)Choosing the wrong topology may have an important impact in integration scenarios with other workloadsThere is NOW a migration path from Lync online to on-premisesUnderstand the service provider offering
Choose the right topology Technical requirements:
Enterprise VoicePSTN connectivity requirementsRemote site survivabilityPersistent Chat3rd party applications that live on top of LyncCall quality
Business requirements:Company strategyProduct roadmapChoose a topology that is cost effective for you
ExamplesRequirements Lync
OnpremLync online
Lync Online Office 365-D
Service provider / Single tenant *
Service Provider / Multitenant *
Full Enterprise Voice capabilities Full admin control
Capability of building 3rd party applications on top of Lync
Full call quality control
Opex model / Cloud strategy
Basic Enterprise Voice capabilities required **
* Understand the Service Provider service description
** Lync to phone, future EV in Office 365
Not supported or not recommended topologies
What topologies are not supported
Lync Server on Windows AzureTenant segregation with Lync Server Hybrid or split domain scenarios:
Lync Hosting Pack hybridLync hybrid with Office 365-DHybrid between two Lync Enterprise deployments
Multiple onprem user forest + single Office 365 tenantOffice 365-S tenant that expand multiple datacenters
Not supported scenarios3 FOREST TOPOLOGIES
AD TOPOLOGY LYNC EXCHANGE MIGRATION PATH FROM ONPREM TO HOSTED
NOTES
TOPOLOGY 5 SP CREATES A DEDICATED RESOURCE FOREST IN THE SP CLOUD TO HOST LYNC (HOSTER 1)
PHYSICALLY DEPLOYED IN SP DATACENTER.
LOGICALLY DEPLOYED IN A DEDICATED RESOURCE FOREST
OFFICE 365 SHARED
NOT SUPPORTED. BIG BANG MIGRATION APPROACH WILL BE NEEDED DUE TO THE LACK OF SPLIT DOMAIN
NOT SUPPORTED BY MICROSOFT DUE TO 3 FOREST EXISTENCE
TOPOLOGY 6 SP CREATES A DEDICATED RESOURCE FOREST IN THE SP CLOUD TO HOST LYNC (HOSTER 1)
PHYSICALLY DEPLOYED IN SP DATACENTER.
LOGICALLY DEPLOYED IN A DEDICATED RESOURCE FOREST
OFFICE 365 DEDICATED
NOT SUPPORTED. BIG BANG MIGRATION APPROACH WILL BE NEEDED DUE TO THE LACK OF SPLIT DOMAIN
NOT SUPPORTED BY MICROSOFT DUE TO 3 FOREST EXISTENCE
TOPOLOGY 7 SP CREATES A DEDICATED RESOURCE FOREST IN THE SP CLOUD TO HOST LYNC (HOSTER 1)
PHYSICALLY DEPLOYED IN SP DATACENTER.
LOGICALLY DEPLOYED IN A DEDICATED RESOURCE FOREST
EXCHANGE IN A 3RD PARTY SERVICE PROVIDER (HOSTER 2)
NOT SUPPORTED. BIG BANG MIGRATION APPROACH WILL BE NEEDED DUE TO THE LACK OF SPLIT DOMAIN
NOT SUPPORTED BY MICROSOFT DUE TO 3 FOREST EXISTENCE
Questions?
Summary
SummaryThe first major decision is how to deploy Microsoft Lync: as Lync Server 2013 on premises, or Lync Online with Microsoft Office 365 in the cloud.What features and capabilities are required?Business drivers provide requirements that will
determine topology What is your strategy?Short and long term strategy & statements of directionI.E. Virtualization, moving to a cloud consumer model, Business drivers provide requirements that will determine topology
“ Il semble que la perfection soit atteinte non quand il n'y a plus rien à ajouter, mais quand il n'y a plus rien à retrancher..”
Antoine de Saint-Exupéry
Breakout SessionsOFC-B341 Microsoft Lync Online Hybrid Deep DiveOFC-B337 Deploying and Managing Microsoft Lync Server 2013 Enterprise Voice
Related content
Microsoft Solutions Experience Location (MSE)
Related Certification ExamEXM05 Exam Prep: 70-336 and 70-337 - MCSE: Communications (Microsoft Lync Server 2013)
Find Me Later At. . .
Resources
Learning
Microsoft Certification & Training Resources
www.microsoft.com/learning
msdn
Resources for Developers
http://microsoft.com/msdn
TechNet
Resources for IT Professionals
http://microsoft.com/technet
Sessions on Demand
http://channel9.msdn.com/Events/TechEd
Complete an evaluation and enter to win!
Evaluate this session
Scan this QR code to evaluate this session.
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.