Lync and Skype for Business Desktop Client Versions (MSI/C2R)

We receive a few number of questions related to the different versions of Skype for Business clients that are available.

If you already use Office 365 then probably you have the Skype for Business  2016 C2R (Click-to-Run).

Skype for Business 2016 C2R (Click-to-Run)

This is the version that is available in Office 365 and it contains the latest features, moving forward this version is also recommended for OnPrem (Lync Server 2013 and Skype for Business Server 2015).

How to check version:

Options > Help > About Skype for Business:

To check the Channel we need to go to another Office application, then File > Office Account:

Update List

Version and build numbers of update channel releases for Office 365 clients
https://technet.microsoft.com/library/mt592918.aspx

Basic Version

How to install the Skype for Business Basic stand-alone client
https://support.microsoft.com/kb/3139711/


Skype for Business 2016 MSI

This version is the Volume License version and doesn’t include all the features available in SfB 2016 C2R.

Both versions are supported but it’s recommended to use the SfB 2016 C2R version instead.

How to check the version

Please note that the version displayed in the Help > About is the MSO version and not the SfB Version.

To check the installed update we can use the following PowerShell cmdlet:

Get-ItemProperty “HKLM:\Software\Microsoft\Windows\CurrentVersion\App Paths\Lync.exe” | ForEach-Object {Get-ChildItem -Path $_.Path -Recurse lync.exe | Select-Object -ExpandProperty VersionInfo | Select FileDescription,ProductVersion}

Alternatively, go to the Tracing Folder and check the ETL filename:

%userprofile%\AppData\Local\Microsoft\Office\16.0\Lync\Tracing

Update List

Skype for Business 2016 Client Update List
https://uclobby.wordpress.com/2016/07/08/skype-for-business-2016-client-update-list/

Basic Version

Microsoft Skype for Business Basic (32/64 Bit)
https://www.microsoft.com/download/details.aspx?id=49440

Please note that SfB Basic version doesn’t include the same features as the SfB2016 MSI client, however, we can use the same updates.


Lync 2013/Skype for Business 2015 C2R (Click-to-Run)

This version was available for Office 365 and it contains the same features as the Lync 2013/Skype for Business 2015 MSI

How to check the version

Options > Help > About Skype for Business

We can also check on another Office application, then File > Office Account:

Update List

Update history for Office 2013
https://support.office.com/article/Update-history-for-Office-2013-19214f38-85b7-4734-b2f8-a6a598bb0117


Lync 2013/Skype for Business 2015 MSI

This version started as Lync 2013 and it was renamed to Skype for Business 2015 on April 14, 2015. This version has the same features as Lync2013/SfB2015 Click-to-Run.

How to check the version

Options > Help > About Skype for Business

Update List

Lync 2013/Skype for Business 2015 Client Update List
https://uclobby.wordpress.com/2016/10/09/lync-2013-skype-for-business-2015-client-update-list/

Basic Version

Microsoft Lync Basic 2013 (32 Bit)
https://www.microsoft.com/download/details.aspx?id=35451

Microsoft Lync Basic 2013 (64 Bit)
https://www.microsoft.com/download/details.aspx?id=35450

Please note that these versions doesn’t include the same features as the Lync2013/SfB2015 MSI client, however, we can use the same updates.

Desktop client feature comparison for Skype for Business Server 2015
https://docs.microsoft.com/skypeforbusiness/plan-your-deployment/clients-and-devices/desktop-feature-comparison

Advertisements

Skype Room Systems V2 Update List: July 2018

Here is the update list for the Skype Room System V2:

Download the latest Skype Room System v2 Deployment Kit

Version Release Date More Info
4.0.8.0 July 6, 2018 Release Notes
3.1.115.0 June 20, 2018 Release Notes
3.1.113.0 June, 2018 Release Notes
3.1.104.0 April 16, 2018 Release Notes
3.1.100.0 March 16, 2018 Release Notes
3.1.99.0 March 14, 2018 Release Notes
3.1.98.0 March 8, 2018 Release Notes
3.0.16.0 November 27, 2017 Release Notes
3.0.15.0 October 3, 2017 Release Notes
3.0.12.0 September 1, 2017 Release Notes
3.0.10.0 August 10, 2017 Release Notes
3.0.8.0 August 4, 2017 Release Notes
3.0.6.0 June 2, 2017
2.0.2.0 March 15, 2017
1.0.8.0 December 7, 2016 RTM

Lync/SfB Client: Disable file upload to external conferences

In the March 2018 update for Lync2013/SfB2015 and SfB2016 a new setting was included that can disable file upload to external conferences (Federated and Anonymous).

Before this update the Lync/SfB Client didn’t had a setting that could prevent file upload to external meetings:

We can configure the EnableExternalFileTransferInConference setting with Inband Policy or Register Key:

Inband Policy

$a = New-CsClientPolicyEntry –Name “EnableExternalFileTransferInConference” –Value $false
Set-CsClientPolicy –Identity <Policy Name> –PolicyEntry @{Add=$a}

