What are they and why does it matter? On-Premises vs. Hosted or Managed Service What features are required? 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 Feature Lync Server Lync 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 1000 250 Meeting Size Feature Lync Server / Lync Split domain onpremise 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 Lync Split domainOnline Users OCS 2007 R2 Lync 2010 Migrations Third party telephony systems Messaging or Exchange UM considerations When should I choose an "On-Premises" solution? Lync Server performance on virtual topologies can vary greatly depending on the workloads being used, the number of users, and the host hardware. Web conferencing, A/V conferencing, Dial-in conferencing 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 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. Whether with corporate users who are connecting externally or federated partners & customers 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 Enable users to have real time conversations that can persist over time. Synergistically enhancing features (Exchange UM) enable users to receive/listen to voicemail, and integrate the personal contact stores (requires Exchange 2013) Ensure service resiliency for voice http://go.microsoft.co m/fwlink/p/?LinkID=39 1837 Topology is defined as a branch of mathematics concerned with those properties of geometric configurations unaltered by elastic deformations Topology is defined as the configuration or “design” of an organism or system Topology is defined as the arrangement of various elements (links, nodes, etc…) of a computer network. The configuration formed by the connections between devices on a local area network (LAN) or between two or more LANs. Deployment Options On-Premises Lync Server 2013 Preview Private cloud / dedicated 13 Hybrid Single domain and directory Users split – server / online Cloud Microsoft Office 365, Lync Online Partner-hosted multi-tenant When should I consider an on-premises deployment? An on-premises deployment is best when… An on-premises deployment is best when… On-premises Active Directory FIM Server Directory Syncronization Lync Server AD Resource forest AD user forest Lync Server AD Resource forest Directory Syncronization AD user forest FIM Server AD user forest Dirsync ADFS Exchange Server Lync Server AD user forest Voice Mail When should I consider an online deployment? An online deployment is best when… Lync online + Exchange online -> limited functionalities Lync online + Exchange onprem -> UM and Exchange archiving not supported Business Voice -> Enterprise Voice in the Office 365-S cloud Syndication partners -> Previously called Lync to phone Single user forest + multiple Office 365 tenants (per region) Multiple user forest + multiple Office 365 tenants Multiple onprem user forest + single Office 365 tenant On-premises Subscription Active Directory Lync Online Windows Azure Windows Azure Active Directory Tenant Directory synchronization When should I consider a hybrid deployment? Dirsync ADFS Lync Server Lync Server AD user forest Lync 2013 Hybrid Deployment Requirements Server Deployment Component Office 365 DirSync 31 Description Notes Synchronization of on-premises Active Directory with Office 365 Common requirement with Exchange Active Directory Federation Single sign-in (SSO) authentication infrastructure; end Services (AD FS) 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 Coexistence between online and onon the federation framework premises IM/Presence Conferencing Lync 2013 admin interface Cross-premise migration is available through Lync Management Shell Lync 2013 pool for Hybrid Voice features Hybrid Voice with E911 and Media Bypass require that a Only required for these two specific Lync 2013 pool/server be deployed on-premises hybrid voice features Admin interface can be used to move 2010 or 2013 users directly to online Multitenant Hybrid / Split Domain Single tenant Multi-Tenant Public Cloud Unified Communications Office 365 Public Cloud Hybrid or Split domain Onprem / Private cloud Doesn’t work between onprem and Office 365-D Doesn’t work between onprem and Service provider clouds Doesn’t work between Service provider clouds Enterprise customers only Part of the user population only needs basic features Online customers that need to enable UC applications for online users Video interoperability for online users through hybrid setup Migration scenario to the cloud Part of the user population only needs basic features “Jajah Voice”, the Lync-to-phone service provider for Office 365, was discontinued August 31, 2013. 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 provider No guidance from Microsoft Cloud – SIP Provider Conf Number -1-800 111 2222 PSTN Access SIP Carrier PSTN Access PBX Customer Site Site Customer MSFT Carrier Peer Point SBC 2 FOREST TOPOLOGIES AD TOPOLOGY LYNC EXCHANGE MIGRATION PATH FROM ONPREM TO HOSTED SUPPORTED NOTES TOPOLOGY 1 CUSTOMER’S AD IS PHYSICALLY DEPLOYED OFFICE 365 SHARED EXTENDED TO SP CLOUD IN SP DATACENTER (HOSTER 1) LOGICALLY DEPLOYED IN CUSTOMER’S AD TOPOLOGY 2 CUSTOMER AD PHYSICALLY DEPLOYED OFFICE 365 EXTENDED TO SP CLOUD IN SP DATACENTER DEDICATED (HOSTER 1) LOGICALLY DEPLOYED IN CUSTOMER’S AD SUPPORTED FULLY SUPPORTED BY MICROSOFT TOPOLOGY 3 CUSTOMER AD PHYSICALLY DEPLOYED EXCHANGE IN A 3RD SUPPORTED EXTENDED TO SP CLOUD IN SP DATACENTER PARTY SERVICE (HOSTER 1) PROVIDER (HOSTER 2) LOGICALLY DEPLOYED IN CUSTOMER’S AD FULLY SUPPORTED BY MICROSOFT TOPOLOGY 4 SP CREATES A DEDICATES PHYSICALLY DEPLOYED RESOURCE FOREST IN IN SP DATACENTER THE SP CLOUD TO HOST LOGICALLY DEPLOYED IN LYNC (HOSTER 1) A DEDICATED RESOURCE FOREST FULLY SUPPORTED BY MICROSOFT 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 Requirements 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 Lync Onprem Lync online ** Lync Online Office 365-D Service provider / Single tenant * Service Provider / Multitenant * 3 FOREST TOPOLOGIES AD TOPOLOGY LYNC TOPOLOGY 5 SP CREATES A DEDICATED RESOURCE FOREST IN THE SP CLOUD TO HOST LYNC (HOSTER 1) PHYSICALLY DEPLOYED OFFICE 365 IN SP DATACENTER. SHARED SP CREATES A DEDICATED RESOURCE FOREST IN THE SP CLOUD TO HOST LYNC (HOSTER 1) PHYSICALLY DEPLOYED OFFICE 365 IN SP DATACENTER. DEDICATED SP CREATES A DEDICATED RESOURCE FOREST IN THE SP CLOUD TO HOST LYNC (HOSTER 1) PHYSICALLY DEPLOYED EXCHANGE IN A IN SP DATACENTER. 3RD PARTY SERVICE LOGICALLY DEPLOYED PROVIDER IN A DEDICATED (HOSTER 2) RESOURCE FOREST TOPOLOGY 6 TOPOLOGY 7 EXCHANGE LOGICALLY DEPLOYED IN A DEDICATED RESOURCE FOREST LOGICALLY DEPLOYED IN A DEDICATED RESOURCE FOREST MIGRATION PATH FROM ONPREM TO HOSTED NOTES NOT SUPPORTED. BIG BANG NOT SUPPORTED BY MIGRATION APPROACH MICROSOFT DUE TO 3 WILL BE NEEDED DUE TO FOREST EXISTENCE THE LACK OF SPLIT DOMAIN NOT SUPPORTED. BIG BANG NOT SUPPORTED BY MIGRATION APPROACH MICROSOFT DUE TO 3 WILL BE NEEDED DUE TO FOREST EXISTENCE THE LACK OF SPLIT DOMAIN NOT SUPPORTED. BIG BANG NOT SUPPORTED BY MIGRATION APPROACH MICROSOFT DUE TO 3 WILL BE NEEDED DUE TO FOREST EXISTENCE THE LACK OF SPLIT DOMAIN as Lync Server 2013 on premises, or Lync Online with Microsoft Office 365 in the cloud. Business drivers provide requirements that will determine topology Short and long term strategy & statements of direction I.E. Virtualization, moving to a cloud consumer model, Business drivers provide requirements that will determine topology Breakout Sessions OFC-B341 Microsoft Lync Online Hybrid Deep Dive OFC-B337 Deploying and Managing Microsoft Lync Server 2013 Enterprise Voice EXM05 Exam Prep: 70-336 and 70-337 - MCSE: Communications (Microsoft Lync Server 2013) Find Me Later At. . . Microsoft Solutions Experience Location (MSE) http://channel9.msdn.com/Events/TechEd www.microsoft.com/learning http://microsoft.com/technet http://microsoft.com/msdn