We have an issue when converting from claims to ADFS

Weve tried the steps defined in this article https://support.microsoft.com/en-us/kb/3042604
The UseDefaultConfiguration and IdentifierClaimIs parameters were not vaild
Also could not create a custom claim provider with the same name as the token issuer. Tried several attempts.

We are executing this script:

add-pssnapin microsoft.sharepoint.powershell -EA 0
$wa = Get-SPWebApplication -Identity https://xxxx.xxxxx.com
$tp= Get-SPTrustedIdentityTokenIssuer
Convert-SPWebApplication -Identity $wa -TO CLAIMS-TRUSTED-DEFAULT -FROM CLAIMS-WINDOWS -TrustedProvider $tp -sourceskiplist c:\scripts\skip.csv

It throws the following error:

Convert-SPWebApplication : Exception of type 'System.ArgumentException' was thrown.
Parameter name: configuration
At C:\DevProjects\SP2013\Scripts\ClaimstoSAML.ps1:4 char:1
+ Convert-SPWebApplication -Identity $wa -TO CLAIMS-TRUSTED-DEFAULT -FROM CLAIMS-W ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Share...tWebApplication:SpCmdletConvertWebApplication) [Convert-SPWebApplication
   ], ArgumentException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SpCmdletConvertWebApplication

The corresponding ULS entries are:

07/08/2015 07:41:42.41  PowerShell.exe (0x4E5C)             0x3338  SharePoint Foundation Claims Authentication                amcpj    Unexpected       Trusted login provider has claim provider that isn't SPTrustedBackedByActiveDirectoryClaimProvider. TrustedLoginProvider: 'ADFS'.              3d5d6ce4-728b-4cc0-b0cf-5d22cbeb9737
07/08/2015 07:41:42.45  PowerShell.exe (0x4E5C)             0x3338  SharePoint Foundation PowerShell         6tf2        High                System.ArgumentException: Exception of type 'System.ArgumentException' was thrown.  Parameter name: configuration     at Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByActiveDirectoryClaimsMigration..ctor(SPTrustedClaimsMigrationConfiguration configuration)     at Microsoft.SharePoint.PowerShell.SpCmdletConvertWebApplication.UpdateDataObject()     at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()     3d5d6ce4-728b-4cc0-b0cf-5d22cbeb9737
07/08/2015 07:41:42.45  PowerShell.exe (0x4E5C)             0x3338  SharePoint Foundation PowerShell         91ux      High                Error Category: InvalidData    Target Object  Microsoft.SharePoint.PowerShell.SpCmdletConvertWebApplication  Details  NULL  RecommendedAction NULL                3d5d6ce4-728b-4cc0-b0cf-5d22cbeb9737

Any help would be appreciated.

Thanks,

Nate

Well you aren't converting from claims to ADFS, you're converting Windows based claims identities to ADFS based claims identities. They are both forms of Claims, it's niggling but the syntax matters.

Speaking of which, that support article is wrong, or at least contradicts technet.

https://technet.microsoft.com/en-gb/library/dn744263.aspx

They don't have the hyphens in the CLAIMS-TRUSTED etc. bits. That would explain why you're getting an invalid argument error, the argument you gave isn't a valid choice.

As you can see in the script, we figured out the hyphens but still throws the error.

Thanks for responding.