You cannot log on to an AD FS server when you use an alternative UPN suffix account in Windows Server 2012 R2

Gilt für: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 R2 Essentials

Symptoms


Consider the following scenario:
  • You create domain A, domain B, and an external trust between the domains.
  • You create an Active Directory Federation Services (AD FS) server that is running Windows Server 2012 R2 in domain A.
  • You add an alternative user principal name (UPN) suffix in domain B.
  • You create a user account that uses the alternative UPN suffix in domain B.
  • You go to the AD FS server sign-in page on a computer in domain A, and then you log on by using the user account.
In this scenario, this issue occurs.

Resolution


To resolve this issue, install update rollup 2975719. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2975719 August 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

Status


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

More Information


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates