Windows 7 clients cannot locate the Active Directory Management Gateway service that is installed on Windows Server 2003-based domain controllers

Windows 7 clients cannot locate the Active Directory Management Gateway Service (running as Active Directory Web Services) that is installed on Windows Server 2003-based domain controllers.

This issue occurs because the Netlogon service on the Windows Server 2003-based domain controllers does not recognize the DS_WEB_SERVICE_REQUIRED flag.

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 this specific problem. 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, the computer must have Windows Server 2003 Service Pack 2 installed.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 SP2, x86-based versions

Windows Server 2003 SP2, Itanium-based versions

Windows Server 2003 SP2 and Windows XP SP2, x64-based versions

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

After you install this hotfix, the Active Directory PowerShell module and Active Directory Administrative center can locate domain controllers that have Active Directory Management Gateway Service installed, similar to Active Directory Web Services (ADWS) on a Windows Server 2008 R2-based computer. Active Directory Management Gateway Service allows Active Directory Module for Windows PowerShell and Active Directory Administrative Center to manage Directory Service instances (Active Directory Domain Service, Active Directory Lightweight Directory Service) that are running locally on the Windows Server 2003-based domain controller on which Active Directory Management Gateway Service is installed.

If Active Directory Management Gateway Service on a Windows Server 2003-based server is stopped or disabled, client applications, such as the Active Directory module for Windows PowerShell and the Active Directory Administrative Center, cannot access or manage any directory service instances that are running on this server.

The DsGetDcName function can help you locate a domain controller in a specified domain. For more information about the function, visit the following Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information, click the following article number to view the article in the Microsoft Knowledge Base: