When trying to execute BusyOnBusy cmdlets (Get-CsBusyOptions & Set-CsBusyOptions), the following error occurs:
Get-CsBusyOptions : A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)
The above error presents itself when ran from a Management Server with the Skype for Business Administrative Tools installed.
BusyOnBusy options can be ran successfully from any internal Skype for Business Servers in the Topology (e.g. Front End server, Mediation server, Trusted Application server), with the same user account. This can be via the Skype for Business Server Management Shell direct from one of the internal servers (e.g. via Remote Desktop), or Remote PowerShell.
It is successful from a Skype for Business server because of the presence of the local RTCLOCAL database. BusyOnBusy operations must be against the local RTCLOCAL SQL Instance where the cmdlet is being executed from.
Execute BusyOnBusy operations from a Skype for Business Server is the easy answer.
However, in enterprise environments, this is not likely to be an option for various security reasons. Defining the Management Server as a Trusted Application Server is a method of allowing BusyOnBusy to be ran from a non-Skype for Business production server.
Skype for Business Administrative Tools need to be installed on the Management Server (they are already installed in this case).
Trusted Application Pool
Create a Trusted Application Pool:
New-CsTrustedApplicationPool -Identity adminhost1.x500.co.uk -Registrar fepool1.x500.co.uk -ThrottleAsServer $True -TreatAsAuthenticated $True -OutboundOnly $False -RequiresReplication $True -ComputerFqdn adminhost1.x500.co.uk -Site 1
- adminhost1.x500.co.uk is the name of the Management Server.
- fepool1.x500.co.uk is the name of the Front End Pool.
- Site 1 – Site ID of my Primary Site (check Get-CsSite if you’re not sure of the Site ID).
Publish the Topology Change:
On the Management Server, run the Skype for Business Server Deployment Wizard.
Go through each of the following steps.
Step 1: Install Local Configuration Store.
Step 2: Setup or Remote Skype for Business Server Components.
Step 3: Request, Install or Assign Certificates.
Request a certificate from an Internal CA, this needs to be for the FQDN of the server (in this case it’s adminhost1.x500.co.uk), and must match what was defined in the Topology when creating a new Trusted Application Pool.
When the above is done, Get & Set-CsBusyOptions are successful from the Management Server.