adfs 2016 wid field related issues

hurry hao 221 Reputation points

I created a second adfs server and added the existing adfs wid farm when configuring it

However, the console of the second adfs server shows up. This computer is not the primary federation server in the farm, and the configuration cannot be edited or viewed.


May I ask this situation

  1. If my main federated server is down, how can I edit or view the adfs configuration
  2. How can I restore my main federated server
  3. I have shut down the main federated server in the test environment for a long time, but the synchronization time with the main server as shown in the figure above has been updated. What is updated here?
  4. I learned from the official website that there is only read-only data in the wid for the non-primary federated server. If the main federated server is offline for a long time, will the data in my wid be updated?
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,168 questions
0 comments No comments
{count} votes

Accepted answer
  1. Pierre Audonnet - MSFT 10,151 Reputation points Microsoft Employee
    1. You need to size the primary role on the secondary server. On the secondary server, type: Set-AdfsSyncProperties -Role "PrimaryComputer"
    2. At this point it is better to rebuild and join the farm that is now hosted by your former secondary (which became primary with the previous command). It is just easier that way.
    3. I can't comment on this one as I am not sure what the screenshot refers to.
    4. The secondary will not update data until you take over the primary role.

    Note that if you have more than 1 secondary server, you also need to run the following on them to make sure they also know that the primary is now one of the former secondary:

    Set-AdfsSyncProperties -Role "SecondaryComputer" -PrimaryComputerName "<FQDN of the new primary server>"
    0 comments No comments

0 additional answers

Sort by: Most helpful