Forum Widgets
Latest Discussions
Skype For Business SE - persistent Chat
Hello, maybe someone of you run into the same error and is able to help me on this topic: we are using SkypeForBusiness only for internal communication last week we have upgraded SkypeForBusinness 2019 to SE: "SkypeServerUpdateInstaller.exe" run without errors, installed the necessary updates and we were able to upgrade to SE on topology builder and publish the new version. on the next step we tried to activate persistent chat. so same procedure for the upgrade: start the update file "PersistentChatUpateInstaller.exe", nothing else to upgrade the first steps (install new sql instance, configure topology builder, publish the new topology were easy, no issues occured. but when we start the Deployment Wizard to install the necessary components we received the error: "File not found trying to install installing c:\programdata\skype for business server\deployment\cache\7.0.2046.0\setup\mgcserver.msi (feature_chat_server)" my question: how can we install the necessary roles/components to activate persistent chat. the file MgcServer.msi couldn't be found on the server, i can't find it on the SkypeForBusinnes 2019 ISO, too. one version i found, was located on the ISO for SkypeForBusiness 2015 ISO, but this version can't be installed. Thanks in advance, best regards, MarkusstimaOct 29, 2025Occasional Reader25Views0likes0CommentsSfB 2019 Install Help
Hey everyone! Happy Monday! I'm trying to install a handful of on-prem Skype for Business 2019 into a lab environment and I'm falling at the second hurdle when running 'Setup or Remove SfB Server Components'. I'm getting the error: 'Error 0x8007054b (The specified domain either does not exist or could not be contacted) setting launch conditions on DCOM layer during action SetDCOMSecurityEx. CustomAction CA_SetDCOMSecurity returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Error returned while installing Server.msi(Feature_Server, Feature_HealthAgent), code 1603. Error Message: A fatal error occurred during installation.' All of the servers are part of the same domain. I can log into the skype servers with a domain account, DNs all seems to be working, nltest commands seem to come back normal. Things that I've tried: - Adjusting the COM Security settings for launch and Activation Permission to include RTCUniversalServerAdmins and my admin account to allow local/remote launch, and local/remote activation - Setting a group policy to allow the group EVERYONE to make remote SAM calls (this seemed to have a broken a lot so reverted... I saw it on an MS forum that fixed it for someone) - Run the installer as admin, run it w/out admin - Put the server into a 'staging' area in AD with no policies applied. Fortunately this same error is happening on all servers, which implies that there is a policy, registry key or some permission that's getting in the way. Does anyone have any ideas of some other things that I can try? Thank you! Edit: I know Skype 2019 is old, I know I should be using something else. I'll be moving to Skype SE in Oct.IBrokeitSep 22, 2025Copper Contributor21Views0likes0CommentsHow to Remove Skype for Business
Skype for Business currently installs as a packaged product with Microsoft 365 Business Professional desktop apps. The installation does not install Teams as a part of the Microsoft 365 Business Professional desktop apps. Additionally, Skype for Business has its own installation which is separate from Microsoft 365 Business Professional desktop apps installation. Windows OS: 11 Pro w/ Windows updates. Issues: Users are unable to remove Skype for Business from their desktop by clicking “Uninstall” located on the Windows Start menu. Teams upgrade requires Skype for Business settings to be set manually via the Teams Admin Center. Using the PowerShell command: uninstall-package 'Microsoft Skype for Business MUI (English) 2016' to remove Skype for Business requires NuGet to be manually installed prior to performing a removal task or does not remove the application at all. The odd thing about this is that the system recognizes that a 2016 edition of Skype for Business exists. Note: Microsoft Word reads with the following version number: Microsoft 365 MSO (Version 2508 Build 16.0.19127.20082) 64-bit Granting and then revoking API permissions via Entra Admin center does not separate Skype for Business from the Microsoft 365 Business Professional installation. Uninstalling Microsoft 365 Business Professional desktop apps only removes the Skype for Business app temporarily until reinstallation occurs.sybase54Sep 04, 2025Copper Contributor41Views0likes0CommentsModern Auth with Skype for Business 2015
Hi, I was wondering if there any newer documentation on how to setup Modern Auth with Skype For Business 2015? I was reading this article: https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__techcommunity.microsoft.com_blog_skype-5Ffor-5Fbusiness-5Fblog_hybrid-2Dmodern-2Dauthentication-2Dfor-2Dskype-2Dfor-2Dbusiness_134751%26d%3DDwMFaQ%26c%3Ddwr0MjUrBqJCVHlZWcv1jg%26r%3DSKZxpzlmCJtnX1r1i1rE0KA4J4E6CkOA7kO_Idr5xrc%26m%3DSNabNm9tBTuQXwR2yhaoP9LPv4iKg7FLz7IZliin7Qu09un5jv0AVZVTHIO8s6MT%26s%3DBFSutEkHn-T-b92xusRwulnTjtzDrPgbx6tSdJRKl7k%26e%3D&data=05%7C02%7Callen%40sd69.bc.ca%7C3c048228a14945f0c70108dda1fa80ed%7C3280d4c237e747f9bb72057a43679c07%7C0%7C0%7C638844819604218028%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=SjXgBqzeID1IoE99hcdyG1RtEHdXdTdDV%2BtNqlV9u3k%3D&reserved=0 But it points to AppID that doesn't exist in our tenant.colaguyJun 02, 2025Copper Contributor51Views0likes0CommentsWhite screen if use local web client in S4B 2019
I would like that my users don't use MS CDN and use only local S4B web client . 1. I have a link for meeting https://meet.exchlab.ru/test01/5V854YXZ?sl=1 2. If I follow it I see white screen. 3. But this page a not really empty it has a html code. 4. If I set UseLocalWebConfig to $false, web client S4B is downloaded from MS CDN and works perfect, but I need local client, because not all of my internal users have access to Internet. Why I see white screen instead of normal web page?pavelnagaevMar 15, 2025Copper Contributor811Views2likes3CommentsCloud PBX experience
Hey folks, I thought I'd share a blog post of my recent experience implementing and migrating myself and a number of users from Skype for Business Server over to Cloud PBX: http://thecloudmouth.com/2017/01/10/experiences-with-cloud-pbx-skype-for-business-online/923Views1like1CommentSalesforce Integration with Skype For Business
A while back you may have heard that there is a way to integrate Skype for Business with Salesforce. We just posted an article to the Skype for Business Community Blog detailing how to do this. Check it out here. Salesforce currently has this feature available as a public Beta. Over time we hope to see continued enhancements to this integration. Let us know what you think!Andrew HitchcockAug 28, 2024Former Employee13KViews7likes4CommentsSONUS - CAS-R2 CD Bit error
I'm trying to setup a SONUS 1K in Brazil with Vivo as a provider It's an E1 R2 CAS connection, but I can't get in or outgoing calls to work This is my current R2 CAS profile When I restart SONUS, I get this CAS-R2 CD Bit error Does anyone have experience with SONUS and an E1 R2 CAS connection to Vivo?Claus-Ole OlsenMay 30, 2024Brass Contributor1KViews0likes1CommentSkype Web Components Server Error
Good day all, Been having a strange issue regarding TLS and Web Components Server Errors since deploying a new single server. There is currently 2 single servers on the topology and moving a user from one FE server to the other seems to not always work, especially if they are coming via the EDGE server. On most login requests we receive the below errors in the even logs: { An unhandled exception was encountered. Service: WebTicketService, exception details: System.ComponentModel.Win32Exception (0x80004005): The client and server cannot communicate, because they do not possess a common algorithm at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc) at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential) at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint) at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output) at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost) at Microsoft.Rtc.Internal.WebServicesAuthFramework.RemoteCertificateResolver.ResolveCertificate(HostAddress hostAddress, Int32 port, ICollection`1 allowedNameList) at Microsoft.Rtc.Internal.WebServicesAuthFramework.WebTicketRemoteSecurityTokenStore.ResolveAndCache(String key, HostAddress hostName, Int32 port, ICollection`1 allowedNameList) at Microsoft.Rtc.Internal.WebServicesAuthFramework.WebTicketRemoteSecurityTokenStore.GetSigningTokenByIssuer(HostAddress hostAddress, Int32 port, ICollection`1 allowedNameList) at Microsoft.Rtc.Internal.WebServicesAuthFramework.WebTicketRemoteSecurityTokenStore.EnsureIssuerSecurityToken(HostAddress machineAddress, Int32 port, ICollection`1 allowedNameList) at Microsoft.Rtc.Internal.WebServicesAuthFramework.WebTicketKeyStore.EnsureIssuerSecurityToken(Uri issuerUri) at Microsoft.Rtc.Internal.WebTicketService.WebTicketService.BeginIssueToken(Message rstMessage, AsyncCallback callback, Object state) at AsyncInvokeBeginBeginIssueToken(Object , Object[] , AsyncCallback , Object ) at System.ServiceModel.Dispatcher.AsyncMethodInvoker.InvokeBegin(Object instance, Object[] inputs, AsyncCallback callback, Object state) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet). Cause: Application error. Please look through the exception details for more information. Resolution: Restart the server. If the problem persists contact product support.} Restart obviously didnt resolve this issue. Checking the system logs, I see the following schannel errors: A fatal error occurred while creating a TLS client credential. The internal error state is 10013. When I checked the TLS settings on the FE (which is where I get all these errors above) with inetcpl.cpl I see that only TLS 1.2 is ticket. Looking at the EDGE server, there is no apparent error that is causing this. We just added the new servers to the SRV and A Record DNS entries, so this shouldnt be an issue. The EDGE has the below schannel errors: An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The TLS connection request has failed. Not sure if this could cause any issues though as the working environment has the same errors as the above.RenierHApr 29, 2024Copper Contributor1.4KViews0likes2CommentsMicrosoft Phone System + Calling Plans + Analogue Device
Hi Everyone, We use Microsoft Teams and Microsoft Phone System with Calling Plans. This is our single phone system for everything, we do not have any other PSTN, SIP Trunks, nothing. Is it at all possible to somehow connect an analogue phone line to this environment? We own an AudioCodecs VE SBC and have an MP-112 ATA, Our AudioCodecs SBC is connected to Teams with Direct Route, but since we use Calling Plans..we don't really know where to go from here or if it's even possible. In an ideal world, we would provision a user in our AD, give it a phone number from Microsoft Calling Plans, and then have that phone number be the number of an analogue device (FAX). Any inbound and outbound faxes would go through the Calling Plans from Microsoft. I just want to know if that's even possible? I have attached the picture I modified from some AudioCodecs documentation. Since we use Calling Plans, everything is in the Microsoft Bubble on the right. Thank you so much for your time.eblendApr 13, 2024Copper Contributor3.9KViews0likes8Comments
Resources
Tags
- Deployment & Operations250 Topics
- Cloud PBX186 Topics
- Voice174 Topics
- PSTN Calling156 Topics
- Skype for Business Adoption156 Topics
- Desktop Client137 Topics
- Conferencing-Meeting Join119 Topics
- devices103 Topics
- Skype for Business100 Topics
- Instant Messaging & Presence81 Topics