Hey all I have been having hash issues with drivers. I have removed the drivers from SCCM then re-distributed them and still get hash errors.

In this recent round I decided to removed the delete the drivers from their driver packages then delete the packages themselves and then will add them back in and then distributes them. This operation is still in progress so I'll post a status update when the process is done.

My SCCM server is server 2008 R2 with most if not all updates applied to the OS and also to SCCM itself; well that I can think of at the moment.

Just for the heck of it I went and installed MDT 2013 as a standalone system and imported the drivers for the various computers that I am currently trying to use and BAM stuff just works! No hash errors, no driver issues (I was getting OS error 31 during installation and it was driver issues because they wouldn't install and blow up the whole process using SCCM to deploy a fresh OS from installers for Windows 7 64-bit) and of course no automation. Sigh! So to get this working, I created an application in MDT to install the SCCM client, bam, some automation after the fact.

hmm ... when I see hash errors and the like I immediately start suspecting AV scanners (im a suspicious guy that way) ... are you using file level scanners on your Primary and/or DP?  Are the content library directories and DP directories excluded?

Definitely agree with Justin. . .A/V is a likely culprit here.

I've seen A/V software cause issues with ini files, autorun.inf files, and various other file types.  Make sure you have exclusions in place on your DP.

Jeff

hmm ... when I see hash errors and the like I immediately start suspecting AV scanners (im a suspicious guy that way) ... are you using file level scanners on your Primary and/or DP?  Are the content library directories and DP directories excluded?

• Marked as answer by Daniel JiSunMicrosoft contingent staff, Moderator Wednesday, July 01, 2015 7:40 AM
• Unmarked as answer by AnonymousToday Wednesday, July 01, 2015 2:49 PM

Definitely agree with Justin. . .A/V is a likely culprit here.

I've seen A/V software cause issues with ini files, autorun.inf files, and various other file types.  Make sure you have exclusions in place on your DP.

Jeff

• Marked as answer by Daniel JiSunMicrosoft contingent staff, Moderator Wednesday, July 01, 2015 7:40 AM
• Unmarked as answer by AnonymousToday Wednesday, July 01, 2015 2:49 PM

Having deleted the packages, since redistributing them while in the system didn't resolve the issue, I then redistributed the content and that corrected the issue. I am guessing that this forced System Center to create a new hash. As a side note, no AV is installed on the system.

• Marked as answer by AnonymousToday 16 hours 32 minutes ago

Having deleted the packages, since redistributing them while in the system didn't resolve the issue, I then redistributed the content and that corrected the issue. I am guessing that this forced System Center to create a new hash. As a side note, no AV is installed on the system.

• Marked as answer by AnonymousToday Thursday, July 02, 2015 3:16 PM