Forum Widgets
Latest Discussions
Migration from 2015 to SFB 2019 with SQL FCI
Hi, Customer have a 2015 setup with SQL Mirroring. All working fine so far. Now we Setup a WFCI with CSV and an SQL FCI. The installation ran smooth and we can access the SQL FCI Name via SQL Management Studio. Also test with port 1433 and 1434 are working. Permissions are checked and we have sa rights on the Databases. After Setting up the 2019 environment in the Topology the Databases for the 2019 environment cannot be installed on the SQL FCI. Always the same error, trying with Install-CSDatabse or with the TB. User also have sa rights. After 10minutes this error occured : ****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.XdsDatabase'**** Initializing DbSetupBase Parsing parameters... Found Parameter: SqlServer Value cluster.lab.com. Found Parameter: SqlFilePath Value C:\Program Files\Common Files\Skype for Business Server 2019\DbSetup. Found Parameter: DatabaseType Value CentralMgmt. Found Parameter: FeatureName Value CentralMgmtStore. Found Parameter: DatabaseNames Value System.Collections.Generic.List`1[System.String]. Found Parameter: Publisheracct Value LWK\RTCUniversalServerAdmins. Found Parameter: Replicatoracct Value LWK\RTCUniversalConfigReplicator. Found Parameter: Consumeracct Value LWK\RTCUniversalReadOnlyAdmins. Found Parameter: Role Value master. Trying to connect to Sql Server cluster.lab.com. using windows authentication... Sql version: Major: 16, Minor: 0, Build 1000. Sql version is acceptable. Validating parameters... DbName xds validated. SqlFilePath C:\Program Files\Common Files\Skype for Business Server 2019\DbSetup validated. DbFileBase xds validated. DbPath is not specified, using default. Default DB Path is C:\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\. DbPath C:\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\ validated. Effective database Path: \\cluster.lab.com\C$\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\. LogPath is not specified, using default. Default Log Path is C:\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\. LogPath C:\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\ validated. Effective Log Path: \\cluster.lab.com\C$\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\. Checking state for database xds. Checking state for database xds. Checking state for database xds. State of database xds is detached. Attaching database xds from Data Path \\cluster.lab.com\C$\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\, Log Path \\cluster.lab.com\C$\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\. The operation failed because of missing file '\\cluster.lab.com\C$\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\xds.mdf' Attaching database failed because one of the files not found. The database will be created. State of database xds is DbState_DoesNotExist. Creating database xds from scratch. Data File Path = C:\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\, Log File Path= C:\ClusterStorage\Volume1\MSSQL16.MSSQLSERVER\MSSQL\DATA\. Clean installing database xds. System.IO.IOException: The network name cannot be found. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost) at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost) at Microsoft.Rtc.Common.Data.DatabaseManager.CreateDatabase(String dbFileBase, String dbPath, String logPath, Int32 dbSizeMB, Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32 maxLogSizeMB) at Microsoft.Rtc.Common.Data.DatabaseManager.CleanInstallDatabase(String dbFileBase, String initialScripfilePath, String dbPath, String logPath, Int32 dbSizeMB, Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32 maxLogSizeMB) at Microsoft.Rtc.Common.Data.DbSetupBase.CleanInstallDatabase() at Microsoft.Rtc.Common.Data.DbSetupBase.CreateOrUpdateDatabase() at Microsoft.Rtc.Common.Data.XdsDatabase.CreateOrUpdateDatabase() at Microsoft.Rtc.Management.Deployment.Tasks.DatabaseCreator.CreateDatabaseForFeature(String featureName, Boolean clean, Boolean update, String sqlServer, String instanceName, String databaseType, List`1 databaseNames, Boolean collocated, Boolean backup, Boolean noreindex, DatabasePathAssignment[] pathAssignments, Boolean broadCast, String& logfile) We tried nearly everything. But SQL FCI with Skype for Business seems not so common. Thank you for Help Br. Ralf
Unable to download 7.0.2046.524 Core Components update?
I am met with a 403 forbidden when I try to download the https://support.microsoft.com/da-dk/topic/kumulativ-opdatering-juli-2023-7-0-2046-524-til-skype-for-business-server-2019-core-components-da442534-7f70-424c-b531-842de37453e5 Cumulative Update july 2023 7.0.2046.524 for Skype for Business Server 2019, Core Components from https://support.microsoft.com/da-dk/topic/opdateringer-for-skype-for-business-server-2019-kb4470124-890f4878-c6fe-f71b-c85f-db2acc284b94 I have downloaded all other 7.0.2046.524 updates without problems. Does anyone know what is going on here?
Skype Meeting App issue
Having an issue with invitees joining Skype For Business 2019 meetings hosted on on-premises. Using the join meeting URL externally brings up a blank screen with the thinking wheel of dots. Using the same URL on the same browser with ?SL= appended to it brings up the Guest sign in screen.Skype for Business Server 2019 IM Integration with Exchange Server 2019
I am having difficulty getting the IM/Presence integration to work between my on-prem Skype for Business 2019 Server and my Exchange 2019 Server. I believe I am having a certificate trust issue. On important note is that my internal domain is domain.local and the external is domain.com. So, my public wildcard certificate is for *.domain.com. When I look at the certificates on the exchange server, there is another certificate that is assigned to IIS issued by the local certificate authority which protects domain.local. I have tried a variety of combinations using either the local certificate with the domain.local name of the servers as well as the public wildcard certificate thumbprint and the dns a record with domain.com that points to each server. None of these combinations seem to work for me. I have run these commands on the SfB Server: New-CsTrustedApplicationPool -Identity exchangeserver.domain.local -Registrar sfbserver.domainlocal -Site "My Site" -RequiresReplication $False New-CsTrustedApplication -ApplicationId OutlookWebApp -TrustedApplicationPoolFqdn exchangeserver.domain.local -Port 5199 I have run these commands on the Exchange Server: New-SettingOverride -Name "IM Override" -Component OwaServer -Section IMSettings -Parameters @("IMServerName=sfbserver.domain.local","IMCertificateThumbprint=mycertificatethumbprint") -Reason "Configure IM" Get-ExchangeDiagnosticInfo -Server EXCHANGESERVER -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh Restart-WebAppPool MSExchangeOWAAppPool Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -InstantMessagingEnabled $True -InstantMessagingType OCS When I check the instant messaging logs on the Exchange Server I see the following: If I try to use the domain.com name and the wildcard certificate I get this error: ERROR:InstantMessageOCSProvider.GenerateInstantMessageUnavailablePayload. Context: User=email address removed for privacy reasons, Sip address=sip:email address removed for privacy reasons, Lyncserver=sfbserver.domain.local. endPoint: Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint, MethodName: InstantMessageOCSProvider.SignInCallback, InstantMessageServiceError: SipEndpointConnectionFailure, Exception: UCWEB Failure: Code=TlsFailure, SubCode=TlsIncorrectNameInRemoteCertificate, Reason=\r\nMicrosoft.Rtc.Internal.UCWeb.Utilities.UCWException: The target principal name is incorrect ---> Microsoft.Rtc.Signaling.TlsFailureException: The target principal name is incorrect ---> Microsoft.Rtc.Internal.Sip.TLSException: outgoing TLS negotiation failed; HRESULT=-2146893022\r\n at Microsoft.Rtc.Internal.Sip.TlsTransportHelper.HandleNegotiationFailure(Int32 status, Boolean incoming)\r\n at Microsoft.Rtc.Internal.Sip.TlsTransportHelper.OutgoingTlsNegotiation(TransportsDataBuffer receivedData, TransportsDataBuffer& pDataToSend)\r\n at Microsoft.Rtc.Internal.Sip.TlsTransportHelper.NegotiateConnection(TransportsDataBuffer receivedData, TransportsDataBuffer& pDataToSend)\r\n at Microsoft.Rtc.Internal.Sip.TlsTransport.DelegateNegotiation(TransportsDataBuffer receivedData)\r\n at Microsoft.Rtc.Internal.Sip.TlsTransport.OnReceived(Object data)\r\n --- End of inner exception stack trace ---\r\n at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()\r\n at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result)\r\n at Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint.OotyUserEndpointEstablish_callback(IAsyncResult asyncResult)\r\n --- End of inner exception stack trace ---\r\n at Microsoft.Rtc.Internal.UCWeb.Utilities.AsyncHelper.EndAsyncCall[T](IAsyncResult asyncResult, String methodName, T ucwScopeInstance)\r\n at Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint.EndSignIn(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.Clients.Owa2.Server.Core.InstantMessageOCSProvider.<>c__DisplayClass89_0.<SignInCallback>b__0(RequestDetailsLogger logger)", When I use the internal domain.local server name and the certificate issued by the local certificate authority, I see: 2024-02-25T14:36:21.783Z,19,5,,,,0,"DEBUG:InstantMessageOCSProvider.SignInCallback. Ignoring exception after the connection is closed: Context User=email address removed for privacy reasons, Sip address=sip:email address removed for privacy reasons, Lyncserver=sfbserver.domain.local, Exception: UCWEB Failure: Code=TlsFailure, SubCode=TlsRemoteDisconnected, Reason=\r\nMicrosoft.Rtc.Internal.UCWeb.Utilities.UCWException: Unknown error (0x80131500) ---> Microsoft.Rtc.Signaling.TlsFailureException: Unknown error (0x80131500) ---> Microsoft.Rtc.Internal.Sip.RemoteDisconnectedException: Peer disconnected while outbound capabilities negotiation was in progress ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host\r\n at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)\r\n at Microsoft.Rtc.Internal.Sip.TcpTransport.OnReceived(Object arg)\r\n --- End of inner exception stack trace ---\r\n --- End of inner exception stack trace ---\r\n at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()\r\n at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result)\r\n at Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint.OotyUserEndpointEstablish_callback(IAsyncResult asyncResult)\r\n --- End of inner exception stack trace ---\r\n at Microsoft.Rtc.Internal.UCWeb.Utilities.AsyncHelper.EndAsyncCall[T](IAsyncResult asyncResult, String methodName, T ucwScopeInstance)\r\n at Microsoft.Rtc.Internal.UCWeb.UCWAuthenticatedEndpoint.EndSignIn(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.Clients.Owa2.Server.Core.InstantMessageOCSProvider.<>c__DisplayClass89_0.<SignInCallback>b__0(RequestDetailsLogger logger)",On MACP, (400 : HTTP/1.1 400 Bad Request) when enabling a user.
Hello everyone! My problem is: When enabling a user on the new MACP, IF the user has configured an email address gives the subjet error. If the user doesn't have configured email address, user is enabled but not without a problem. Viewing trough developer mode on the browser, the error lies in: https://<sfbs-fe-pool-fqdn>/OcsPsws/Service.svc//$batch The payload of the $batch: --batch_1706182664593 Content-Type: multipart/mixed; boundary=changeset_21.25566040805762 --batch_1706182664593 Content-Type: multipart/mixed; boundary=changeset_21.25566040805762 --changeset_21.25566040805762 Content-Type: application/http Content-Transfer-Encoding: binary PATCH /OcsPsws/Service.svc/CsAdUser/fragments/2/<BLABLABLA> HTTP/1.1 Content-Type: application/json {"SipAddressType":"EmailAddress","SipDomain":"<domain.tld>","RegistrarPool":"<sfbs-fe-pool-fqdn>"} --changeset_21.25566040805762-- --batch_1706182664593 Content-Type: multipart/mixed; boundary=changeset_21.25566040805762 --changeset_21.25566040805762 Content-Type: application/http Content-Transfer-Encoding: binary PATCH /OcsPsws/Service.svc/CsUser/fragments/2/<BLABLABLA> HTTP/1.1 Content-Type: application/json {"AudioVideoDisabled":false,"EnterpriseVoiceEnabled":false,"RemoteCallControlTelephonyEnabled":false} --changeset_21.25566040805762-- --batch_1706182664593-- Gives this error without regards of wich option i choose about the format of the sip address (email, UPN, etc.): HTTP/1.1 400 Bad Request X-Content-Type-Options: nosniff DataServiceVersion: 1.0; Content-Type: application/xml;charset=utf-8 <?xml version="1.0" encoding="utf-8"?><m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code /><m:message xml:lang="es-ES">The request URI is not valid. Since the segment 'CsAdUser' refers to a collection, this must be the last segment in the request URI. All intermediate segments must refer to a single resource.</m:message></m:error>--changesetresponse_a677ace1-29ed-4549-b606-2b90d0a4d6d8-- --batchresponse_681cb375-bac7-4afe-a2fa-9ceb5f199d4aContent-Type: multipart/mixed; boundary=changesetresponse_608de08e-6dbe-4000-aab4-95c97c576d09 --changesetresponse_608de08e-6dbe-4000-aab4-95c97c576d09 Content-Type: application/http Content-Transfer-Encoding: binary HTTP/1.1 400 Bad Request X-Content-Type-Options: nosniff DataServiceVersion: 1.0; Content-Type: application/xml;charset=utf-8 <?xml version="1.0" encoding="utf-8"?> <m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code /><m:message xml:lang="es-ES">The request URI is not valid. Since the segment 'CsUser' refers to a collection, this must be the last segment in the request URI. All intermediate segments must refer to a single resource.</m:message></m:error> --changesetresponse_608de08e-6dbe-4000-aab4-95c97c576d09-- --batchresponse_681cb375-bac7-4afe-a2fa-9ceb5f199d4a-- And, when enabling a user without a configured email address, the payload of $batch looks like this: --batch_1706183087284 Content-Type: multipart/mixed; boundary=changeset_3.9714624502973583 --batch_1706183087284 Content-Type: multipart/mixed; boundary=changeset_3.9714624502973583 --changeset_3.9714624502973583 Content-Type: application/http Content-Transfer-Encoding: binary PATCH /OcsPsws/Service.svc/CsAdUser('BLABLABLA') HTTP/1.1 Content-Type: application/json {"SipAddressType":"UserPrincipalName","SipDomain":"<domain.tld>","RegistrarPool":"<sfbs-fe-pool-fqdn>"} --changeset_3.9714624502973583-- --batch_1706183087284 Content-Type: multipart/mixed; boundary=changeset_3.9714624502973583 --changeset_3.9714624502973583 Content-Type: application/http Content-Transfer-Encoding: binary PATCH /OcsPsws/Service.svc/CsUser('<BLABLABLA>') HTTP/1.1 Content-Type: application/json {"AudioVideoDisabled":false,"EnterpriseVoiceEnabled":false,"RemoteCallControlTelephonyEnabled":false} --changeset_3.9714624502973583-- On the MACP i get a spinning wheel, but if i go to users, it appears as enabled. On the browser's developer tools the server gives this answer: HTTP/1.1 500 Internal Server Error X-Content-Type-Options: nosniff Cache-Control: no-cache DataServiceVersion: 1.0; Content-Type: application/xml;charset=utf-8 <?xml version="1.0" encoding="utf-8"?><m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code /><m:message xml:lang="es-ES">An error occurred while processing this request.</m:message><m:innererror><m:message>No se pudo ejecutar el comando Set-CsUserDetails. Causa del problema: No se encontró ningún objeto de administración para la identidad "<ad user distinguished name>".</m:message><m:type>Microsoft.Management.Odata.CommandInvocationFailedException</m:type><m:stacktrace> en Microsoft.Management.Odata.PS.PSCommand.ExecutionCompletionHandler()
 en Microsoft.Management.Odata.PS.PSCommand.Invoke(Expression expression, Boolean noStreamingResponse)
 en Microsoft.Management.Odata.Core.PSOperationManager.InvokeCRUDCommand(CommandType commandType, String resourceTypeName, IEnumerable`1 properties)
 en Microsoft.Management.Odata.Core.PSOperationManager.Update(SenderInfo senderInfo, String resourceTypeName, IEnumerable`1 properties)
 en Microsoft.Management.Odata.Core.OperationManagerAdapter.FunctionInvoker`1.Invoke()
 en Microsoft.Management.Odata.Core.OperationManagerAdapter.InvokeMethod(IInvoker invoker, String functionName, String resourceTypeName, Boolean ignoreNotImplementedException)
 en Microsoft.Management.Odata.Core.OperationManagerAdapter.InvokeOperationManagerFunction[T](Func`1 func, String functionName, String resourceTypeName, Boolean ignoreNotImplementedException, T defaultResultForNotImplementedException)
 en Microsoft.Management.Odata.Core.OperationManagerAdapter.CUDRequest(CommandType commandType, ResourceType resourceType, Dictionary`2 properties, Dictionary`2 urlParams)
 en Microsoft.Management.Odata.Core.EntityUpdate.InvokeCommand()
 en System.Data.Services.DataService`1.BatchDataService.HandleBatchContent(Stream responseStream)</m:stacktrace><m:internalexception><m:message>No se encontró ningún objeto de administración para la identidad "CN=Carmen Morillo Rodriguez,OU=USUARIOS,OU=CUENTAS DESHABILITADAS,OU=OU _01_VARIOS,DC=depo,DC=es".</m:message><m:type>Microsoft.Rtc.Management.AD.ManagementException</m:type><m:stacktrace> en Microsoft.Rtc.Management.AD.ADTask`1.GetDataObject[TDataObject](IIdentity id, IDirectorySession session, ObjectId rootID)
 en Microsoft.Rtc.Management.AD.ADTask`1.GetDataObject(IIdentity id)
 en Microsoft.Rtc.Management.AD.SetPersonBase`2.ResolveDataObject()
 en Microsoft.Rtc.Management.AD.GenericSetADObjectIdentityTask`3.PrepareDataObject()
 en Microsoft.Rtc.Management.AD.GenericSetADTask`1.InternalValidate()
 en Microsoft.Rtc.Management.AD.ADTask`1.PrepareForScopeCheck()
 en Microsoft.Rtc.Management.OcsCmdlet.IsUserInScope()
 en Microsoft.Rtc.Management.OcsCmdlet.ProcessRecord()
 en System.Management.Automation.CommandProcessor.ProcessRecord()</m:stacktrace></m:internalexception></m:innererror></m:error> --changesetresponse_42f57019-b938-47b1-a3f6-aaf2a7bb23c8-- --batchresponse_c7d33751-d003-448c-89db-4ebcda4bc6ae-- The only difference is that on the failing payload i see: PATCH /OcsPsws/Service.svc/CsAdUser/fragments/2/<BLABLABLA> And on the working payload: PATCH /OcsPsws/Service.svc/CsAdUser('<BLABLABLA>') Sounds like a bug? Configuration problem?? Edit: I forgot to mention the environment - SfBS 2019, patched to October 2023 level. Three Win servers 2019 as front-ends, two win server 2019 as Edges. Applied, as patch requested, the prerequisites without errors. bootstrapper executed without errors. 🤷:male_sign:Skype for Business 2019 Edge Server with other RD Gateway
I have a Skype for Business 2019 Standard Edition Server currently running without the Edge Transport server. I'd like to add remote access but would prefer not to have to deploy another server specifically dedicated to this. Does anyone know (or has anyone tried) installing Skype for Business 2019 Edge Server on the same machine as a terminal server running RD Gateway and RD Web Apps? Or, is there any other server this could run on without interfering? I have a server running Office Online Server (OOS) and I have another running Sharepoint, one running Exchange 2019, one running Skype for Business 2019 frontend and then the one running RD Gateway and RD Web Apps as a terminal server. Thanks!
Decommission Skype 2015 On-Prem servers
I want to decommission our Skype On-Prem (2015) servers and cleanup AD from the RTC delegations and groups (RTC* and CS*). I've been following the guide: https://learn.microsoft.com/en-us/skypeforbusiness/hybrid/decommission-remove-on-prem However, when doing step 1 of "Prepare to remove the Skype for Business deployment" and run the commands, the command Get-CsAudioTestServiceApplication returns an object. In step 2 there is no corresponding Remove-cmdlet, so we tried disabling it with the Set-cmdlet. Moving on to "Remove your on-premises Skype for Business deployment", when getting to step 3 I run "Publish-CsTopology -FinalizeUninstall" but gets the following error. Publish-CsTopology : Command execution failed: Cannot publish topology changes. Users or contacts are still homed on a pool that would be deleted. Move or remove the users or contacts before continuing. At line:1 char:1 + Publish-CsTopology -FinalizeUninstall + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Publish-CsTopology], Inva lidOperationException + FullyQualifiedErrorId : ProcessingFailed,Microsoft.Rtc.Management.Deploy ment.PublishTopologyCmdlet Running the command generates a html file with the result, where the same error can be found and the following suggestion: "UserPoolInUseResolution: Consult your Skype for Business Server documentation to learn how to move or disable objects still homed on the pool. To find those objects, execute the following cmdLets: Get-CsUser, Get-CsExUmContact, Get-CsCommonAreaPhone, Get-CsAnalogDevice, Get-CsRgsWorkflow, Get-CsDialInConferencingAccessNumber, Get-CsAudioTestServiceApplication, Get-CsTrustedApplicationEndpoint, Get-CsPersistentChatEndpoint." So I'm guessing we need to get rid of that Audio Test Service Application, anyone got any ideas how to do that? I can't find anything for it in the GUI either. The main objective is to clean up any remnents in AD, the entire Skype environment will be removed and all servers decommissioned. I'm guessing that the Disable-CsAdDomain and Disable-CsAdForest cmdlets does this somewhat. Is the above steps a requirement to be able to run these cmdlets, or would this be a viable option?
Publishing new topology for additional SIP trunk.... Downtime?
Hi Just looking for a quick bit of advice here please. We have the urgent need for a new SIP trunk on an existing (working) S4B 2019 Standard deployment. From editing the topology to publishing this, will this cause any downtime to the existing Skype deployment due to just adding an additional medial gateway and SIP trunk? The rest of the configuration is staying the same. Also are there any other gotchas to be aware of? Thanks
