Partilhar via

ADFS 2016 - Cannot add/update Relying Parties from the GUI from metadata files "Method not found"

  • Artigo

UPDATE: The following update is fixing this issue:

If you are currently using the October release of Windows Server 2016 (build: 10.0.14393 N/A Build 14393) you might experience a weird error message when you try to add a relying party trust or update a relying party trust with the metadata files. Whether it is from an HTTPs source or even a local XML files that you previously saved, you have the following message:

GUI_METADATA_1

It seems that adding or updating a relying party from the console currently does not work as expected. If you don't know what version of Windows you are running, you can run the command "systeminfo" in command prompt and look at the build line.

But no worry, you can still do the job thanks to our good old friend PowerShell.

Adding a relying party trust from an online metadata file:

 Add-AdfsRelyingPartyTrust -Name "My App" -MetadataUrl "https://web.piaudonn.com/app/federationmetadata/2007-06/federationmetadata.xml"

Adding a relying party trust from a metadata saved on the your ADFS server:

 Add-AdfsRelyingPartyTrust -Name "My App" -MetadataFile "C:\Temp\FederationMetadata.xml"

Updating the relying party trust from the metadata file already set on the properties of the trust:

 Update-AdfsRelyingPartyTrust -TargetName "My App"

This will probably be fixed very soon!

Comments

  • Anonymous
    October 24, 2016
    Thanks Pie, that just worked.PS1 rocks.
  • Anonymous
    October 30, 2016
    Thank you sir!implementing a complete windows infrastructure is truly overwhelming!
  • Anonymous
    November 07, 2016
    I also have a bug, on server 2016, i cannot update the text of the default tile "Active Directory". have you the same issue ?
  • Anonymous
    December 06, 2016
    And by "very soon" you mean it's not fixed yet after 2 months :)Well done, Microsoft!
  • Anonymous
    December 09, 2016
    I can confirm this issue is now resolved by installing KB3201845.https://support.microsoft.com/en-us/kb/3201845Many Thanks
  • Anonymous
    January 03, 2017
    Turns out that Microsoft pulled the update 3201845 on December 12th, mentioned as resolving this issue on December 9th.Source: http://www.infoworld.com/article/3149590/microsoft-windows/microsoft-pulls-kb-article-3201845-for-windows-10-14393479.html3206632 was released on December 13th, and this page: https://support.microsoft.com/en-us/help/4004227/windows-10-update-kb3206632says that it replaces 3201845
  • Anonymous
    July 26, 2018
    Thanks for this .. i have been trying to understand why this error keeps poping up for 2 days now.
  • Anonymous
    August 08, 2018
    Hi , i am having this exact issue for 1 of my relying trusts, the only thing that worked for me was update-AdfsRelyingPartyTrust -TargetName "My App" -MetadataFile "C:\Temp\FederationMetadata.xml"My Windows 2016 server says its up to date with windows updates. any ideas on how to get around this manual process? I tried to manually download and install the updates and prereqs and they failed stating not applicable to my OS.