Skype vs Skype for Business The consumer experience that people around the world know and love will continue to be referred to as Skype for Business brings together the familiar experience and user love of Skype with the enterprise security, compliance, and control from Lync End users get a familiar Skype experience that is as easy to use at work as it is at home
What is a successful deployment?
Deployment options Do you feel lucky? Supported Topologies Focus of today’s session Recommended Topologies Reference Architectures Structured Topology Standardized Topology O 365 MT
Deployment choice Online Hybrid Server
Decision tree Yes No Some new investments will require hybrid even for on premises customers Yes No
Skype for Business Online Exchange Online Skype for Business Online Azure AD Directory Synchronization O 365 MT Customer User AD Customer AD
Skype for Business Online All users are in a single user forest There are no resource forests present Also, there is only a single user forest Single O 365 tenant Exchange is provided via O 365 Skype for Business on premises can be introduced later with hybrid
Skype for Business Hybrid Split Domain Exchange Online Azure AD O 365 MT Skype for Business Online Directory Synchronization Skype for Business Server Customer User AD Customer AD
Skype for Business Hybrid All users are in a single user forest There are no resource forests present Also, there is only a single user forest Skype for Business on premises is deployed in the user forest Exchange Skype for Business users online consume Exchange via Exchange Online Skype for Business users on premises consume Exchange either online or on premises Important Federation and login via Skype for Business on premises environment
Skype for Business On Premises Skype for Business Server Customer User AD Customer AD
Skype for Business On Premises Skype for Business deployed in user forest Exchange is provided either via Exchange on premises in user forest Exchange Online Exchange Hybrid Skype for Business hybrid can be enabled later
Three-forest architecture Motivation Enable partners to host Lync 2013 for customer Provide full Lync on premises feature set while consuming Lync as a service Consume Exchange from O 365 MT Documentation Whitepaper published September 2014 Deploying Lync in a Multi-Forest Architecture (Partner Hosted Lync with Exchange Hybrid) http: //www. microsoft. com/en-us/download/details. aspx? id=44276 Tech. Ed session Microsoft Lync Deployment Options and the Multi-Forest Architecture http: //channel 9. msdn. com/Events/Tech. Ed/Europe/2014/OFC-B 412
Three-forest Directory Synchronization Azure AD Exchange Server User Forest Customer User AD FIM Exchange Online Lync Server O 365 MT Resource Forest AD
Three-forest status Supported for Lync 2013 Since September 2014 Very complex Three different forests interacting Trust required between resource and user forest Directory synchronization user forest and resource forest (FIM) Directory synchronization user forest and O 365 (Dir. Sync) Only topology that allows combination of Lync in resource forest Exchange in O 365 (pure or hybrid) Alternatives Can customer AD be extended to partner datacenter?
Recommendations Skype for Business O 365 MT Single Tenant in O 365 MT Single user forest No resource forests Skype for Business Hybrid Single Tenant in O 365 MT Single user forest No resource forests Skype for Business on premises Single user forest No resource forests
Pool decision tree no yes no yes
Enterprise Edition pool Three Front Ends minimum Two Front Ends supported but not recommended Very specific steps required, if you need to restart your pool or servers Use Hardware Load Balancer for HTTP Never lose two (or more) servers at the same time Consider failure domains when placing servers
Routing groups Each user is part of exactly one routing group Placement during user provisioning Will change when servers are added to pool (or removed) Holds information about this user Presence, Contacts, Groups, Voice Settings, Conferences, … Each routing group has three replicas One Primary Two secondary If one replica is lost, pool will recover If two replicas are lost, replica will lose quorum
Upgrade domains What is it? Front End pools are organized in Upgrade Domains Idea: All servers of a single upgrade domain can be offline without impacting availability Routing groups are distributed to accomplish this goal Initial Pool Size Number of Upgrade Domains Front End Placement per Upgrade Domain 12 8 First 8 FEs into 4 UD with 2 each, then 4 UD with 1 each 9 8 First 2 FEs into one UD, then 7 UD with 1 each 8 8 Each FE placed into its own UD 5 5 Each FE placed into its own UD
Pool quorum Pool will go offline if less than 50% of Front End servers are available Pool will also go offline if exact 50% are online but SQL database is not Total Number of Front End Server in the pool (defined in Topology) Number of Servers that must be running for pool to be functional 2 1 3 -4 Any 2 5 -6 Any 3 7 Any 4 8 -9 Any 4 of the first 7 servers 10 -12 Any 5 of the first 9 servers
Fault domains “A fault domain is a set of hardware components – computers, switches, and more – that share a single point of failure. “ – IEEE Computer Magazine March 2011 Issue Never lose two* Front End Servers at the same time! *Except if they are part of the same upgrade domain You cannot configure your upgrade domains Use an n+1 model when planning your pools
Metropolitan and Lync 2013/Skype for Business Not supported and will not provide HA Pool quorum is not the main issue Routing groups will be negatively impacted As soon as one datacenter is unavailable, users will be impacted Instead of higher availability, it will be lower Solution Don’t do Metropolitan! Use paired pools
Front End: Disaster Recovery Use paired pools Geo. DNS Get sure that simple URLs and lyncdiscover still work
Disaster Recovery: Too close? What disaster to protect against?
Front End: Too far? What is the latency? Remember: ITU recommends 150 ms mouth-to-ear Consider conferencing scenarios What is your bandwidth? What are your SLAs?
SQL back end database Same location as FE servers High Availability SQL mirroring One mirror server Use SQL witness “Feature Not Supported in a Future Version of SQL Server” SQL Always. On Runs on top of Windows Server Failover Clustering Up to three Secondary Replicas SQL Enterprise required for more than one replica Disaster Recovery Via pool failover
File Share Used for meeting content, address book files Same location as FE servers High Availability Distributed File Share (DFS) Disaster Recovery Via pool failover
Office Web App Server Used for Presenting Power. Point Same location as Front End pool High Availability Pool of OWAS Hardware Load Balancer recommended Disaster Recovery Via pool failover
Monitoring Server Database Used for Collection Quality of Experience and CDR data Runs SQL Server Reporting Services and the Server Monitoring Reports Globally one Monitoring database Complete view on your data For performance you might want to copy data to a second database and run reports against the second High Availability Via SQL
Edge Server In Hybrid, on premises environment required for sign-in! High Availability is crucial Used for Remote Access, Federation, O 365 Integration Same location as Front End pool High Availability Pool of Edge Servers DNS Load Balancing recommended Disaster Recovery Via pool failover Hardware Load Balancing recommended if Federation with OCS 2007, OCS 2007 R 2 Exchange UM 2007 or Exchange UM 2010 Legacy clients
Reverse Proxy Used for Meeting join, mobile clients, file download Same location as Edge Server Qualified Reverse Proxies to be published on Tech. Net High Availability Depends on Reverse Proxy solution Disaster Recovery Via pool failover
Mediation Server Connection to PSTN next hop Placement depends… With media bypass can be in datacenter Without media bypass: next to PSTN next hop High availability Pool of mediation servers Disaster Recovery Multiple pools, multiple voice routes
Mediation Server: co-location Depends on the load on Mediation Server Calls with Media Bypass put very little load on Mediation Server Some type of calls will never leverage media bypass Calls to/from external users via Edge Conference dial-in/dial-out Calls controlled by Call Admission Control Dual homed mediation Needs to be dedicated Mediation Server
SBA, SBS Survivable Branch Appliance/Server Place next to PSTN next hop Qualified devices to be published on Tech. Net High availability Multiple gateways User services provided by Front End Pool Disaster recovery SBA/SBS users will have only limited functionality mode in pool failover
Call Quality Dashboard (CQD) Your next generation call quality reports!
Call Quality Dashboard Components Archive Database Quality of Experience (Qo. E) data is replicated and stored Qo. E Cube Archive DB is aggregated for optimized and fast access Reporting Web Portal Query and visualize Qo. E data Recommendation Sizing to be determined Requires SQL Enterprise or Business Intelligence
Video Interoperability Server (VIS) Used for Integration in VTC and video gateways Place next to video next hop Qualified devices to be published on Tech. Net High availability VIS pool Skype for Business facing: DNS LB Video next hop facing: multiple trunks, DNS LB Disaster Recovery Does your video next hop still exist? Trunks to multiple pools Will connect to failover Front End pool
“The waterfall” ]! Collect requirements g n Calculate server sizing o r Deploy servers W [ Live happily ever after
Sizing numbers Supported users per server This is based on recommended hardware This is based on a very specific user model Useful as a starting point Need to be closely monitored and adopted
Healthy planning cycle Size servers Monitor Server health Deploy Enable users
Examples from user model User models in Lync Server 2013 http: //technet. microsoft. com/en-us/library/gg 398811. aspx Category Description Peer-to-peer IM sessions Each user averages six peer-to-peer IM sessions per day. 10 instant messages per session. Meeting concurrency 5% of users will be in conferences during working hours. Media mix for conferences 75% of conferences are web conferences, which include audio plus some other collaboration modalities. 50% add application sharing. We assume one users sends data at a peak of 1. 1 MB per second. 50% add instant messaging (with an average of 2 messages per user). 20% add data collaboration, including Power. Point or whiteboard In these, an average of 2 Power. Point files presented per conference, with an average Power. Point file size of 10 MB (without embedded video) or 30 MB (with embedded video). Average of 20 annotations per whiteboard. 20% add video. Of these users, 70% are in conferences enabled for multiview video, where each user receives 2 -3 video streams. 15% add shared notes
Server sizing Server Lync 2013 Front End Server 6, 600 Edge Server 12, 000 Mediation Server 1500 concurrent calls Standard Edition Server 5000 Skype for Business li b u d e h s [to p e b ]
Server sizing: Conclusion Still testing Skype for Business for scalability Don’t assume same sizing as Lync 2013 Even with in-place upgrade Sizing numbers are a starting point Good monitoring needs to be in place Leverage Key Health Indicators (KHI) (http: //go. microsoft. com/fwlink/p/? Link. ID=390677) Scale out when required Stress and load testing is a great idea!
In. Place Upgrade More convenient upgrade path from Lync Server 2013 to Skype for Business by: § Preserving existing hardware/server investments § Smoother upgrade process without extensive planning § Reducing the overall cost for deployment § The goal of heading towards Smart Setup Upgrade Path Original Topology New Topology In-Place Upgrade Supported ? Lync 2013 Sf. B + 2013 Yes. In-Place upgrade support from 2013 -> Sf. B Lync 2010 Sf. B + 2010 No. Upgrade from 2010 -> Sf. B , Same as 2010 -> 2013 Lync Coexistence (2013 + 2010) Sf. B + 2013 Mandatory migration from 2010 -> 2013 before deploying Sf. B. Then In-Place upgrade from 2013 to Sf. B
Server Operating System Operating system selection impacts the installed version of Windows Fabric during setup: Operating System Windows Server 2008 R 2 Windows Server 2012 R 2 Installed version of Windows Fabric v 2 Windows Fabric v 3 Recommended OS: Windows Server 2012 R 2 § Windows Fabric v 3 is incompatible with Windows Server 2008 R 2 § Latest fixes for Windows Fabric may not be available for older operating systems
SQL Always. On SQL Server Always. On HA Solutions Next generation of Database Mirroring technologies Provides High Availability and Disaster Recovery in SQL Introduced in SQL Server 2012 and present in SQL Server 2014 Runs on top of WSFC (Windows Server Failover Clustering) Always. On Advantages Latest and Greatest SQL HA solution Although database mirroring is still available in its original feature set, it is now considered a deprecated feature and will be removed in a future release of SQL Server. More Reliable Always. On (One Primary, can have up to three corresponding Secondary Replicas) Mirroring (One Primary, One Mirror) Multi-Database Failovers Useful in applications with several databases Databases can be added to an Availability Group that can be failed over between replicas All databases in Availability Group are failed over at the same time
Bringing it all together Consider the full lifecycle Forests matter The simpler the better Metropolitan does not provide HA Be aware of failure and upgrade domains Sizing is not a one-time activity