Today I was noticing on a few of our advertisements that all of our machines in the collection had received the “Program failed (download failed – content mismatch)” failure message.
Note that when doing a client push installation you can specify custom install strings directly in the SCCM GUI (more on this later) Alternatively SCCM allows you to deploy it’s client using WSUS…
this method is much easier and simpler to achieve in an AD domain environment & really if your planning on using SCCM to control patching for your organisation is the only choice you should consider.
This method can be very messy as you have to have an account that has local admin rights on each pc, you also need to make sure you have a bunch of ports open on any firewalls between your SCCM server and the client (for CIFS and WMI).
If any of these factors are out, or the remote machine is turned off when SCCM tries to install, you can end up getting heap of error messages in your SCCM logs that will ultimately show your hierarchy as being unhealthy.
During a recent SCCM 2012 deployment I noticed an issue when deploying the client using WSUS integration.