Trust relationships are lost on secondary AD FS server after you add or remove claims provider in Windows Server 2012 R2

This article describes an issue that occurs after you add or remove claims providers on a Windows Server 2012 R2-based Active Directory Federation Services (AD FS) server. A hotfix is available to resolve this issue. Before you install this update, check out the Prerequisites section.

Symptoms

Assume that you have an AD FS farm that uses Windows Internal Database (WID) and a relying party trust (RP) to which you have assigned one or more claims providers by using the Set-AdfsRelyingPartyTrust cmdlet together with the ClaimsProviderName parameter. When you add or remove claims providers on the primary AD FS server and the second AD FS server synchronizes with the primary AD FS server, the claims provider property on the RP is deleted.  

Cause

This issue occurs because, during the synchronization, all existing objects on the secondary server are deleted, and the current objects from the primary server are added. When the claims provider is deleted, the object that represents the RP's claims provider property is also deleted because of cascading delete.

Resolution

To resolve this issue, we have released a hotfix for Windows Server 2012 R2.

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.


A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


Prerequisites

To apply this hotfix, you must have update 2919355 installed in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

See the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3075610 - Last Review: Aug 11, 2015 - Revision: 1

Feedback