Adding ADFS Windows server 2019 second node failed

amr naeem 1 Reputation point

we have already ADFS 2019 farm with two servers, suddenly ADFS service stopped on the second node. So, after troubleshooting, we decided to remove the role from the second node and delete the internal DB .
So, when trying to add the ADFS role again on the same server we received errors:

  • There was no SPNs set on the service account
  • SOAP security negotiation for with http://servername/adfs/services/policystoretransfer
  • value account be null
  • unable to retrieve group managed service account information
  • unable to determine the service SPN . there were no SPNs set on the following service account
  • unbale to determine the current behavior level. SOAP security negotiation
  • unable to retrieve configuration from the primary servers

tried the following :

  • verify MSA was registered SPN (host\fs.domain name)
  • registred SPN again, the result was duplicated -Setspn - s host/FQDN service account and Setspn - s host/server name serviceaccount
  • port 80 and 443 opened / no firewall between servers
  • domain controller reached and DNS resolved successfully
  • verify that the computer account listed under allowed to retrieve managed password by using Get-ADserviceaccount
  • try to add new server to the ADFS farm but with the same error
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,220 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 39,506 Reputation points


    Thank you for your question and reaching out.

    I can understand you are not able to add another Node in ADFS.

    You could try below steps to resolve the issue.

    1. Change Logon Domain controller do Different DC as below command.

    nltest /\srv001

    1. Please try to create new ADFS server with New Name as it may happened due stale or Orphne records of Old ADFS server in the AD.
    2. Disable any Antivirus program or Windows firewall you may have for temporary purpose.
    3. Please verify AD health is Good and DATE and Time are synced your Domain controller.

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments