Skip to main content
Blog

SCCM Software Updates GPO conflict

by Dan Newton

As we all know details matter… in SCCM this can be painfully true. And today I find yet another little item that bears this out.

A client of ours is moving from GPO/WSUS management of Windows Updates to SCCM 2012 R2. There’s a great article about dealing with the migration of the GPO settings by using GPO preferences.

We made sure we had all our settings configured properly… yet the GPO conflict (error 0x87d00692 in the ScanAgent.log) remained on all the test systems. What’s a guy to do??

Come to find out the GPO Preference was pushing down the SCCM’s short name and not FQDN. Changed the GPO Preference forced and policy update (gpupdate /force) and there you go no errors.

Details matter.


2 comments to SCCM Software Updates GPO conflict

  1. AJ Hawkes
    June 23, 2017

    Hi Dan,
    In SCCM Current Branch, how do you prevent the client from looking to Windows Update to download updates, and strictly wait for updates to be pushed down from Configuration Manager? I am migrating from WSUS to SCCM for Windows 10 updates, and removed the Group Policy domain settings, and now all clients want to download updates from Windows causing me massive bandwidth issues. I found a Group Policy that prevents all Windows Updates (Turn off all access to Windows Update features), but if I understand correctly, I still need this available to download drivers for new hardware.
    Any help is appreciated!
    Thanks in advance!
    AJ

    Reply

Leave a comment