Microsoft KB Archive/931753

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:36, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Group Policy settings are not applied when a client computer that is running Windows Server 2003 tries to apply Group Policy settings together with WMI filters from an RODC

Article ID: 931753

Article Last Modified on 2/15/2007



APPLIES TO

  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)



SYMPTOMS

When a client computer that is running Microsoft Windows Server 2003 tries to apply Group Policy settings together with Windows Management Instrumentation (WMI) filters from a read-only domain controller (RODC), Group Policy settings are not applied.

This problem occurs when Windows Server 2003-based client computers coexist with Windows Vista-based client computers in a domain environment.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Microsoft regularly releases software updates to address specific problems. If Microsoft releases a software update to resolve this problem, this article will be updated with more information.

MORE INFORMATION

You can use Group Policy to manage client computers in a domain environment. Many policy changes that affect IPsec require that you apply WMI filters when you deploy the changes. In segmented networks, domain clients that have limited access to a domain controller that has full permissions do not apply Group Policy files. Managing these clients increases total cost of ownership (TCO) and management costs. To reduce the cost and risk involved in managing these clients, you can implement Group Policy settings with WMI filters through an RODC. This method reduces the number of Group Policy object files.

Keywords: kbexpertiseadvanced kbtshoot KB931753