Command Prompt

Lync 2013/Skype for Business 2015
reg add HKLM\Software\Policies\Microsoft\Office\15.0\Lync /v EnableExternalFileTransferInConference /t REG_DWORD /d 0 /f

Skype for Business 2016
reg add HKLM\Software\Policies\Microsoft\Office\16.0\Lync /v EnableExternalFileTransferInConference /t REG_DWORD /d 0 /f

PowerShell

Lync 2013/Skype for Business 2015
New-Item -Path “HKLM:Software\Policies\Microsoft\Office\15.0\Lync” -Force
New-ItemProperty -Path “HKLM:Software\Policies\Microsoft\Office\15.0\Lync” -Name EnableExternalFileTransferInConference -Type DWORD -Value 0 -Force

Skype for Business 2016
New-Item -Path “HKLM:Software\Policies\Microsoft\Office\16.0\Lync” -Force
New-ItemProperty -Path “HKLM:Software\Policies\Microsoft\Office\16.0\Lync” -Name EnableExternalFileTransferInConference -Type DWORD -Value 0 -Force

Please note that this registry key is available on a User Level (HKCU) and Local Machine (HKLM).

After disabling the upload the users won’t be able to upload file to External Conferences:

Please note that EnableExternalFileTransferInConference won’t block users to download files from external conferences:

The EnableExternalFileTransferInConference setting is available in the following Lync/SfB Client versions:

Office 365 ProPlus/Office Professional Plus 2016 Click-to-Run (after 16.0.8827.2082)
https://technet.microsoft.com/en-us/library/mt592918.aspx

March 6, 2018, update for Skype for Business 2015 (Lync 2013) (KB4018290) (15.0.5015.1000)
https://support.microsoft.com/kb/4018290

March 6, 2018, update for Skype for Business 2016 (KB4011725) (16.0.4666.1000)
https://support.microsoft.com/kb/4011725

Lync/SfB: Check client version using PowerShell

During troubleshooting we often need to check the installed version, for Lync/SfB Server we already know how to check the installed version using PowerShell:

Skype for Business Server Component Version using Get-CsServerPatchVersion

Skype for Business Server 2015 Component Version using PowerShell

Lync Server Component Version using PowerShell (Windows Registry)

On the client we can check the version by using going to Option > Help > About:

However, for the SfB 2016 MSI this is a slightly different since the displayed version is the MSO component and not the SfB client version:

To get the Lync/SfB client version we can simply run the following in PowerShell cmdlet:

(Get-ItemProperty -path “HKLM:\Software\Microsoft\Windows\CurrentVersion\App Paths\lync.exe”).”(Default)” | ForEach-Object {Get-ChildItem -Path $_ | Select-Object -ExpandProperty VersionInfo | Select FileDescription,ProductVersion} | ft -autosize

Skype for Business 2016 MSI

Skype for Business 2016 Click-to-Run

Skype for Business 2015 MSI

Please note that this will work for Lync2013/SfB2015/SfB2016 Click-to-Run or MSI versions.

For Lync 2010 and previous client versions we need to modify from lync.exe to communicator.exe:

(Get-ItemProperty -path “HKLM:\Software\Microsoft\Windows\CurrentVersion\App Paths\communicator.exe”).”(Default)” | ForEach-Object {Get-ChildItem -Path $_ | Select-Object -ExpandProperty VersionInfo | Select FileDescription,ProductVersion} | ft -autosize

Skype for Business on Mac Update List: August 2018

Here is the update list for the Skype for Business on Mac:

Download the latest update for Skype for Business on Mac

Version Release Date
16.20.0.90 August 13, 2018
16.19.0.132 July 13, 2018
16.18.0.51 June 7, 2018
16.17.0.65 May 9, 2018
16.16.0.102 April 3, 2018
16.15.0.166 February 28, 2018
16.14.0.163 January 31, 2018
16.13.0.184 December 7, 2017
16.12.0.77 November 8, 2017
16.12.0.75 October 31, 2017
16.11.0.149 October 5, 2017
16.10.0.97 August 30, 2017
16.9.0.37 August 02, 2017
16.8.0.196 June 20, 2017
16.6.0.333 May 2, 2017
16.5.0.185 March 28, 2017
16.3.0.240 February 6, 2017
16.2.0.145 December 12, 2016
16.1.0.456 November 23, 2016
16.0.0.3638 October 27, 2016 (RTM)

Please also check the Known issues – Skype for Business on Mac.

If you were looking for the previous version here is the list:

Lync Mac 2011

Version Release Date KB Article
14.4.1 July 13, 2016 KB3175174
14.3.3 February 23, 2016 KB3139293
14.2.1 October 1, 2015 KB3098588
14.1.1 July 23, 2015 KB3074981
14.0.11 March 14, 2015 KB3037358
14.0.10 (Hotfix 1) December 3, 2014 KB3019983
14.0.10 October 29, 2014 KB3007876
14.0.9 (Hotfix 1) July 31, 2014 KB2979062
14.0.9 June 10, 2014 KB2963369
14.0.8 April 9, 2014 KB2952672
14.0.7 December 13, 2013 KB2909662
14.0.6 October 8, 2013 KB2888920
14.0.5 (Hotfix 1) September 4, 2013 KB2884053
14.0.5 June 6, 2013 KB2844274
14.0.4 (Hotfix 1) April 18, 2013 KB2836517
14.0.4 February 1, 2013 KB2778095
14.0.1 RTM NA

 

 

Cannot Sign-in to Office 365 in SfB Control Panel – Exception of type ‘Microsoft.LiveID.IDCRL.IDCRLException’ was thrown

In a new Skype for Business Server 2015 lab we tried to sign-in to Office 365 in the Skype for Business Control Panel:

But after a few seconds we got the following error message:

We couldn’t log in to your Office 365 account. Please check the errors and then select OK to try again:
Get-CsWebTicket: Exception of type ‘Microsoft.LiveID.IDCRL.IDCRLException’ was thrown.

Also in the Event Viewer > Windows Logs > Application the following errors were present:

Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 11/28/2016 12:00:04 PM
Event ID: 1325
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: sfbfe.uclobby.com
Description:
An unhandled exception occurred and the process was terminated.

Application ID: DefaultDomain

Process ID: 30668

Exception: System.Runtime.Serialization.SerializationException

Message: Type ‘Microsoft.LiveID.IDCRL.IDCRLException’ in Assembly ‘Microsoft.Rtc.Management.OnlineConnector.AuthenticationHelper, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ is not marked as serializable.

StackTrace: at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeObject(Object obj, MemoryStream stm)
at System.AppDomain.Serialize(Object o)
at System.AppDomain.MarshalObject(Object o)

Log Name: Application
Source: .NET Runtime
Date: 11/30/2016 6:32:21 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: sfbfedr.uclobby.com
Description:
Application: w3wp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.LiveID.IDCRL.IDCRLException
at Microsoft.LiveID.IDCRL.NativeIdcrlWrapper.Uninitialize()
at Microsoft.Rtc.Admin.Authentication.ManagedIdcrl.Dispose(Boolean)
at Microsoft.Rtc.Admin.Authentication.ManagedIdcrl.Finalize()

To fix this issue we need to add the following permissions to the NETWORK SERVICE account (Please add the permissions in all Front Ends):

Read

%windir%\System32\config\systemprofile\AppData\Local\Microsoft

Full Control

%windir%\System32\config\systemprofile\AppData\Local\Microsoft\MSOIdentityCRL

After this we need recycle the LyncIntManagement application pool. We can do this in the Internet Information Service (IIS) Manager > Applications Pools:

Or with the following PowerShell cmdlet:

Restart-WebAppPool -Name LyncIntManagement
https://technet.microsoft.com/en-us/library/ee790580.aspx

Now we can successfully sign in to Office 365 in the Skype for Business Control Panel:

Lync/SfB Server: Create a custom announcement for Unanswered Calls

We were asked if we could customize the sound/tone for unanswered calls when the called user isn’t voice mail enabled.

Usually the mobile networks will play a announcement like “Sorry, the person you tried to call isn’t available please try again later”.

In Lync/SfB Server we cannot change the default tone, however, we can use an announcement and the unassigned numbers to configure a workaround.

The first step is to get a WAV file with the custom announcement and import it to the Lync/SfB Server with the following cmdlet:

$a = Get-Content “C:\UCLobby\Unanswered.wav” -ReadCount 0 -Encoding Byte
Import-CsAnnouncementFile -Parent ApplicationServer:pool.gears.lab -FileName “UnansweredCall.wav” -Content $a
New-CsAnnouncement -Parent ApplicationServer:pool.gears.lab -Name “Unanswered Call Announcement” -AudioFilePrompt “UnansweredCall.wav”

Then we need to associate a number, this doesn’t need to be a valid number, if can be a dummy number as long that it’s a number that can be assigned to a Unassigned Numbers.
In the lab we use +449920145999 and assign a announcement to it:

New-CsUnassignedNumber -Identity “UnansweredCallAnnouncement” -NumberRangeStart “+449920135999” -NumberRangeEnd “+449920145999” -AnnouncementName “Unanswered Call Announcement” -AnnouncementService ApplicationServer:pool.gears.lab

Finally, we can forward the unanswered calls to +449920145999.  We can do it in the Lync/SfB client Options > Call Forwarding:

Select New Number or Contact:

Then we add the number we specify in the New-CsUnassignedNumber:

Now all unanswered calls will be forwarded to the configured announcement:

Please note that it’s also possible to configure the unanswered calls forward setting on the server side using the SEFAUtil:

Configure simultaneous ring, delegate-ringing and call-forwarding settings on behalf of a Lync Server 2010 user
https://blogs.technet.microsoft.com/meacoex/2011/04/23/configure-simultaneous-ring-delegate-ringing-and-call-forwarding-settings-on-behalf-of-a-lync-server-2010-user/