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.

WinRM does not transfer impersonation tokens correctly in Windows 7 or in Windows Server 2008 R2


View products that this article applies to.

Symptoms

Assume that you use Windows Remote Management (WinRM) on a computer that is running Windows 7 or Windows Server 2008 R2. For example, you use WinRM scripting objects, the WinRM command-line tool, or the Windows Remote Shell (WinRS) command line tool to obtain management data from remote computers. However, WinRM does not transfer the impersonation token correctly.

For example, you develop a service that backs up and recovers an Exchange server. To perform these operations, the service accesses Microsoft Exchange PowerShell commandlets by using administrative credentials for an Exchange organization. An end-user provides their logon credentials to an administrator of the Exchange organization so that the administrator can use the service to impersonate that end-user and obtain the necessary PowerShell access. However, during the impersonation process, the PowerShell commandlets fail with an "Access Denied" error.

↑ 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 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, 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 apply 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
  • 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:
    VersionProductMilestoneService branch
    6.1.760
    0.21xxx
    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
Wsmanhttpconfig.exe6.1.7600.21120198,65605-Jan-201205:36x86
Wsmanmigrationplugin.dll6.1.7600.21120248,83205-Jan-201205:43x86
Wsmauto.dll6.1.7600.21120145,92005-Jan-201205:43x86
Wsmsvc.dll6.1.7600.211201,176,06405-Jan-201205:43x86
Wsmwmipl.dll6.1.7600.21120213,50405-Jan-201205:43x86
Wsmanhttpconfig.exe6.1.7601.21891198,65605-Jan-201205:22x86
Wsmanmigrationplugin.dll6.1.7601.21891248,83205-Jan-201205:25x86
Wsmauto.dll6.1.7601.21891145,92005-Jan-201205:25x86
Wsmsvc.dll6.1.7601.218911,176,57605-Jan-201205:25x86
Wsmwmipl.dll6.1.7601.21891214,01605-Jan-201205:25x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Wsmanhttpconfig.exe6.1.7600.21120266,24005-Jan-201206:27x64
Wsmanmigrationplugin.dll6.1.7600.21120346,11205-Jan-201206:34x64
Wsmauto.dll6.1.7600.21120181,24805-Jan-201206:34x64
Wsmsvc.dll6.1.7600.211202,019,32805-Jan-201206:34x64
Wsmwmipl.dll6.1.7600.21120309,76005-Jan-201206:34x64
Wsmanhttpconfig.exe6.1.7601.21891266,24005-Jan-201206:24x64
Wsmanmigrationplugin.dll6.1.7601.21891346,62405-Jan-201206:27x64
Wsmauto.dll6.1.7601.21891181,24805-Jan-201206:27x64
Wsmsvc.dll6.1.7601.218912,020,35205-Jan-201206:27x64
Wsmwmipl.dll6.1.7601.21891310,27205-Jan-201206:27x64
Wsmanhttpconfig.exe6.1.7600.21120198,65605-Jan-201205:36x86
Wsmanmigrationplugin.dll6.1.7600.21120248,83205-Jan-201205:43x86
Wsmauto.dll6.1.7600.21120145,92005-Jan-201205:43x86
Wsmsvc.dll6.1.7600.211201,176,06405-Jan-201205:43x86
Wsmwmipl.dll6.1.7600.21120213,50405-Jan-201205:43x86
Wsmanhttpconfig.exe6.1.7601.21891198,65605-Jan-201205:22x86
Wsmanmigrationplugin.dll6.1.7601.21891248,83205-Jan-201205:25x86
Wsmauto.dll6.1.7601.21891145,92005-Jan-201205:25x86
Wsmsvc.dll6.1.7601.218911,176,57605-Jan-201205:25x86
Wsmwmipl.dll6.1.7601.21891214,01605-Jan-201205:25x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Wsmanhttpconfig.exe6.1.7600.21120517,12005-Jan-201205:25IA-64
Wsmanmigrationplugin.dll6.1.7600.21120671,74405-Jan-201205:33IA-64
Wsmauto.dll6.1.7600.21120392,19205-Jan-201205:33IA-64
Wsmsvc.dll6.1.7600.211203,575,80805-Jan-201205:33IA-64
Wsmwmipl.dll6.1.7600.21120611,32805-Jan-201205:33IA-64
Wsmanhttpconfig.exe6.1.7601.21891517,12005-Jan-201205:17IA-64
Wsmanmigrationplugin.dll6.1.7601.21891671,74405-Jan-201205:24IA-64
Wsmauto.dll6.1.7601.21891392,19205-Jan-201205:24IA-64
Wsmsvc.dll6.1.7601.218913,576,83205-Jan-201205:24IA-64
Wsmwmipl.dll6.1.7601.21891611,32805-Jan-201205:24IA-64
Wsmanhttpconfig.exe6.1.7600.21120198,65605-Jan-201205:36x86
Wsmanmigrationplugin.dll6.1.7600.21120248,83205-Jan-201205:43x86
Wsmauto.dll6.1.7600.21120145,92005-Jan-201205:43x86
Wsmsvc.dll6.1.7600.211201,176,06405-Jan-201205:43x86
Wsmwmipl.dll6.1.7600.21120213,50405-Jan-201205:43x86
Wsmanhttpconfig.exe6.1.7601.21891198,65605-Jan-201205:22x86
Wsmanmigrationplugin.dll6.1.7601.21891248,83205-Jan-201205:25x86
Wsmauto.dll6.1.7601.21891145,92005-Jan-201205:25x86
Wsmsvc.dll6.1.7601.218911,176,57605-Jan-201205:25x86
Wsmwmipl.dll6.1.7601.21891214,01605-Jan-201205:25x86

↑ 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_62b453f78b3629ff24056d96e40a6c1e_31bf3856ad364e35_6.1.7601.21891_none_00374a7535638499.manifest
File versionNot Applicable
File size720
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable
File nameX86_ca444350363ee5f8a81d299309ae9c3b_31bf3856ad364e35_6.1.7600.21120_none_b37cad4d983bf34d.manifest
File versionNot Applicable
File size720
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable
File nameX86_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7600.21120_none_cb0129ea274cfd63.manifest
File versionNot Applicable
File size191,904
Date (UTC)05-Jan-2012
Time (UTC)13:17
PlatformNot Applicable
File nameX86_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.21891_none_cc9cffa424ab12fb.manifest
File versionNot Applicable
File size191,904
Date (UTC)05-Jan-2012
Time (UTC)13:17
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_137103a2171f010e1cfc90dbd094a829_31bf3856ad364e35_6.1.7601.21891_none_13780473a3ce292f.manifest
File versionNot Applicable
File size1,090
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable
File nameAmd64_edb80e325a42f94ada532e26f4760161_31bf3856ad364e35_6.1.7600.21120_none_e547b6eb2fdcf037.manifest
File versionNot Applicable
File size1,090
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable
File nameAmd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7600.21120_none_271fc56ddfaa6e99.manifest
File versionNot Applicable
File size191,908
Date (UTC)05-Jan-2012
Time (UTC)13:39
PlatformNot Applicable
File nameAmd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.21891_none_28bb9b27dd088431.manifest
File versionNot Applicable
File size191,908
Date (UTC)05-Jan-2012
Time (UTC)13:39
PlatformNot Applicable
File nameWow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7600.21120_none_31746fc0140b3094.manifest
File versionNot Applicable
File size75,910
Date (UTC)05-Jan-2012
Time (UTC)13:39
PlatformNot Applicable
File nameWow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.21891_none_3310457a1169462c.manifest
File versionNot Applicable
File size75,910
Date (UTC)05-Jan-2012
Time (UTC)13:39
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_7151cbe1a39f0d8bf53f79f6414ff6c2_31bf3856ad364e35_6.1.7601.21891_none_a5d56f3d33768469.manifest
File versionNot Applicable
File size1,088
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable
File nameIa64_7de6efa8099e950368724226ef8fa941_31bf3856ad364e35_6.1.7600.21120_none_e4054862a760e3fc.manifest
File versionNot Applicable
File size1,088
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable
File nameIa64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7600.21120_none_cb02cde0274b065f.manifest
File versionNot Applicable
File size191,906
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable
File nameIa64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.21891_none_cc9ea39a24a91bf7.manifest
File versionNot Applicable
File size191,906
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable
File nameWow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7600.21120_none_31746fc0140b3094.manifest
File versionNot Applicable
File size75,910
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable
File nameWow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.21891_none_3310457a1169462c.manifest
File versionNot Applicable
File size75,910
Date (UTC)05-Jan-2012
Time (UTC)12:58
PlatformNot Applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2659071
Revision : 1
Created on : 1/7/2017
Published on : 2/16/2012
Exists online : False
Views : 184