Servers have no way of negotiating their role in the AD FS farm, so each computer must be updated manually: Firstly, on the new Windows Server 2016 computer, set it to be the primary computer.
This enables its database for changes, and means it will no longer sync its configuration from the previous primary computer.
See here for instructions on how to do that using regedit or deploy the setting using logon scripts or Group Policy.
The great news here is that provided your Windows Server 2012 R2 servers can access the new AD FS server(s) by hostname, these will just keep on trucking If you want to go the whole hog and upgrade your WAPs to Windows Server 2016 at the same time, that’s pretty straightforward too.
In this example, our domain is litwareinc.com: The Priority specifies which target server the client should connect to first.
If two target servers have the same priority then the client looks at the weight for each and decides which to connect to based on which has the highest weight.
Removing the autodiscover.A record means that clients will not be able to connect to this address.
This is helpful as we now no longer need autodiscover.as a name on our certificate and can use a single name certificate for Exchange to cut costs and simplify the namespace.