A container object conflict occurs when you create a GPO for a wireless network policy by using the Group Policy Management MMC snap-in from a domain controller that is running Windows Server 2008 to connect to a PDC that is running Windows Server 2003

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

On This Page

SYMPTOMS

Consider the following scenario:
  • In a domain, you have a domain controller that is running Windows Server 2008 and a domain controller that is running Windows Server 2003. The domain controller that is running Windows Server 2003 hosts the primary domain controller (PDC) emulator role.
  • You use the Group Policy Management Microsoft Management Console (MMC) snap-in (gpmc.msc) to connect to the domain controller that is running Windows Server 2003 and that has PDC emulator role installed.
  • You create a new Group Policy object (GPO) to configure a wireless network policy.
In this scenario, some conflict container objects are generated in the following location:
Domain\Your.Domain.Name\System\Policies\{Guid of your Policy}\Machine
Additionally, if you export and then try to import the GPO into a domain, the import action fails because of this container object conflict.

CAUSE

This problem occurs because a container object is unnecessarily created on the domain controller that is running Windows Server 2008. This behavior causes a container object conflict. Therefore, the GPO cannot be imported.

RESOLUTION

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:
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, the computer must be running one of the following operating systems:
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
Additionally, the computer must have Active Directory Domain Services (AD DS) installed.

For more information about how to install the 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

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfix.

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 Vista and Windows Server 2008 file information note

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wlangpui.dll6.0.6001.22475397,31218-Jul-200911:56x86
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wlangpui.dll6.0.6002.22180397,31218-Jul-200911:47x86
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wlangpui.dll6.0.6001.22475486,91218-Jul-200912:25x64
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wlangpui.dll6.0.6002.22180486,91218-Jul-200911:47x64


STATUS

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

REFERENCES

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

MORE INFORMATION

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Package_for_kb973625_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42519-Jul-200910:18Not Applicable
Package_for_kb973625_server_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,53019-Jul-200910:18Not Applicable
Package_for_kb973625_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71319-Jul-200910:18Not Applicable
X86_microsoft-windows-wlangpui_31bf3856ad364e35_6.0.6001.22475_none_40bfc4b623e4317a.manifestNot Applicable25,29918-Jul-200922:26Not Applicable
X86_microsoft-windows-wlangpui_31bf3856ad364e35_6.0.6002.22180_none_42966540211723dc.manifestNot Applicable25,29918-Jul-200922:02Not Applicable

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

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-wlangpui_31bf3856ad364e35_6.0.6001.22475_none_9cde6039dc41a2b0.manifestNot Applicable25,34518-Jul-200922:36Not Applicable
Amd64_microsoft-windows-wlangpui_31bf3856ad364e35_6.0.6002.22180_none_9eb500c3d9749512.manifestNot Applicable25,34518-Jul-200922:00Not Applicable
Package_for_kb973625_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43319-Jul-200910:18Not Applicable
Package_for_kb973625_server_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,54019-Jul-200910:18Not Applicable
Package_for_kb973625_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,72319-Jul-200910:18Not Applicable
Wow64_microsoft-windows-wlangpui_31bf3856ad364e35_6.0.6001.22475_none_a7330a8c10a264ab.manifestNot Applicable21,78618-Jul-200922:09Not Applicable
Wow64_microsoft-windows-wlangpui_31bf3856ad364e35_6.0.6002.22180_none_a909ab160dd5570d.manifestNot Applicable21,78618-Jul-200921:48Not Applicable

Properties

Article ID: 973625 - Last Review: October 16, 2009 - Revision: 2.1
APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 Standard without Hyper-V
Keywords: 
conflict wireless kbfix kbbug kbsurveynew kbhotfixserver kbautohotfix kbexpertiseinter kbqfe KB973625

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