Skype for Business Web App or Skype Meeting App doesn’t respect conferencing policy for AllowParticipantControl and AllowExternalUserControl

Note This fix only applies to Skype Meeting App. If you are using the Skype for Business Web App, you have to enable the Skype Meetings App to replace the Skype for Business Web App.

To enable the Skype Meetings App, please run the following cmdlet:

Set-CsWebServiceConfiguration -MeetingUxUseCdn $True

Skype for Business on Mac can’t save a password when AllowSaveCredentials is False and “Keep me signed in” is selected

The issue occurs because the mobility policy was applied to the Skype for Business on Mac desktop client, and it was by design. After you apply this update, the mobility policy is applied only to the mobile clients.

Failed to setup database rtcxds due to an unexpected error.

Detail: Microsoft.SqlServer.Management.Smo.UnknownPropertyException: Cannot write property TargetRecoveryTime.This property is not available on SQL Server 2008 R2.

This issue occurs because a value of targetRecoveryTime attribute isn’t set correctly, and it isn’t present in SQL Server 2008 R2.

This issue occurs because the external file transfer’s traffic doesn’t traverse the Edge Server. Therefore, the external file transfer is enabled.

This issue occurs because the connection type of MobileBB and Tunnel is interchanged.

• Identity
• Target
• Credential
• MoveToTeams

For example:

Move-CsUser -Identity “UserAccountName” -Target “RegistrarPool FQDN” – UseOAuth

In this example, the OAuth authentication method is invoked when you move the user account by using the Identity to the Registrar pool. Otherwise, the Skype for Business Server will use the existing legacy authentication.

This issue occurs because the routing group IDs for trusted application endpoints don’t populate correctly.

• You set the Busy Options feature to Busy on Busy or Voicemail on Busy status by using the Set-CsBusyOptions cmdlet.
• You verify that the Busy Options is turned on by using the Get-CsBusyOptions cmdlet.
• You sign in to the Skype for Business for iPhone or Android client. Or, you sign in to the Skype for Business client by using a third-party phone device such as Polycom, Spectralink and so on.
• You turn on the Call Forwarding.
• You run the Get-CsBusyOptions cmdlet to check the Busy Options status.

In this scenario, you can see the Busy Options settings that you set before are lost.

• You force the deletion of the queues that the workflow uses by using the Remove-CsRgsQueue -Force cmdlet.
• You set the RGS workflow to inactive and configure it for “Managed.”

When you remove the queues, the workflows that use these queues become inactive and Skype for Business Server can’t find the queues referenced by these inactive workflows. Therefore, the import cmdlet fails.

• You implement the German version of Microsoft Skype for Business Server 2015 in a German language operating system of Windows Server.
• You configure a watcher node test user by using the Set-CsUserTestCredential cmdlet.

For example:

Set-CsTestUserCredential -SipAddress “sip:user@contoso.com” -UserName “contoso\user” -Password “<Password>”

In this scenario, you receive an error message that resembles the following:

Set-CsTestUserCredential : Fehler beim Festlegen der Anmeldeinformationen f.r sip:user@contoso.com. Innere Ausnahme: Microsoft.Rtc.Management.SyntheticTransactions.CredentialManagement.NetworkServiceImpersonator+NetworkServiceImpersonatorException: Fehler beim Annehmen der Identit.t des Netzwerkdienstkontos. Fehlerdetails: Es wurden keine Prozesse im Besitz von ‘NT Authority\Network Service’ gefunden..

Prerequisite installation failed: Prerequisite installation failed: SqlInstanceRtcLocal For more information, check your SQL Server log files. Log files are in the folder C:\Program Files\Microsoft SQL Server\MSSQL*.RtcLocal\MSSQL\Log, where the * represents your SQL Server version number. For example, SQL Server 2012 uses this path: C:\Program Files\Microsoft SQL Server\MSSQL11.RtcLocal\MSSQL\Log.

In addition, an Event ID 26011 could be logged in the Event Viewer. This issue occurs when you enable the TLS 1.2 and disable the TLS 1.0/1.1 on the operating system.

This issue occurs because the setup installs a version of SQL Express that does not support TLS 1.2.

You have to enable TLS 1.0 and TLS 1.1 on the local computer; uninstall Microsoft SQL Server 2014 (64-bit) through Programs and Features in Control Panel, and then rerun step 1 – Install Local Configuration Store and step 2 – Setup or Remove Skype for Business Server Components. After that, update SQL Server to the version that supports TLS 1.2, and then disable TLS 1.0 and TLS 1.1 again after SQL Server is updated.

• One or more Survivable Branch Appliances or Survivable Branch Servers (SBAs/SBSs) are deployed in a Microsoft Skype for Business 2015 or Lync Server 2013 environment.
• The servers interact with a trusted application (typically UCMA-based) that queries the presence information for users who are homed on these SBAs/SBSs.

In this situation, when some users’ presence information is queried, the Lync Server Front-End service (RtcSrv.exe) of the SBAs or SBSs starts but then crashes within about 20 seconds. Additionally, you receive an event that resembles the following:

Time: Date
ID: 1000
Level: Error
Source: Application Error
Machine: MachineName
Message: Faulting application name: RTCSrv.exe, version: VersionNumber, time stamp: TimeStamp
Faulting module name: wsiphsh.DLL, version: VersionNumber, time stamp: TimeStamp
Exception code: 0xc0000005
Fault offset: 0x0000000000005e2f
Faulting process id: 0x420c
Faulting application start time: Time
Faulting application path: C:\Program Files\Skype for Business Server 2015\Server\Core\RTCSrv.exe
Faulting module path: C:\Program Files\Skype for Business Server 2015\Server\Core\wsiphsh.DLL
Report Id: ReportID
Faulting package full name:
Faulting package-relative application ID:

You can rejoin the meeting from the UCWA client.

$cred1 = Get-Credential “CONTOSO\User1”
$cred2 = Get-Credential “CONTOSO\User2”
Test-CsUcwaConference -OrganizerSipAddress sip:User1@contoso.com -OrganizerCredential $cred1 -ParticipantSipAddress sip:User2@contoso.com -ParticipantCredential $cred2 -TargetFqdn pool.contoso.com
Target Fqdn: pool.contoso.com
Target Uri:
Result: Failure
Latency: 00:00:01.3141048
Error Message : Failed creating application activity.
Inner Exception:One or more errors occurred.
Inner Exception:One or more errors occurred.
Inner Exception:Object reference not set to an instance of an object.

The commands that are shown here test the ability of a pair of users (CONTOSO\User1 and CONTOSO\User2) to participate in a UCWA online conference.

• You’re a Location-Based Routing (LBR) enabled user and located on a LBR enabled site in Microsoft Skype for Business Server 2015.
• You successfully start a peer-to-peer call with a public switched telephone network (PSTN) user by using the Skype for Business on Mac client.
• Then you escalate the peer-to-peer call to a conference by inviting another Voice over Internet Protocol (VoIP) user who is located on the same site as you.

In this scenario, you may notice that the user can’t be reached because of conferencing service issues. It’s expected that the user can join the conference without any problem as the escalation happens to the same site’s user only.

• You are in a Microsoft Skype for Business Server 2015 on-premises and Exchange hybrid environment.
• You implement the Skype for Business Server 2015 Front-End pools with the proxy and without a direct access to the Internet.
• You set up the Skype for Business Server OAuth configuration settings (-ExchangeAutodiscoverUrl-) pointing to your on-premises Exchange CAS server.
• You enable the server-side conversation history feature by using the conversation history configuration settings for Skype for Business.
• You set up an account by creating an Exchange online mailbox.

In this scenario, the user of the account can’t use the feature of server-side conversation history to save the conversation history in the Exchange online mailbox. In addition, the on-premises users won’t be affected.

The issue occurs because the Exchange CAS server is redirecting the Autodiscover request to Exchange Online directly instead of using the proxy server. As the Exchange on-premises servers can’t directly connect to Exchange Online, the connection fails.

In addition, as the on-premises mailboxes are local resource, the Autodiscover process works fine.

• You implement a third-party SIP-Trunk integration solution such as Cisco, Avaya Aura and so on, with Microsoft Skype for Business Server 2015.
• You are an enterprise voice (EV) enabled Skype for Business user. User B and User C are using the Cisco or Avaya phone.
• User C has a call forwarding to User B.
• You make a telephone call with User C by using the Skype for Business client.
• The call connection is established between you and User B.

In this scenario, you may see the Skype for Business client displays the User C’s caller ID (also known as a Calling Line ID) instead of User B’s caller ID.

This issue occurs because the information about the original caller is lost at the Skype for Business Mediation server.

Test-CsClientAuthentication -TargetFqdn <FeFqdn> -UserSipAddress <UserSIP> -UserCredential <UserCred> -Verbose

The cmdlet fails and you may receive an error message that resembles the following:

“Unable to perform authentication of credentials. Inner Exception:ComputeSignature failed.”

Second chance exception on worker thread. Thread: 21, Exception: Exception: System.ArgumentOutOfRangeException
> Message: The value 3905470566 is out of the expected range 0..2147483647.
Parameter name: value
> ParamName: value
> TargetSite: Void ThrowIfIntOutOfRange(Int64, Int64, Int64, System.String)
> StackTrace:
at Microsoft.Rtc.Signaling.ArgumentVerifier.ThrowIfIntOutOfRange(Int64 number, Int64 minValue, Int64 maxValue, String paramName)
at Microsoft.Rtc.Signaling.SdpBandwidth.set_Value(Int64 value)
at Microsoft.Rtc.Internal.Collaboration.Media.SdpMediaSession`2.GenerateSdp(SdpDialogNegotiationContext dialogContext, GenerateSdpReason reason)
at Microsoft.Rtc.Internal.Collaboration.Media.SdpMediaSession`2.GenerateAnswer(Object dialogId)
at Microsoft.Rtc.Collaboration.AudioVideo.MediaSessionAgent.ProcessGenerateAnswerWorkitem(GenerateAnswerWorkitemAsyncResult workitem)
at Microsoft.Rtc.Signaling.WorkitemQueue.ProcessItems()
at Microsoft.Rtc.Signaling.QueueWorkItemState.ExecuteWrappedMethod(WaitCallback method, Object state)
> Source: Microsoft.Rtc.Collaboration
> HResult: -2146233086

• You implement the Microsoft Skype for Business UCMA based Contact Center applications that support app sharing in your organization.
• You enable the Video-based Screen Sharing (VbSS) feature in Skype for Business Server 2015.
• You share your desktop with another user by using a Skype for Business client.

In this scenario, the desktop sharing fails.

An error occurred during the screen presentation.

• The January 2019 cumulative update 6.0.9319.537 for Skype for Business Server 2015, Web Components Server.
• The January 2019 cumulative update 6.0.9319.537 for Skype for Business Server 2015, Core Components.
• The January 2019 cumulative update 6.0.9319.537 for Skype for Business Server 2015, Front End Server and Edge Server.