Jump to content

Registry disabled


Recommended Posts

I have a user policy that has registry disabled. I then create a HKLM registry setting that changes some settings and deploy this over the network using a machine policy. Some PCs have the setting applied successfully and some dont. The PCs that dont had errors relating "could not contact the domain controller" (event 1053 i think).

I checked our DNS and it 'seems' to be fine. However i rejoined the PC to the domain which seemed to have resolved any errors as such. Now the same problem exists (reg disabled by admin) when the user boots up the PC. Under the local PC there are some firmware issues listed, but before i start taking the PC apart and resolving this error, could any advise if this could be related to the original error? As i say some PCs have the setting applied via GP and some dont?

In addition i checked GP results and i noticed under Reason denied it has the status Inaccessible... i couldnt find the gptext.log file as it doesnt exist under.

Any hints to resolving this issue?

Thanks

Link to comment
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...