gMSA-based services can't log on after a password change in a Windows Server 2012 R2 domain

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 FoundationWindows Server 2012 R2 Standard

Symptoms


Consider the following scenario:
  • In a Windows Server 2012 R2 domain environment, you have a group of domain member servers. These member servers are running one or more services that use a group Managed Service Account (gMSA).
  • The user password that is used to run the services is automatically updated.

In this scenario, some services in the gMSA may be unable to log on for a short period immediately after the password change. This causes service downtime. Additionally, an "Access Denied" error is returned to the service.

Cause


This problem occurs after the changed password is replicated to all the domain controllers. However, the gMSA server still uses the older password for a brief period during the password rollover period. When the gMSA server tries to log on to the domain controller that has the updated password in this situation, the "Access Denied" error is returned.

Resolution


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

Get the update rollup for Windows Server 2012 R2

To resolve this issue, install the update rollup that is dated November 2014. 

Get the November 2014 update rollup for Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2

Get the hotfix for Windows Server 2012 R2

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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, go to 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 update, you must first have update 2919355  installed in Windows Server 2012 R2.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

Status


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

References


Learn about the terminology that Microsoft uses to describe software updates.