Ignite 2018

Back from HUMID Orlando Florida and another year of Ignite. There was a theme on the Modern Workspace side of the conference of Teams Teams Teams. There was, as expected, some concern and confusion over the announced removal of Skype for Business Online for sub-500 tenants. Surprisingly (at least to me) there was a general question of what the Skype for Business v2 (SRSv2) system was and even what Teams was.


Since there is little more that can be said about what Teams is I will not go into that and hopefully this audience is aware of the SRSv2. However, I do think it is important to take the time to reemphasize the need and requirement to perform (yourself or with an external consultant) network validations and health checks PRIOR to implementing a real-time communication SaaS such as Teams. Korneel Bullens and Siunie Sutjahjo provided a session where the discussion of the network health was stressed once again, and some great input was provided.


When I am asked to perform a network health check for Skype for Business/Teams there are multiple things I am looking for but often overlooked that those items need to be looked at from all SUPPORTED client networks. You may say my network is healthy and that if I get positive test results from one location or VLAN I have no reason to test another. I would argue, really? Users working in a remote user office with 10 total clients may end up having an even better experience than those in the 10k employee corporate office simply because of the network (assuming local breakout for the remote office). Then you have the Wi-Fi network and all that it entails – sometimes the Wi-Fi network is something that until fixed must be classified as an unsupported client network. I have yet to be involved in a deployment that did not have at least one area to address within the LAN/WAN but if you are the company – congratulations (and this assumes you did not already perform a network discovery and remediation for a previous Skype for business or an earlier version).


From a basic network discussion, the questions that come to mind when it comes to Teams specifically are:

  1. Are the correct network ports open inbound/outbound
    ( tcp/443 AND udp/3478-3481)?

  2. Are there content filters/proxies in the mix?

  3. Do all locations have a direct ingress/egress point of Internet (really for all O365 workloads and no, Express Route does not fix this need)?

  4. Are PCs/Laptop network drivers up to date (the video and IO subsystem drivers are important too, but this is about networking)?

Keep the network health and utilization top of mind when working with SfB, SfB0 and Teams and your deployment will be a great success.

Office 2016 / Skype for Business 2015 Client Preview

Much has been posted recently regarding the preview of Skype for Business client and what it has to bring to the table. The basic office team announcement was made on their blog (found here) this morning but others attending the various release functions commented as well. Those comments are the ones I have issue with and want to make a few basic comments of my own here.

First and foremost the new Skype for Business client is NOT a new client but rather an update to the existing Lync client. That's right - a CU/KB is applied and voila - you have the new Skype4B client. That brings a lot of ramifications with it, not the least that this client does communicate and work with Lync Server 2013 just fine. In its basic client upgrade and work as you are state, the features are the same, but you get a new look.

Skype4B client does NOT add the additional functionality of initiating calls, communication, etc. directly from Office apps (such as Outlook) as Lync already did that - and has done that - forever. This is nothing new and the contact cards are still shared. This also means it is not pulling on Lync features, they are Lync features as again, this is Lync under the covers.

Another important feature - and one that has been available in Lync for some time - is the ability to communicate with the public Skype counterpart. The idea of public federation was introduced in 2006 with Live Communication Server 2005 SP1 (that's LCS, the predecessor to OCS which was the predecessor to Lync). Public federation is a feature that has been in Lync's history and today (and yes even yesterday) you had the option to configure this federation link using the Microsoft provisioning website of https://pic.lync.com. Will the process and the features improve with time - yes, but not a new feature as of today.

Skype for Business Client and Office 2016 are coming and are exciting improvements. But it is important to understand what the changes are, how they impact current infrastructure, and what  (if any) impact that means on your end users. The last big piece of that equation is rolled into the original comment above - that this release is simply a cumulative update. What if you don't want the update? Well for those on-premise that are delivering Office Pro Plus 2013 using the "fat" method, easy - don't install it. For those using the Click-2-Run Office 365 distribution method - not such an easy decision. The good news is regardless, administrative control will be available to decide how Lync/Skype looks on the desktop using Lync/Skype client policies. This means the updates can occur and the switch to the new interface (and potentially new features) can be at the control of IT.