ADFS 2016 upgrade to 2019

Anonymous
2021-12-07T13:13:39.427+00:00

Hello,

I need to upgrade ADFS 2016 to 2019. We use SQL db.
I installed a new ADFS 2019 server, added that into farm.
Both ADFS servers work fine.

I see this article: https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/upgrading-to-ad-fs-in-windows-server
But that for WID db.

Using SQL Server to store the AD FS configuration database
The term "primary federation server" does not apply when the AD FS configuration database is stored in a SQL database instance because all federation servers can equally read and write to the AD FS configuration database that is using the same clustered SQL Server instance, as shown in the following illustration.
You can use SQL Server to configure two or more servers to work together as a server cluster to ensure that AD FS is made highly available to service incoming client requests. High availability provides a scale-out architecture in which you can increase server capacity by adding additional servers. Single points of failure are mitigated by automatic cluster failover.

What should be my next steps ?

Decomiss ADFS 2016
Install new server 2019
Add this server into ADFS farm

How to update SQL db to AdfsConfigurationV4 ?
At the moment SQL db is AdfsConfigurationV3.

...

Thanks

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,166 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Pierre Audonnet - MSFT 10,151 Reputation points Microsoft Employee
    2021-12-09T20:30:51.763+00:00

    The process stays the same. Just that you can do the upgrade from any server.
    That said I would maybe take this as an opportunity to move away from SQL as a backend (unless you have a valid reason to use SQL as a backend?).

    Using ADFS Rapid Restore, you can backup the environment and restore it using a WID configuration. I would do that on a new server, and then cut off the SQL based one. Once this is done, I'd upgarde the new WID farm.

    0 comments No comments