Windows cannot access the registry policy file



We have a 2003 Active Directory Domain and backup domain controller in
the tree. There roughly 200 workstations in the domain tree (150 WinXP
and 50 w2k) 80% of the Windows XPs are processing the computer
configuration settings from the domain Group Policy. However, the other
10% of the Windows XPs refused to process the Computer Configuration
(Example. Firewall settings and Windows Updates).
I ran RSOP.MSC (Resultant tool) on each of the clients I have verified
that all the layers of group policies have been applied correctly
expect for the parts that are processed by the client-side Security
extension.
But if we open the local policy (gpedit.msc) on the workstation and
manually enable the firewall settings, it processes all the information
from the domain group policy. However, when I reboot the machine it
returns back to original stage.

I was able to retrieve the Group Policy applied locally on several of
my workstations. I figured out the problem, but not the solution. The
problem is the policy is failing to apply to the registry. Below is the
report generated from the local machine, it's identical on all three
machines I download it from. Under the component Status

Component name Status
Last Process Time
Group Policy Infrastructure Success 3/7/2006 8:28:32
EFS Recovery Success 3/7/2006 8:28:32
Registry Failed 3/7/2006 8:28:32
Registry failed due to the error listed below
Unspecified error

Additional information may have been logged. Review the policy Events
tab in the console or the application events log for events between
3/7/2006 8:28:32AM and 3/7/2006 8:28:32.

Security Success 3/7/2006 8:28:32

According to Microsoft and a few online threads, the NTuser.POL is
corrupted on the local machine.
Please share if you have experience anything like this.
Thanks,

.



Relevant Pages

  • Windows cannot access the registry policy file
    ... There roughly 200 workstations in the domain tree (150 WinXP ... configuration settings from the domain Group Policy. ... report generated from the local machine, ...
    (microsoft.public.windowsxp.general)
  • Re: Windows cannot access the registry policy file
    ... There roughly 200 workstations in the domain tree (150 WinXP ... configuration settings from the domain Group Policy. ... report generated from the local machine, ...
    (microsoft.public.windows.server.sbs)
  • Re: PPTP misery
    ... Domain PCs away from domain will not VPN. ... I am going to do what you ask re Firewall & Policy because I value your ... The only real difference between the domain workstations and the ... YourDomain.local> Group Policy Objects. ...
    (microsoft.public.windows.server.sbs)
  • Re: Active directory Group Policy (Win2k)
    ... Thanks for the pointer, that is obviously the way to go forward. ... We have a requirement to allow users, when logged on to certain workstations, to access Microsoft Office. ... We can give users access to the menu items by removing the group policy but this then gives all users greater access than required on other workstations. ... Posted via a free Usenet account from http://www.teranews.com ...
    (microsoft.public.security)
  • RE: Require Network login?
    ... In GPMC.MSC, use Group Policy Result wizard, generate a report with the ... Open Server Management, navigate to Advanced Management, Group Policy ... >>5 Windows XP Professional Workstations ... >>2 printers use print server and 1 printer connect to one workstation ...
    (microsoft.public.windows.server.sbs)

Loading