The "RemoteApp and Desktop Connection Management" service cannot start on a computer that is in a disjointed namespace and that is running Windows Server 2008 R2

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

On This Page

SYMPTOMS

Consider the following scenario:
  • You install the Remote Desktop Connection Broker role service on a computer that is running Windows Server 2008 R2.
  • The primary Domain Name System (DNS) suffix of the computer does not match the DNS name of the Active Directory Domain Services (AD DS) domain. This is known as a disjoint namespace.
In this scenario, the RemoteApp and Desktop Connection Management service cannot start. Additionally, an event that resembles the following is logged in the Applications and Services Logs:

Source: Microsoft-Windows-RemoteApp and Desktop Connection Management
Date: <date & time>
Event ID: 1009
Task Category: Setup
Level: Error
Keywords: Server Core
User: NETWORK SERVICE
Computer: <computer name>
Description:
Error starting the Remote App and Desktop Management Service.

Error Code: 0x80070534

CAUSE

The issue occurs because the RemoteApp and Desktop Connection Management service assumes that the first part of the fully qualified domain name (FQDN) is equal to the NetBIOS domain name. However, this assumption is not true in a disjointed namespace.

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:
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 Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1). Additionally, you must have the Remote Desktop Connection Broker role service installed. For more information about how to obtain 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, you do not have to change the registry.

Restart requirement

If you stop the RemoteApp and Desktop Connection Management service before you install this hotfix, you do not have to restart the computer.

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 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, 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.16xxxWindows Server 2008 R2RTMGDR
    6.1.760 0.20xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.17xxxWindows Server 2008 R2SP1GDR
    6.1.760 1.21xxxWindows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Tscpubsvr.dll6.1.7600.20929180,22421-Mar-201105:33x64
Tscpubsvr.dll6.1.7601.21687180,22419-Mar-201107:43x64

STATUS

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

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 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_337120c0918b0ea90ea13fe49e2a806b_31bf3856ad364e35_6.1.7601.21687_none_82cedb7c67a1148c.manifest
File versionNot applicable
File size726
Date (UTC)22-Mar-2011
Time (UTC)01:55
PlatformNot applicable
File nameAmd64_3652d858d68f91a097c3890cb9cf8325_31bf3856ad364e35_6.1.7600.20929_none_8ac42645ea5a6dad.manifest
File versionNot applicable
File size726
Date (UTC)22-Mar-2011
Time (UTC)01:55
PlatformNot applicable
File nameAmd64_microsoft-windows-t..s-centralpublishing_31bf3856ad364e35_6.1.7600.20929_none_4a483be0732a4baf.manifest
File versionNot applicable
File size24,362
Date (UTC)21-Mar-2011
Time (UTC)06:11
PlatformNot applicable
File nameAmd64_microsoft-windows-t..s-centralpublishing_31bf3856ad364e35_6.1.7601.21687_none_4bebb6e470832f6c.manifest
File versionNot applicable
File size24,362
Date (UTC)19-Mar-2011
Time (UTC)08:17
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,989
Date (UTC)22-Mar-2011
Time (UTC)01:55
PlatformNot applicable

Properties

Article ID: 2525608 - Last Review: April 1, 2011 - Revision: 1.0
APPLIES TO
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Foundation
Keywords: 
kbhotfixserver kbautohotfix kbsurveynew kbfix kbexpertiseadvanced kbqfe KB2525608

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com