Symptoms

Consider the following scenario:

  • You have a disjoint namespace in a Windows-based domain environment. For example, the Domain Name System (DNS) name is test1.com and the primary DNS suffix of the computers in the domain is test2.com.

  • You try to use the Add an Entry Point Wizard to add a new entry point on a Windows Server 2012-based Direct Access server in the domain.

In this scenario, the wizard fails at the "Server GPO Settings" stage. More specifically, you cannot create a Group Policy Object (GPO) or browse to select an existing GPO to use.

Cause

This issue occurs because the Add an Entry Point Wizard assumes that the DNS name is the same as the primary DNS suffix of the computers when it fetches a domain name. Although in most cases the primary DNS suffix of the computer in the domain is the same as DNS name, there are some situations in which you may have a disjoint namespace in the domain. In this situation, the same domain name assumption is invalid.

Resolution

This hotfix is also available at Microsoft Update Catalog

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.

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, submit a request to 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=supportNote 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 2012.

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.

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 2012 file information notesImportant Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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 8" 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:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.20 xxx

    Windows Server 2012

    RTM

    LDR

  • 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 2012" 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 2012

File name

File version

File size

Date

Time

Platform

Damgmt.dll

6.2.9200.20708

9,712,640

04-May-2013

08:19

x64

Ramgmtui.exe

6.2.9200.20708

8,689,664

04-May-2013

08:19

x64




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 for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File name

Amd64_13861b20b274ba89d85d2a681f29c666_31bf3856ad364e35_6.2.9200.20708_none_0e7cc1bfa1e4dc7c.manifest

File version

Not applicable

File size

686

Date (UTC)

04-May-2013

Time (UTC)

17:33

Platform

Not applicable

File name

Msil_damgmtmanaged_31bf3856ad364e35_6.2.9200.20708_none_777a2c7c0664fc2b.manifest

File version

Not applicable

File size

5,953

Date (UTC)

04-May-2013

Time (UTC)

08:31

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×