Smart card authentication does not work when you use VDI and RD Gateway for RDC client in Windows 7 or in Windows Server 2008 R2

Article ID: 2548538 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

On a computer that is running Windows 7 or Windows Server 2008 R2, you use Virtual Desktop Infrastructure (VDI) and Remote Desktop (RD) Gateway for Remote Desktop Connection (RDC) client. In this scenario, the RDC client cannot connect to MyDesktop or to VMpool by using smart card authentication. Additionally, you receive an error message that resembles the following message:
Your computer can't connect to the remote computer because a user name and password are required to authenticate to the Remote Desktop Gateway server instead of smart card credentials.
Note This issue occurs only when the you try to log on to the remote server for the first time by using the RDC client.
Back to the top | Give Feedback

CAUSE

This issue occurs because the RDC broker does not generate the RDP File option correctly. Therefore, smart card authentication cannot be selected.
Back to the top | Give Feedback

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 that is 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 exist, 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:
http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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 with Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 with Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 service pack or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932
(http://support.microsoft.com/kb/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
  • 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:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.20xxxWindows 7 and Windows Server 2008 R2RTMLDR
    6.1.760 1.21xxxWindows 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 very important to maintaining 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 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Sbmgr.dll6.1.7600.209711,667,07223-May-201105:31x86
Sbmgr.mscNot applicable116,20010-Jun-200920:32Not applicable
Sbmgr.dll6.1.7601.217321,712,12823-May-201105:13x86
Sbmgr.mscNot applicable116,20010-Jun-200920:32Not applicable
Back to the top | Give Feedback

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 | Give Feedback

MORE INFORMATION

For more information about how to deploying remote desktop licensing, visit the following Microsoft TechNet website:
A step-by-step guide for deploying remote desktop licensing
(http://technet.microsoft.com/library/dd983943(WS.10).aspx)
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/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 x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_1f51a88ae61aa61d111a4410a4919dcd_31bf3856ad364e35_6.1.7601.21732_none_5ef5596cf5b8c6e7.manifest
File versionNot applicable
File size729
Date (UTC)23-May-2011
Time (UTC)19:39
PlatformNot applicable
File nameAmd64_f89809b35666d485fb904cdb329679c0_31bf3856ad364e35_6.1.7600.20971_none_b00a891d384a0dec.manifest
File versionNot applicable
File size729
Date (UTC)23-May-2011
Time (UTC)19:39
PlatformNot applicable
File nameAmd64_microsoft-windows-t..bmgr-snapin-nonmsil_31bf3856ad364e35_6.1.7600.20971_none_af40754e63599ff8.manifest
File versionNot applicable
File size11,897
Date (UTC)23-May-2011
Time (UTC)05:56
PlatformNot applicable
File nameAmd64_microsoft-windows-t..bmgr-snapin-nonmsil_31bf3856ad364e35_6.1.7601.21732_none_b153124e605eb577.manifest
File versionNot applicable
File size11,897
Date (UTC)23-May-2011
Time (UTC)07:15
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,989
Date (UTC)23-May-2011
Time (UTC)19:39
PlatformNot applicable
Back to the top | Give Feedback

Properties

Article ID: 2548538 - Last Review: June 15, 2011 - Revision: 1.0
APPLIES TO
  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Ultimate
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Web Server 2008 R2
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2548538
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top