However, if no policy is set and Lync Server 2010/2013 is being used on-premises, you can use this script to keep reverting back to the Skype for Business Client if it is desired – until a policy is set. controlling whether the Lync or SFB UI is displayed – until the client policy governs the behavior after the first run. The purpose of the SFB client registry key is primarily for the first run of the SFB client – i.e.

I used this script enough myself that I thought the community would benefit from it. I ended up writing a quick script to flip the registry value so I could switch back-and-forth for various reasons (testing, helping users). In a nutshell, the type of UI ‘skin’ that is used depends on a combination of backend server version, optional server-side client policy, and a registry key.

Most of you are aware that the UI can either run as the Lync 2013 look-and-feel, or the new Skype for Business look-and-fell (if you are not familiar with it, do a quick search, or visit one of the many good write-up’s like fellow Lync MVP Tom Arbuthnot’s write-up here: Important Changes coming to the Lync 2013 Client UI/UX in the April 2015 Client Patch).

Just apply the latest Office Professional Plus 2013 updates, and you will get the Skype for Business client update. As you are probably aware, Microsoft rolled-out the new Skype for Business client as an Office 2013 in the form of 2 update for the Lync 2013 client ( KB2889853 and KB2889923).

Upgrade lync 2013 to skype for business