The original AD FS 2.0 server was deployed using the WID and Farm options for Office 365.
- WID is suitable for the majority of deployments (if it is not you will know about it)
- Choosing WID sets the first server deployed to be the primary
- Only the primary server can write configuration changes to the database
- Opting for a Farm provides scope for HA and scale
Log on to the
new primary server (NEUADFS02) and run PowerShell.
Add-PsSnapin Microsoft.Adfs.PowerShell
Set-AdfsSyncProperties -Role PrimaryComputer
On all other AD FS servers in the farm run the following.
Add-PsSnapin Microsoft.Adfs.Powershell
Set-AdfsSyncProperties -Role SecondaryComputer
-PrimaryComputerName NEUADFS02.EXCHANGEGEEK.COM
On a related note, I also identified that TCP/80 should be open between farm members, despite all resources and configuration identifying only TCP/443 as required. This came up when extending the farm across data center boundaries.