Trend OfficeScan 10 causing Hash Mismatch Errors in SCCM 2007

For the last 2 years of my SCCM Career I've been blighted with issues concerning the above.  I've added exceptions to our Trend server, calls have been logged but I can never seem to get this sorted.

I find that if Trend is running the execmgr.log will sometimes show Hash Mismatch errors.  If I manually disable Trend (or better still remove it!!) - it works fine.

I've started adding a quick command to my Task Sequences and package deployments to temporarily disable OfficeScan while the deployment takes place and it works a charm!!

Simply add the following command lines before and after via Task Sequence or simply create a package with a batch file containing the following.

Before:

net stop tmlisten
net stop ntrtscan

After:

net start tmlisten
net start ntrtscan

Obviously this works manually too if you should ever need to disable Trend remotely...  Even if it has a password!!!!!!!! ;)

X1 Carbon Incorrect Hash Errors during OSD

I was fighting with this one for a couple of days.  Lenovo X1 Carbon - deploying Windows 7 x64.  All drivers were fine and dandy but I was getting randon "Incorrect hash value" errors when the OSD was failing.

This was determined by looking in the SMSTS.log once the OSD had failed.

It transpires that if the USB to Ethernet adapter was plugged in to the right hand USB socket it was dropping loads of packets.  Plugging it into the left hand side worked a treat.

As simple a solution as it sounds this may be far too obvious for some tecchy to even try.  I managed to replicate this on 3 different units so it wasn't just faulty parts.

Felt like a complete numpty once I discovered the fix!

OnContentAvailable program 0x80091007

Symptoms:

When deploying software to a collection the client execmgr.log shows the following error:

OnContentAvailable program 0x80091007

You will notice a hash mismatch also " SoftDistAdvertHashMismatchEvent" - when checking the CAS.log you will see

"Hash matching failed."

Cause: 

SCCM is a temperamental bitch

Solution:

Goto the package in question and right click on Distribution Points and click "Manage Distribution Points".  Choose "Update all distribution points with a new package source version" - and thats exactly what happens.
Kick of a hardware policy cycle on the client and watch the magic.