[This blog posting was written with knowledge based on Windows Server 2016 TP4. Things may change in RTM.]
Some more investigations with ADFS in Windows Server 2016 TP4 – you have to start somewhere, right?
There are two ADFS servers that I mean to replace with two new ones on 2016 TP4, and then raise the farm behavior level. Easy enough – or so.
- Swap ADFS servers
- Use the Test-ADFSFarmBehaviorLevelRaise CMDlet to test the procedure
- Raise the ADFS Farm Behavior Level with Invoke-ADFSFarmBehaviorLevelRaise
The installation worked identical to installations with 2012 R2, when adding new nodes to an existing farm – in the end, there’s no difference between adding 2012 R2-based ADFS nodes to an existing farm or 2016-based nodes.
- join to the domain
- install the Service Communication cert on the new boxes
- install ADFS role
- add box to Load Balancer (probing will only activate it, when the service starts responding)
- join to ADFS farm
- Verify installation went good, event log is clean, WID replication worked