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.

You cannot start any RemoteApp applications through a Windows Server 2008-based or later Terminal Server or RD Gateway


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install the Terminal Services Gateway role service on a computer that is running Windows Server 2008 or Windows Server 2008 R2. Or, you install the Remote Desktop Gateway (RD Gateway) role service on a computer that is running Windows Server 2012 or Windows Server 2012 R2.
  • You configure some RemoteApp applications to be accessed through the Gateway.
  • You configure the Gateway so that it can resolve the Service records (SRV records) of domain controllers in a remote domain.
  • You configure the Gateway so that it cannot connect to these domain controllers by using firewall policies.
In this scenario, all users from the remote domain cannot start any RemoteApp applications through the Gateway.

Notes
  • Users may be unable to establish  sessions through the Gateway because of this issue.
  • Users may experience a delay of several seconds (such as 40 to 50 seconds) before they successfully establish sessions through the Gateway because of this issue.

↑ Back to the top


Cause

This issue occurs because of an authentication time-out issue that occurs when the Gateway expects a response from the Network Policy Server (NPS) during authentication. The time-out issue occurs because the NPS cannot validate the MS_ATTRIBUTE_MACHINE_NAME attribute in the authentication request.

↑ Back to the top


Resolution

For Windows Server 2012 and above installing the hotfix is not required only the addition of the registry key is needed. For Windows Server 2008 and Windows Server 2008 R2 the hotfix and the registry key are required.

After you install the hotfix, the following registry entry is created under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Gateway registry subkey:
Name: SkipMachineNameAttribute
Type: REG_DWORD
Value: 1
When the registry entry exists with a value of 1, the Gateway does not include the MS_ATTRIBUTE_MACHINE_NAME attribute in the authentication request.

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 Web site: 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 Server 2008 Service Pack 2 (SP2)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
Additionally, you must have the Gateway role service installed.

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

For more information about how to obtain a Windows 7 or a 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 Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" 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 Vista" 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.0.600
    2.
    22xxx
    Windows Server 2008SP2LDR
  • 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 " section. MUM files 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 Server 2008
File nameFile versionFile sizeDateTimePlatform
Aaedge.dll6.0.6002.22719193,53620-Sep-201115:29x86
Aaedge.mofNot Applicable1,10409-Sep-201111:25Not Applicable
Aatspp.dll6.0.6002.2271973,72820-Sep-201115:29x86
Aatspp.mofNot Applicable1,10709-Sep-201111:25Not Applicable
Rap.xmlNot Applicable89509-Sep-201111:25Not Applicable
Tsgateway.xmlNot Applicable59109-Sep-201111:25Not Applicable
Tsgclean.exe6.0.6002.22719225,79220-Sep-201113:48x86
Tsproxy-edgeadapter-ppdlic.xrm-msNot Applicable3,01820-Sep-201117:30Not Applicable
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Aaedge.dll6.0.6002.22719221,69620-Sep-201115:40x64
Aaedge.mofNot Applicable1,10415-Mar-201104:34Not Applicable
Aatspp.dll6.0.6002.2271976,28820-Sep-201115:40x64
Aatspp.mofNot Applicable1,10715-Mar-201104:34Not Applicable
Rap.xmlNot Applicable89515-Mar-201104:34Not Applicable
Tsgateway.xmlNot Applicable59115-Mar-201104:34Not Applicable
Tsgclean.exe6.0.6002.22719377,85620-Sep-201114:08x64
Tsproxy-edgeadapter-ppdlic.xrm-msNot Applicable3,01820-Sep-201119:49Not Applicable
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.
    21xxx
    Windows Server 2008 R2RTMLDR
    6.1.760
    1.
    21xxx
    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" 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 2008 R2
