Before you attempt to configure your client environment to use the Lync 2013 client, please check the client version to ensure it does not start with the number 16 for example: 16.x.x.x. NOTE The Lync 2013 client experience isn’t an option for Skype for Business 2016 client versions.
Skype for business 2013 64 bit install update#
June 9, 2015, update for Office 2013 (KB3054853) Note You do not have to apply update KB3054853 if you applied the April 14, 2015, update (KB2889923) or the May 12, 2015, security update (KB3039779) for Lync 2013 (Skype for Business). If you have MSDN subscriptions, you can download Lync 2013 with Service Pack 1 (x86 and 圆4) from: Moreover, you can also check out this article. Download the 64-bit Lynchelploc update package now.
If you’d prefer to use the Lync client experience, you can manage the first launch client behavior to display the Lync user interface following the steps later in this topic. Based on my understanding, you’ll want a MSI package of Skype for Business 2016/ Lync 2013. The default setting is for users to use the Skype for Business client user interface. Switching between the Skype for Business and the Lync client user interfacesįor Skype for Business Online organizations, you can use the Remote PowerShell in Office 365 to enable your Skype for Business users to use the Skype for Business client or the Skype for Business (Lync) client user interface. Navigating through the TechNet and Office blogs I’ve encountered the following statement: One of the things I’ve noticed right away is that the new Skype for Business client which is part of the Office 2016 suite is showing the Skype for Business UI regardless of the policy assigned to the user, meaning that if the policy for EnableSkypeUI is set to TRUE or FALSE, the Skype UI is being showed to the user. Microsoft has released Office 2016 suite two weeks ago and I decided to give that a try after using the beta for couple of months now.
0 kommentar(er)
