Failed to add ADFS4.0 to farm

Clinton van Axel 126 Reputation points
2020-03-26T15:21:11.7+00:00

I have two ADFS 3.0 servers and two ADFSproxy servers(DMZ). All located in Azure. The machines all or load balanced.
Now i try to add a windows 2016 server (ADFS 4.0) on a different VNET but peer with the old VNET.

When i try to add the ADFS 4.0 (windows 2016 machine) I get this error.

Unable to retrieve configuration from the primary server. The specified DNS name of the primary federation server could not be resolved. Verify that the DNS name is correct, and that the AD FS service is running on the primary federation server and try again.

Active Directory Federation Services
Active Directory Federation Services
An Active Directory technology that provides single-sign-on functionality by securely sharing digital identity and entitlement rights across security and enterprise boundaries.
1,193 questions
{count} vote

Accepted answer
  1. Clinton van Axel 126 Reputation points
    2020-03-27T14:52:34.883+00:00

    Fixed the problem. I was adding the farm name and thats was only reachable from outside. So it landed on the WAP. But the question was. What is your Primary server in the farm.

    But i have a question if I add the windows 2016 (ADFS4.0) machine to the farm. Does it take all Replying party trusts. Even if i gone raise the farm level.


1 additional answer

Sort by: Most helpful
  1. Clinton van Axel 126 Reputation points
    2020-03-26T20:40:21.03+00:00

    When i open the port 80 on the adfsproxy server. i get another error:

    The HTTP service located at http://****************/adfs/services/policystoretransfer is unavailable. This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service again later.

    1 person found this answer helpful.