Hi, We are currently using Task Sequences in order to deploy software packages sometimes multiple sometimes simple packages. Our site setup means we have a CENtral server 3 primary and the rest made up of Secondary or BDP's. As the title suggests we seems to have this ever occuring issue where by ( for example my deployment today that prompted this) I am deploying Adobe and one other application to 400 machines last night. This morning I come into around 18% of these have failed and generally the error is similar to below: 05/10/2010 16:11:44 Accepted Program received 10002 12177032 05/10/2010 22:59:01 Running Program started 10005 12202192 05/10/2010 23:04:06 Succeeded Program completed with success 10008 12202596 05/10/2010 23:04:07 Waiting Waiting for content 10035 12202606 05/10/2010 23:04:29 Failed Program failed (download failed - content mismatch) 10057 12202849 06/10/2010 05:00:01 Expired Program expired 10019 12207830 As you can see highlights the download failed content-mismatch is my issue,. Now what is weird is that a large proportion work perfectly fine however 18% is to big a number to fail on a regular basis. I have searched the length and breath of the internet for answers and thet vary in how to potentially resolve it. I have tried updating the DP but that did not work, i have not turned of binary replication as its a BDP, im reluctant to do anything ultra extreme baring in mind that so mnay complete with no issues. In this TS there are two apps and on a few machines i have sampled the CAS.log file it seems to reference one or the other package that failed to downloard and sure as anything on that machine it is not in the cache folder. Anyone throw anylight on this be most apprecaited. Thanks in advance

Usually an "Update Distribution Point" works fine for these issues. If you are still seeing that this isnt working you can modify the source path then change it back to its original source path and update this should change the content version and rereplicate the content. If that does not work it might be easier to just remove from that BDP and wait until its fully removed from the BDP and then repush back down to it. Verify in the package status that the package is actually updating on the BDP.Thanks, Brandon

Hi, Take a look at this thread: http://social.technet.microsoft.com/forums/en-US/configmgrswdist/thread/d8fe15f3-fbb3-4993-a111-cca2c1d1a5d7/Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.