[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1302
  • Last Modified:

Group Policy Update Failing

I very recently migrated from a Server 2003 DC to a Server 2008 R2 DC. The migration didn't go smooth. I was forced to demote the 2008, and fix some issues on the 2003 (one of them was to rebuild the sysvol, remove orphaned GPO's and run DCGPOFIX).

I've since re-installed the 2008 R2, and successfully migrated. The 2003 server is now demoted.

Everything appeared to be working correctly, until I introduced a new GPO on a single OU containing one computer object (just for testing). The computer object is for a windows 7 system, and it is now failing "gpupdate" both with and without the force switch.

I've since removed the GPO and placed the computer object back in the built-in "computers" OU, but it is still failing on gpupdate.

Attempting to logoff the system takes a very long time (it's waiting for gpupdate to timeout).

Output from "gpupdate /force" after a very long (~10-15min) timeout:

 

Updating Policy...

User Policy update has completed successfully.

Computer Policy update has not completed in the expected time. Exiting...

To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results.

I have attached a copy of gpresult /h, but I don't see anything of significance.
gpreport.htm
0
M_Bursill
Asked:
M_Bursill
1 Solution
 
Mike ThomasConsultantCommented:
Shows no data available for the computer policy, what was that part of the policy for? if anything.
0
 
InderjeetjaggiCommented:
Check if all the ADM template are on place
Check if there are some issue with SYSVOL folder because it contains all GP's
Try to remove all GPs and add them again
0
 
M_BursillAuthor Commented:
You're right, it had to do with the nature of the policy, and my own stupidity.

I set a PowerShell script to run during startup, and stupidly I had a bug in the script which caused a credentials popup to be displayed.

Oddly enough this would cause the gpupdate to fail, as though the script was running, hitting the credentials dialog (presumably on session 0 since you couldn't actually see the dialog) and hanging.

I know the script it wasn't actually running because it would have updated a log file as per the first part of the script, but still, odd that a bug in the script (causing a credentials dialog) was the reason for it to hang on the gpupdate.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now