Well, technically, that's not the proper upgrade process.
The upgrade process is described here: https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/prepare-migrate-ad-fs-server-r2 (same
process to migrate from 2008 R2 to 2016/2019).
If you don't want to upgrade, you will have to re-create the trust on your new ADFS farm. You can do it with Azure AD Connect (there is wizard for ADFS setup) or simply by re-running the following command with the new information:
-
$cred = get-credential
Note When you're prompted, enter your cloud service administrator credentials.
-
Connect-MSOLService –credential:$cred
-
Set-MSOLADFSContext –Computer: <AD FS 2.0 ServerName>
Note In this command, the placeholder <AD FS 2.0 Server Name> represents the
Windows host name of the primary AD FS server.
-
Update-MSOLFederatedDomain –DomainName: <Federated Domain Name>
or
Update-MSOLFederatedDomain –DomainName: <Federated Domain Name> –supportmultipledomain
(this is described here: https://support.microsoft.com/en-us/help/2647048/how-to-update-or-repair-the-settings-of-a-federated-domain-in-office-3)
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
