Tuesday, June 12, 2018

Executing Test-CsFederatedPartner throws the error: “No matching cluster found in topology.”


You attempt to use the Test-CsFederatedPartner cmdlet ( to test a configured partner federation but receive the following error:

PS C:\> Test-CsFederatedPartner -TargetFqdn -Domain

Test-CsFederatedPartner : No matching cluster found in topology.

At line:1 char:1

+ Test-CsFederatedPartner -TargetFqdn -Domain

tokiomillenn ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


+ CategoryInfo : ResourceUnavailable: (:) [Test-CsFederatedPartne

r], InvalidOperationException

+ FullyQualifiedErrorId : NoMatchingClusterFound,Microsoft.Rtc.Management.


PS C:\> Test-CsFederatedPartner -TargetFqdn -Domain



I’ve been asked about this error quite frequently every so often so I hope this blog post will help anyone who may be searching for this error when using the cmdlet. The most frequent cause of this issue is if you did not specify the correct value for the TargetFqdn switch as most administrators tend to misinterpret that as being the external partner’s Edge server SIP address and having this incorrect value would throw the error. The correct value for this switch is actually the internal FQDN name of the local Edge server. Using the correct value for this switch with the domain switch will allow the test to execute and return the result similar to the following output:

Target Fqdn :

Result : Success

Latency : 00:00:00

Error Message :

Diagnosis :


No comments: