Change is coming. What EnableSkypeUI doesn’t do.

Microsoft has done a good job of telling people that change is coming to their Lync client. A quick recap of what is coming.

April 14th (Patch Tuesday) Microsoft is starting the process of pushing out the Skype for Business Client UI. This is going to hit “click to run” and those users who use Windows Update first. If you are a business organization you have more control because you are most likely using SCCM/WSUS to approve patches to your workstations and you can take a bit more time to deal with it.

Microsoft has several resource sites that you can use for more details on this. I suggest checking these out:

In these you will find the EnableSkypeUI option that allows you to change the UI of your client.  However, there are a few things that will change regardless that the EnableSkypeUI doesn’t control.


The installer will replace all of the Lync Sounds with the Skype Sounds.  Users of both UI’s will experience this change.  To me, this is the most notable change that your users will notice regardless.  The sounds are VERY different then before.  You should make sure your users are aware of this and your helpdesk is ready for the calls.

Meeting Links

If you are using Lync Conferencing your users are about to see a change.  The Lync patch will update the Outlook Plugin and change the Lync Meeting to a Skype Meeting


And the actual join link will be changed as well



Your Lync icon will look a lot like Skype for Business icon regardless which UI you choose.


Title Bar

The title is going to say Skype for Business.  If you have the Lync UI, it will say Skype for Business (Lync Mode).

Initial Join

The default behavior of the Skype for Business Client is to launch into the Skype for Business UI.  If you have selected via policy to use the Lync 2013 client you will see this:


This poses two problems.  First, you need to inform all of your users they are going to see this annoying message.  Second, it gives them the ability to choose Restart Later and lets them play in the new UI (which they are going to pick because end-users who see Restart will always pick later).  The only way to suppress this is to push out the registry key before hand so the client never even asks.  See this post for registry settings.

Here is a table that describes the scenarios


This is the most notable visual change that users will see after the patch if they are using the Lync UI option.  Hopefully these help and if I find anymore changes along the way I’ll make sure to note them here.

7 comments on “Change is coming. What EnableSkypeUI doesn’t do.”

  1. Pingback: Weekly IT Newsletter – March 30-April 3, 2015 | Just a Lync Guy

  2. Pingback: NeWay Technologies – Weekly Newsletter #141 – April 2, 2015 | NeWay

  3. Pingback: NeWay Technologies – Weekly Newsletter #141 – April 3, 2015 | NeWay

  4. Jeff Brown Reply

    Do we know yet if the Skype UI change will be a targeted Lync update or part of a larger Office update?

  5. Tony Nunn Reply

    If like me, you want to use the new UI but have no capability to change the policy for client setting or your infrastructure is still that of Lync, you can force the use of the Skype for Business UI via the registry:

    REGEDIT, Navigate to


    and notice the value for EnableSkypeUI;

    00 00 00 01 – Skype for Business UI
    00 00 00 00 – Lync 2013 UI

    • Harbob Reply

      @Tony Nunn,
      I performed this step Tuesday on two clients, and the UI did not update to S4B on either workstation. Should I reinstall O365 and try again, or is the O365 admin overriding my registry setting?

  6. Pingback: Microsoft releases April 2015 update for Lync/Skype for Business client | Just a Lync Guy

Leave A Reply

Your email address will not be published. Required fields are marked *