locked
failed to install update(s); 0x87d00692 error - group policy conflict RRS feed

  • Question

  • I'm having a problem with deploying a set of Windows updates.  I'm getting the (evidently) fairly common error "failed to install update(s); 0x87d00692 error - group policy conflict".  From what I can tell that error normally occurs when there is a (as the error implies) conflicting GPO that may have a WSUS server configured in it.  I checked and did not find any GPO's that any conflicting Windows Update.  I also checked the registry keys on the problem machines and they all had the correct URL for the SCCM server.  The registry keys are the same for machines that received the updates without problem.  All of these machines have the SCCM client correctly installed and several have received software package deployments without problems.  I checked the wuahandler.log and updatesdeployment.log and didn't seen anything other than the error above and the URL of my SCCM server.  Anyone have any ideas about where I should check next?  Thanks again in advance.


    Über Random

    Friday, January 18, 2013 11:41 PM

Answers

  • Just use the FQDN and see if it solves the problem. The settings will be refreshed when the GPO is refreshed.

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Uber Random Saturday, February 9, 2013 12:44 AM
    Tuesday, January 22, 2013 7:30 AM

All replies

  • Hi, you mean this kind of problem?

    http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/e2eaf736-5b59-410a-bd5d-1fd5b1e30988

    (specifically the example shown by @mjh110)


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)


    • Edited by DonPick Friday, January 18, 2013 11:59 PM
    Friday, January 18, 2013 11:57 PM
  • It's pretty close; I'm not sure if the logs are exactly the same but the symptoms are pretty close.  It's weird though because the updates did go out successfully to some computers without any problems, but not too many.  Currently our SCCM client is mostly deployed using a GPO that points the clients to http://sccm2:8530.  We have installed some using the right-click client install method.  Should I put the FQDN (http://sccm2.ad.uvu.edu:8530) of our SCCM server into the GPO instead and if I do will the clients automatically update to the new settings when the GPO refreshes?

    Über Random

    Tuesday, January 22, 2013 5:44 AM
  • Just use the FQDN and see if it solves the problem. The settings will be refreshed when the GPO is refreshed.

    Torsten Meringer | http://www.mssccmfaq.de

    • Marked as answer by Uber Random Saturday, February 9, 2013 12:44 AM
    Tuesday, January 22, 2013 7:30 AM
  • That seems to have fixed it.  Sorry it took me so long to answer back.  Thanks again for all the help! Again, you guys rock!

    Über Random

    Saturday, February 9, 2013 12:43 AM
  • That seems to have fixed it.  Sorry it took so long for me to respond back.  Thanks again for the help; as always, you guys rock!

    Über Random

    Saturday, February 9, 2013 12:45 AM
  • From what I gather in 2018 with build 1711, you don't need to have a GPO settings for WSUS.. the agent sets this locally on the clients?

    Run report - Computer Failing with Scan Errors will show you if there are any GPO conflicts with SCCM..

    Cheers

    Thursday, February 1, 2018 2:44 PM
  • Yes thankyou Torsten Meringer. This worked for me.

    I also had to put in the port number (8530) after the FQDN

    Brilliant thanks for your help!

    Thursday, August 27, 2020 9:27 AM