File nameFile versionFile sizeDateTimePlatform
Aaedge.dll6.1.7600.21095305,66422-Nov-201106:42x64
Tsproxy-edgeadapter-ppdlic.xrm-msNot Applicable3,01822-Nov-201107:04Not Applicable
Aaedge.dll6.1.7601.21864308,22422-Nov-201106:23x64
Aaedge.mofNot Applicable1,26805-Nov-201001:52Not Applicable
Aatspp.mofNot Applicable1,27105-Nov-201001:52Not Applicable
Rap.xmlNot Applicable89505-Nov-201001:52Not Applicable
Tsgateway.xmlNot Applicable42905-Nov-201001:52Not Applicable
Tsproxy-edgeadapter-ppdlic.xrm-msNot Applicable3,01822-Nov-201106:42Not 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 Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_0c92d70283bfb272176e7b5189b2ba09_31bf3856ad364e35_6.0.6002.22719_none_89c8e6183ceedbee.manifest
File versionNot Applicable
File size707
Date (UTC)20-Sep-2011
Time (UTC)23:18
File nameX86_2a71532760838a15235f4e2f176012bd_31bf3856ad364e35_6.0.6002.22719_none_1dca19a6b2be4880.manifest
File versionNot Applicable
File size707
Date (UTC)20-Sep-2011
Time (UTC)23:18
File nameX86_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.0.6002.22719_none_4078c5e0e2f92adf.manifest
File versionNot Applicable
File size86,940
Date (UTC)20-Sep-2011
Time (UTC)17:36
File nameX86_tsproxy-edgeadaptor-machinenameconfig_31bf3856ad364e35_6.0.6002.22719_none_21d7b97d6203ccf1.manifest
File versionNot Applicable
File size1,341
Date (UTC)20-Sep-2011
Time (UTC)17:36
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_aeedc4e62b166746840ee3aff094b114_31bf3856ad364e35_6.0.6002.22719_none_ec6d55b8fa24b092.manifest
File versionNot Applicable
File size711
Date (UTC)20-Sep-2011
Time (UTC)23:18
File nameAmd64_f229672d8ea38c6dc46403ee831717f0_31bf3856ad364e35_6.0.6002.22719_none_96f19b9f87517fa3.manifest
File versionNot Applicable
File size711
Date (UTC)20-Sep-2011
Time (UTC)23:18
File nameAmd64_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.0.6002.22719_none_9c9761649b569c15.manifest
File versionNot Applicable
File size87,298
Date (UTC)20-Sep-2011
Time (UTC)19:56
File nameAmd64_tsproxy-edgeadaptor-machinenameconfig_31bf3856ad364e35_6.0.6002.22719_none_7df655011a613e27.manifest
File versionNot Applicable
File size1,343
Date (UTC)20-Sep-2011
Time (UTC)19:55

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_24cfaca29893ce423e896bc6f5949144_31bf3856ad364e35_6.1.7601.21864_none_11285b4aeb9cd328.manifest
File versionNot Applicable
File size711
Date (UTC)22-Nov-2011
Time (UTC)16:47
PlatformNot Applicable
File nameAmd64_2f71d9c4bb0b574514fb639541a6ad64_31bf3856ad364e35_6.1.7600.21095_none_510896a6d976a28c.manifest
File versionNot Applicable
File size711
Date (UTC)22-Nov-2011
Time (UTC)16:47
PlatformNot Applicable
File nameAmd64_6dfffecf8d7c85fe0a3ce9116ca67e24_31bf3856ad364e35_6.1.7600.21095_none_8884630a5914e0f3.manifest
File versionNot Applicable
File size711
Date (UTC)22-Nov-2011
Time (UTC)16:47
PlatformNot Applicable
File nameAmd64_d362737cf1d64f4d793f456b939f9c83_31bf3856ad364e35_6.1.7601.21864_none_92573a32fdc50e49.manifest
File versionNot Applicable
File size711
Date (UTC)22-Nov-2011
Time (UTC)16:47
PlatformNot Applicable
File nameAmd64_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.1.7600.21095_none_9a7e138fff8c36f9.manifest
File versionNot Applicable
File size99,560
Date (UTC)22-Nov-2011
Time (UTC)16:47
PlatformNot Applicable
File nameAmd64_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.1.7601.21864_none_9c8409d3fc9affa0.manifest
File versionNot Applicable
File size99,560
Date (UTC)22-Nov-2011
Time (UTC)16:47
PlatformNot Applicable
File nameAmd64_tsproxy-edgeadaptor-machinenameconfig_31bf3856ad364e35_6.1.7600.21095_none_7bdd072c7e96d90b.manifest
File versionNot Applicable
File size1,311
Date (UTC)22-Nov-2011
Time (UTC)07:18
PlatformNot Applicable
File nameAmd64_tsproxy-edgeadaptor-machinenameconfig_31bf3856ad364e35_6.1.7601.21864_none_7de2fd707ba5a1b2.manifest
File versionNot Applicable
File size1,311
Date (UTC)22-Nov-2011
Time (UTC)06:50
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,414
Date (UTC)22-Nov-2011
Time (UTC)16:47
PlatformNot Applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2620264
Revision : 1
Created on : 3/21/2017
Published on : 7/29/2015
Exists online : False
Views : 317