Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The operating system cannot establish a secure channel after a failed deployment of Windows 7 or Windows Server 2008 R2 on client computers


View products that this article applies to.

Symptoms

When you try to deploy Windows 7 or Windows Server 2008 R2 to many client computers at the same time, the deployment fails on a small percentage of them. On client computers where the deployment fails, the operating system cannot establish a secure channel after the deployment or the offline domain join operation. Additionally, the following event is logged:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 3224
Description: Changing machine account password for account %1 failed with the following error: %n%2
Note When this issue occurs, you must remove the computer from the domain and then rejoin it to the domain.

↑ Back to the top


Cause

This issue occurs because the client computer may receive the STATUS_DS_BUSY status when a user of the client computer tries to set the user account password. The expected behavior is that the client computer can recover from the STATUS_DS_BUSY status. However, in the situation described in the "Symptoms" section, the client computer cannot recover.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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, 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 be running one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global 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 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.1.760
    0. 21 xxx
    Windows 7 and Windows Server 2008 R2RTMLDR
    6.1.760
    1.
    21xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • 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 Server 2008 R2 and for Windows 7" 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 x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Netlogon.dll6.1.7600.21010564,73616-Jul-201104:26x86
Nlsvc.mofNot applicable2,87310-Jun-200921:29Not applicable
Netlogon.dll6.1.7601.21772564,22416-Jul-201104:56x86
Nlsvc.mofNot applicable2,87310-Jun-200921:29Not applicable
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Netlogon.dll6.1.7600.21010693,76016-Jul-201105:22x64
Nlsvc.mofNot applicable2,87310-Jun-200920:47Not applicable
Netlogon.dll6.1.7601.21772695,29616-Jul-201105:29x64
Nlsvc.mofNot applicable2,87310-Jun-200920:47Not applicable
Netlogon.dll6.1.7600.21010564,73616-Jul-201104:26x86
Nlsvc.mofNot applicable2,87310-Jun-200921:29Not applicable
Netlogon.dll6.1.7601.21772564,22416-Jul-201104:56x86
Nlsvc.mofNot applicable2,87310-Jun-200921:29Not applicable
For all supported IA-64–based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Netlogon.dll6.1.7600.210101,150,46416-Jul-201104:04IA-64
Nlsvc.mofNot applicable2,87310-Jun-200920:52Not applicable
Netlogon.dll6.1.7601.217721,150,46416-Jul-201104:15IA-64
Nlsvc.mofNot applicable2,87310-Jun-200920:52Not applicable
Netlogon.dll6.1.7600.21010564,73616-Jul-201104:26x86
Nlsvc.mofNot applicable2,87310-Jun-200921:29Not applicable
Netlogon.dll6.1.7601.21772564,22416-Jul-201104:56x86
Nlsvc.mofNot applicable2,87310-Jun-200921:29Not applicable

↑ Back to the top


Status

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

↑ Back to the top


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

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_1c5d3eb1f4f3ce12329290e41479051c_31bf3856ad364e35_6.1.7600.21010_none_7311923c1de243c9.manifest
File versionNot applicable
File size705
Date (UTC)16-Jul-2011
Time (UTC)10:17
File nameX86_d7fad3be837f1b4016a1ad0ee9e73009_31bf3856ad364e35_6.1.7601.21772_none_c092ef017a3dbc79.manifest
File versionNot applicable
File size705
Date (UTC)16-Jul-2011
Time (UTC)10:17
File nameX86_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21010_none_fe5e39d3b237004d.manifest
File versionNot applicable
File size35,541
Date (UTC)16-Jul-2011
Time (UTC)04:52
File nameX86_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21772_none_0005dfc3af8c134b.manifest
File versionNot applicable
File size35,541
Date (UTC)16-Jul-2011
Time (UTC)05:23
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_2864bcb44ff89892a2f152a3bf66db0f_31bf3856ad364e35_6.1.7600.21010_none_cef52028cc262535.manifest
File versionNot applicable
File size709
Date (UTC)16-Jul-2011
Time (UTC)10:17
File nameAmd64_43125dfaa4b953e6488ccec439d1eca2_31bf3856ad364e35_6.1.7601.21772_none_f9a51fdc9e8ceb54.manifest
File versionNot applicable
File size709
Date (UTC)16-Jul-2011
Time (UTC)10:17
File nameAmd64_9d85130a4cac5711570bc9f32a16d9b5_31bf3856ad364e35_6.1.7601.21772_none_2502c690c7dedb44.manifest
File versionNot applicable
File size1,060
Date (UTC)16-Jul-2011
Time (UTC)10:17
File nameAmd64_a2a625b07430615cd2c36109a04a3de9_31bf3856ad364e35_6.1.7600.21010_none_331cca83233f79d8.manifest
File versionNot applicable
File size1,060
Date (UTC)16-Jul-2011
Time (UTC)10:17
File nameAmd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21010_none_5a7cd5576a947183.manifest
File versionNot applicable
File size35,547
Date (UTC)16-Jul-2011
Time (UTC)05:53
File nameAmd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21772_none_5c247b4767e98481.manifest
File versionNot applicable
File size35,547
Date (UTC)16-Jul-2011
Time (UTC)06:10
File nameWow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21010_none_64d17fa99ef5337e.manifest
File versionNot applicable
File size16,596
Date (UTC)16-Jul-2011
Time (UTC)04:45
File nameWow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21772_none_667925999c4a467c.manifest
File versionNot applicable
File size16,596
Date (UTC)16-Jul-2011
Time (UTC)05:15
Additional files for all supported IA-64–based versions of Windows Server 2008 R2
File nameIa64_019a7490d437f11dd7ec1e940bd67983_31bf3856ad364e35_6.1.7600.21010_none_2a1613a56f9090e1.manifest
File versionNot applicable
File size1,058
Date (UTC)16-Jul-2011
Time (UTC)10:17
File nameIa64_5d73fcef3bf176183ec8560e3da77900_31bf3856ad364e35_6.1.7601.21772_none_01b77e83b9a09cf4.manifest
File versionNot applicable
File size1,058
Date (UTC)16-Jul-2011
Time (UTC)10:17
File nameIa64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21010_none_fe5fddc9b2350949.manifest
File versionNot applicable
File size35,544
Date (UTC)16-Jul-2011
Time (UTC)05:42
File nameIa64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21772_none_000783b9af8a1c47.manifest
File versionNot applicable
File size35,544
Date (UTC)16-Jul-2011
Time (UTC)06:10
File nameWow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7600.21010_none_64d17fa99ef5337e.manifest
File versionNot applicable
File size16,596
Date (UTC)16-Jul-2011
Time (UTC)04:45
File nameWow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.1.7601.21772_none_667925999c4a467c.manifest
File versionNot applicable
File size16,596
Date (UTC)16-Jul-2011
Time (UTC)05:15

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2580119
Revision : 1
Created on : 1/7/2017
Published on : 12/27/2012
Exists online : False
Views : 196