Skype for Business Server Recovery Expert
Budget: $250 – $750 USD
Project Description:
Title: Urgent Support Required: Skype for Business 2019 Enterprise Pool - Windows Fabric Quorum Loss Recovery
Hello Everyone,
We are facing a critical production issue with our Skype for Business Server 2019 Enterprise Pool environment consisting of 3 Front End Nodes, and we need an expert to help us bring it back online safely.
Current Situation & Backend Infrastructure Status:
SQL Backend: The backend is running on SQL Server AlwaysOn. Following a major database outage, the original Availability Group Listener configuration was corrupted/deleted.
Listener Restored: We have already fixed the database layer. We successfully re-created the AG Listener via T-SQL under the exact name expected by the topology (sfb-sql-listene) on a new IP (172.16.15.165). The listener is now completely Online inside the Windows Failover Cluster Manager, and the corresponding A-record has been fully updated in our Infoblox DNS.
The Core Issue: The Skype for Business Front End services (RTCSRV and RTCCPS) fail to start. Because the entire 3-node pool dropped simultaneously during the initial SQL crash, we are stuck in a hard Windows Fabric Quorum Loss state. The local services clear their cache but drop back to a "Stopped" state upon manual service startup attempts due to the lack of a cluster majority.
What we need from you:
We need an expert to safely guide our engineering team through recovering the Windows Fabric cluster and forcing/syncing the core Front End services back to a Running state. We prefer to execute one of the following approaches based on your assessment:
Properly force-start the pool on the primary node by bypassing the standard quorum constraint via management shell (Start-CsPool -IsPrimaryComputerFailureRecovery).
Or coordinate and sync the clean initial startup sequence between the multiple Front End nodes (FE-1 and FE-2) to satisfy the native Windows Fabric quorum safely without causing a split-brain scenario.
Requirements:
Proven hands-on experience with Skype for Business Server 2019 Enterprise Pools.
Deep expertise in Windows Fabric Clustering troubleshooting and lifecycle management.
Strong knowledge of SQL AlwaysOn integration with SfB Topologies.
Please apply only if you have resolved exact Windows Fabric quorum loss scenarios in enterprise environments before. Ready to start immediately.
Title: Urgent Support Required: Skype for Business 2019 Enterprise Pool - Windows Fabric Quorum Loss Recovery
Hello Everyone,
We are facing a critical production issue with our Skype for Business Server 2019 Enterprise Pool environment consisting of 3 Front End Nodes, and we need an expert to help us bring it back online safely.
Current Situation & Backend Infrastructure Status:
SQL Backend: The backend is running on SQL Server AlwaysOn. Following a major database outage, the original Availability Group Listener configuration was corrupted/deleted.
Listener Restored: We have already fixed the database layer. We successfully re-created the AG Listener via T-SQL under the exact name expected by the topology (sfb-sql-listene) on a new IP (172.16.15.165). The listener is now completely Online inside the Windows Failover Cluster Manager, and the corresponding A-record has been fully updated in our Infoblox DNS.
The Core Issue: The Skype for Business Front End services (RTCSRV and RTCCPS) fail to start. Because the entire 3-node pool dropped simultaneously during the initial SQL crash, we are stuck in a hard Windows Fabric Quorum Loss state. The local services clear their cache but drop back to a "Stopped" state upon manual service startup attempts due to the lack of a cluster majority.
What we need from you:
We need an expert to safely guide our engineering team through recovering the Windows Fabric cluster and forcing/syncing the core Front End services back to a Running state. We prefer to execute one of the following approaches based on your assessment:
Properly force-start the pool on the primary node by bypassing the standard quorum constraint via management shell (Start-CsPool -IsPrimaryComputerFailureRecovery).
Or coordinate and sync the clean initial startup sequence between the multiple Front End nodes (FE-1 and FE-2) to satisfy the native Windows Fabric quorum safely without causing a split-brain scenario.
Requirements:
Proven hands-on experience with Skype for Business Server 2019 Enterprise Pools.
Deep expertise in Windows Fabric Clustering troubleshooting and lifecycle management.
Strong knowledge of SQL AlwaysOn integration with SfB Topologies.
Please apply only if you have resolved exact Windows Fabric quorum loss scenarios in enterprise environments before. Ready to start immediately.