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.