One of the most noticeable changes from Skype for Business (SfB) to Lync Server 2013 is the client user interface.
First, the Lync 2013 client will simply become the SfB client. The client will ship with two UI’s or skins. This will allow administrators to choose which one works best for their environment.
Second, the SfB client is going to be distributed via Windows Update as an Office update. The UI is going to be controlled initially based on the backend server platform you have. That is the client will detect if you are homed on Lync 2013 and present the 2013 UI. If you connect to a SfB backend, it will display that UI. However, that said, you have the ability to control the UI via policy as well. This would allow you to upgrade the backend of your deployment, leave the Lync 2013 UI for the time being until you are ready to train, etc.
Control the UI
The ability to control the UI is done via a client policy.
You can update your client policy using the following command:
Get-CsClientPolicy Set-CsClientPolicy -EnableSkypeUI $true
During the testing of the new client it has been rumored that an update to the Lync Server 2013 will introduce the new EnableSkypeUI for those organizations not ready to move to SfB Server 2015. I don’t know when this patch is going to be available or if one will be coming to Lync Server 2010.
However, you can control the client via registry as well. The client policy is creating a local registry in the following location: HKEY_CURRENT_USER\Software\Microsoft\Office\Lync\EnableSkypeUI
The EnableSkypeUI REG_BINARY can be set to either 01 00 00 00 (True) or 00 00 00 00 (False). What I don’t understand is why a REG_DWORD wasn’t used instead. Pushing REG_BINARY can be a bit of a pain so hopefully the Lync Server 2013 updates will be released soon.
Here is a side-by-side comparison of the two clients. Note that I’m using the EnableSkypeUI flag to flip between the UI’s so the build number of the clients are exactly the same.
There are some things that are immediately noticeable. First, we have moved to the over used picture in a circle look. Second, the default view takes up much more space then the old client. Using the same resolution and window size we can see that we can’t fit as many people into the visible window. That is unfortunate in my mind. There is plenty of white space between the contacts that could be removed. Third, the presence icons have changed to small round circles instead of the color bar next to the pictures. I’ll be honest this takes a bit of time to get used to. I’ve looked at the client more than once and didn’t even notice the presence of the user.
Another change you can’t see in these pictures is that the default sounds have all changed from the Lync to Skype sounds. I would highly recommend that you take a backup of the Lync sounds and distribute them to your users. I understand the desire to make the new UI look and feel like the consumer version but changing the sound files may cause some administrative headaches. Even running the client in Lync 2013 UI mode the sounds are still the new SfB sounds which might be unnerving for some users and result in unnecessary helpdesk calls.
I think the changes overall are a positive. I have some issues with the UI much like I did when we moved from Lync 2010 to Lync 2013 but I do believe the client will resonate with end users.
The SfB Client comes with a floating call control window that appears whenever the client is in the background. This feature can be enabled or disabled in the General Settings. This is also controlled in the registry via a DWORD entry of CallMonitorEnabled.
You can now control where the toaster pop appears in the SfB Client. This is a significant change and one people have been asking requesting for a while. While there are third party applications that do the same (and some do even more) it’s a welcome add to the client.
One of the huge complaints of Lync 2013 was the emoticons. I never quite understood the rage but Microsoft has introduced the animated emoticons from the Skype Consumer client to the SfB Client. However some people may not want to see a smily face vomit so you have the option to disable the animations. This is controlled in the registry with EnableEmoticonAnimation.
There is a new Call Handling menu if you enable Call via Work but that will be discussed in-depth later on.