If so implement Lync successfully, it's a feel good product. I have never heard of so many happy users as when we succeed with Lync in an organization. I will go through 5 key elements of how to succeed with Lync and BYOD in a WiFi infrastructure.
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
Succeed with #Lync BYOD and WiFi
1. Succeed with Lync, BYOD and WiFi
Ståle Hansen
Lync MVP
Chief Technical Architect
2. When you do telephony, Lync will become a
true productivity tool
@StaleHansen
3. The Lync 2013 mobile client works on
Microsoft, Apple and Android operating systems
and is a strong solution for those
enterprises seeking a UC and telephony
client for their mobile devices.
Gartner 2014
Gartner Magic Quadrant for Corporate Telephony 2014
http://www.gartner.com/technology/reprints.do?id=1-23HXCI1&ct=141022&st=sb @StaleHansen
4. Clients report poor call quality,
dropped calls and system
outages in implementations that didn't
use a Lync integrator
Gartner 2014
Gartner Magic Quadrant for Corporate Telephony 2014
http://www.gartner.com/technology/reprints.do?id=1-23HXCI1&ct=141022&st=sb @StaleHansen
5. LAN Wi-Fi
Bring Your Own Device (BYOD)
Choose Your Own Device
Bring Your Own Disaster
@StaleHansen
10. Succeed with Lync, BYOD and WiFi
• Understand Lync Mobile media flow
• Make sure logon is simple
• Do unmanaged devices correct
• Optimize WiFi for Lync
• Evaluate security and authentication
@StaleHansen
13. Lync mobile sign in
• Lyncdiscoverinternal.domain.com
• Lyncdiscover.domain.com
• Lync Mobile is an UCWA application
• Will always connect to external web services
– Internal UCWA and Externa UCWA attributes is
reserved for future use
@StaleHansen
17. Lyncdiscoverinternal and certificates
• Lyncdiscoverinternal pointing to Lync Front-End
• If internal PKI is used
• Unmanaged clients typically don’t trust Root CA
• iOS clients will sign in fine
• Android clients will give a redirect warning
• Windows Phone will not be able to sign in
– Use public certificates on Front-End Server
– Or point lyncdiscover or lyncdiscoverinternal to external reverse
proxy
@StaleHansen
21. Do it right
EXCHANGE WEB SERVICES (EWS)
@StaleHansen
22. Outlook works perfectly with Exchange
Using SCP records to locate autodiscover
Lync client is introduced, no exchange integration works
THE CHALLENGE, ON-PREMISES
@StaleHansen
24. MAPI fallback when EWS fails
• Exchange delegation information (MAPI only)
• Missed Conversations history and Call Logs are written
– Retrieving conversation history fails
• Voice Mail count only
• Exchange integrated Archiving will work
Major failures
• Presence update based on calendar
• Presence based on Out of Office messages
• All mobile clients fail to connect to Exchange
@StaleHansen
25. Features available only with EWS
• Unified Contact Store
• High-Resolution Photos
• Meeting tab
• Contact Information
• Presence based on Calendar Information
• Conversation History
– Missed Conversations
– Missed Calls
• Voice Mail Playback
@StaleHansen
26. That is why we Lync folk care about
Exchange Web Services
@StaleHansen
27. Best Practice publishing EWS
• DNS A Record for autodiscover.domain.com
– SRV is supported, but not recommended
– Multidomain? Use HTTP redirect
• Publish using NTLM, no pre-authentication
– EWS and autodiscover
– Avoids authentication pop-up for EWS
• No need to Set-AutodiscoverVirtualDirectory
– Should point to HLB with correct autodiscover
certificate
@StaleHansen
37. WiFi problem areas
• Shared medium
• Limited band selection in 2.4 GHz band
• Was designed for none-real time data
usage
• Deployed for access, not throughput
@StaleHansen
38. How to optimize for voice over WiFi
• WiFi tag Lync voice traffic with DSCP value
– Through heuristic approach, deep packet inspection and guestimates
– Use QoS to prioritize Lync voice traffic
– Great for unmanaged devices
• Move to 802.11n and 5ghz or 802.11ac
• High-density AP deployments
– Closer to users
• Fast inter-AP handover support
– All venderos stress end to end optimization
– Endpoint -> WiFi -> LAN -> WAN -> LAN -> WiFi -> Endpoint
@StaleHansen
41. Validate your WiFi network with Ixia
• Discovery Phase
– Understand what network environment exists
– Understand user modalities
• Modeling Phase
– Determine Lync utilization per AP
• Traffic Simulation
– Using a Lync Traffic simulator, connect clients and apply real traffic to
production network and monitor factors that affect the quality of Lync
traffic: delay, jitter, and packet loss
• Report
– Analyze factors affecting quality and produce a full report with
recommendations
@StaleHansen
42. Validate your network
• Network Stats (RSSI, PHY)
– Target & other networks
– HTTP speed test
• Lync results per location
– By traffic class (voice, video)
– By client
45. Challenges
• Lync clients need to authenticate directly
• Native passive authentication breaks
exchange
@StaleHansen
46. Passive authentication
• Supported on WP8 and iOS
• Works only with Lync, breaks Exchange
Web Services
– Meetings environment
– Voice Mail environment
– UCS will still work through the Lync Server
@StaleHansen
47. • A number of third parties can sit in the HTTP
flow/Reverse Proxy Role and add additional Security
– Restrict sign in to selected devices
– Authenticate specific devices to specific users
– Use dedicated “lync mobile” credentials so that AD
credentials to not sit on the phone
• Vendors include
– PointSharp
– Lync Solutions
– LyncShield
@StaleHansen
48. PointSharp
• Lync reverse proxy
• App specific password
• Device control
• User identity
• Pre-authentication
• 2-factor auth
@StaleHansen
49. Media
Lync Web Services
PointSharp Web Services
Exchange Web Services
In the first half of 2015, the next version of Lync will become Skype for Business with a new client experience, new server release, and updates to the service in Office 365. With the best of Lync, and the best of Skype, we believe that Skype for Business will again transform the way people communicate by giving organizations reach to hundreds of millions of Skype users outside the walls of their business.