The process of moving from the Lync to Skype for Business look (see it here) is taking a big step April 15, 2015. The cumulative update for the Lync 2013 client will include the new Skype for Business (Skype4B) client user interface.
What will happen if my users are updated to latest cumulative update of Lync 2013 client?
If you have Lync Server 2013 or Lync Server 2010 and get the new Lync cumulative update on April 15, 2015 the users will keep the Lync 2013 user interface. (But do note: after the Lync client updates your users will see the new Skype for Business (Skype4B) user interface, but will be prompted [see below] to restart their client so they get the Lync 2013 user interface again)
How can we avoid the need for users to restart the Lync 2013/Skype4B client to get the Lync 2013 user interface?
To make it so that the client starts in Lync 2013 user interface mode on first run after the update, you need to have the below registry key in place before the update:
- Value name: EnableSkypeUI
- Value data: 00 00 00 00
What WILL change, no matter what we do when we get the Lync 2013 CU on April 15, 2015?
- The Lync/Skype4B sounds will change to new Skype for Business sounds
- Outlook “New Lync Meeting” will change to Skype branding and say “New Skype Meeting”
- Lync/Skype4B client Application/taskbar icon will be the new Skype for Business icon
What if we want to immediately turn the Skype4B client User interface on?
If you want to turn on the Skype4B user interface when the Lync/Skype4B client update comes out you need to:
- Have the December 2014 Lync Server 2013 Cumulative Update Installed (or February 2015 CU
- run Set-CsClientPolicy –EnableSkypeUI $true
This is a short and sweet version, but if you want the longer version that covers more scenarios and details, please jump over to Tom Arbuthnot’s excellent and detailed article: click here
Skype for Business Readiness Download: