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.

The update rollup fixes many other issues in addition to the issue that the hotfix fixes. We recommend that you use the update rollup. The update rollup is larger than the hotfix. Therefore, the update rollup takes longer to download.

Get the update rollup for Windows Server 2012 R2To 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 R2A 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:

http://support.microsoft.com/contactus/?ws=supportNote 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 requirementYou must restart the computer after you apply this hotfix.

Hotfix replacement informationThis hotfix does not replace any previously released hotfix.

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 R2 file information and notesImportant Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17 xxx

    Windows Server 2012 R2

    RTM

    GDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 8.1 and Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Kerberos.dll

6.3.9600.17340

972,800

12-Sep-2014

05:12

x64

Kerberos.dll

6.3.9600.17340

783,360

12-Sep-2014

05:12

x86

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2

File name

Amd64_a8c7072a2c495029c3b27b3dca3aa54d_31bf3856ad364e35_6.3.9600.17340_none_69f189aa12ea4713.manifest

File version

Not Applicable

File size

709

Date (UTC)

12-Sep-2014

Time (UTC)

18:23

File name

Amd64_d895b43f16eac93a0764653410e1106f_31bf3856ad364e35_6.3.9600.17340_none_ab4b9967f11c1837.manifest

File version

Not Applicable

File size

709

Date (UTC)

12-Sep-2014

Time (UTC)

18:23

File name

Amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.3.9600.17340_none_d7bc64f684a7daed.manifest

File version

Not Applicable

File size

48,001

Date (UTC)

12-Sep-2014

Time (UTC)

07:48

File name

Package_1_for_kb2998082~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not Applicable

File size

1,826

Date (UTC)

12-Sep-2014

Time (UTC)

18:23

File name

Package_2_for_kb2998082~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not Applicable

File size

2,484

Date (UTC)

12-Sep-2014

Time (UTC)

18:23

File name

Package_3_for_kb2998082~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not Applicable

File size

2,289

Date (UTC)

12-Sep-2014

Time (UTC)

18:23

File name

Package_for_kb2998082_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not Applicable

File size

1,969

Date (UTC)

12-Sep-2014

Time (UTC)

18:23

File name

Package_for_kb2998082_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not Applicable

File size

2,773

Date (UTC)

12-Sep-2014

Time (UTC)

18:23

File name

Wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.3.9600.17340_none_e2110f48b9089ce8.manifest

File version

Not Applicable

File size

37,746

Date (UTC)

12-Sep-2014

Time (UTC)

07:27


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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×