Current environment: Load balancer --> Two WAP servers (each wap has local host dns file pointing to a specific adfs server) --> two adfs servers. Version is 3.0. and database is hosted in external SQL server with adfsconfiguration and artifact databases.
My plan:
Create a new 2019 in parallel with 2 wap and 2 adfs. But this time I do not want to host the database externally and use WID for new environment. So, one of the adfs server will be primary and the other secondary. My questions then:
What should the architecture be like? Eg. with new WAP behind network load balancer how to best set up the backend adfs with WID since one acts as primary and the other secondary? Is it still required that the local host file of each wap point to a specific adfs? Trying to understand how the requests would be routed from load balancer to wap to adfs in such case.
The current environment has custom onload.js for appending the domain name to the username and also some changes on the default placeholder names. What is the best way to migrate the current config and settings to the new one?
I am not sure if artifact database is used in the current scenario. It sounds like with WID option the artifact db doesn't get installed. How to verify if that is being used currently? Or, does it even make any difference?
It would be nice to be able to create an environment in parallel, have configs and settings from current migrated over, test, and then cutover at convenience. Couldn't find a good documentation that provided at least an overview for such scenario. Most point to doing an inplace upgrade.
I have gone through
https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/upgrading-to-ad-fs-in-windows-server