Currently running SCCM 2012 R2 on Windows Server 2012 R2.
My question is, when updating the boot image with new drivers and distributing out to distribution points, does checking the 'Enable binary differential replication' really only replicate those new changes? I do not think it would since the .WIM file would be changed. It would take some DISM commands to rip open the .WIM on the DPs and recompile. Possibly even resulting in a different hash value for the file and causing a different problem. I can't find much information for this "delta" scenario.
I have 200+ sites that would need to update the .WIM and they actively use OSD services throughout the day. Transfer speeds to a DP would be around 1 hour per site, but a site would be down while it sits in the distribution queue waiting to receive the new WIM I believe since the hash wont match.
Is this just the nature of the beast, am I wrong about the pending transfer and failing hash check? I have toyed with having an alternate boot image that I try to keep in parity and can slide task sequences over to for interim, but would like to avoid maintaining multiple boot images.