Hy,

we have problem with SCCM 2012 SP1 on Windows Server 2012 with OSD. When task sequence reaches Setup windows and configmgr it fails with following error:

0x80091007 hash value is not correct.

If i create new package from definition for sccm client, then it works for couple of computers 2-3, then error appear again..and so on.

Today we setup clean install of Server 2012, SQL 2008R2 sp2, and SCCM 2012 sp1. Pxe boot worked for 2 computer, then fails again with same error.

We tried with different images, Win 7 enterprise and professional, with captured image, but still the same.

Content validation is always OK.

There is no antivirus software

• Edited by andrej pus Thursday, February 07, 2013 3:46 PM

Hi,

Any Anti-virus installed? Exclusions made for Configuration Manager?

I have seen a lot of strange issues whith different Anti-Viruses..

Regards,
Jrgen

There are no antivirus software, all firewalls are off. OSD downloads sccm client files then error appear. I read somewhere if there is a hash problem, you cant create standalone media, but we can create it just fine.

Is this possible:

1. can you install sccm client into image, then when you deploy throught OSD ts, can u install applications? So we dont need setup windows and configmgr step?

2. Can i make my ts only install SCCM client from distribution point? So there is no hash checking.. i know there is a way if all packages are run directly from dp, but can i make only sccm client?

Just to make sure..there is no AV running on your Server hosting the Distribution Point? As Jrgen stated, there are known issues with AV even scanning the DP directories that can throw off hash values...

there is no antivirus

here is smsts.log

http://www.filedropper.com/smsts

I removed all drivers, but didnt help..

• Edited by andrej pus Thursday, February 07, 2013 3:50 PM

Did you use the latest version of the source files for ConfigMGr 2012 SP1, updated on the 25/1, or have you applied kb2801987 http://support.microsoft.com/kb/2801987?wa=wsignin1.0?

i have applied kb, but this kb is for different error.. This is strange issue, some of packages after couple of deployments fails with error 0x80004005. It looks like something is destroying packages... For example Office 2010 application works for couple of deployments, then it fails and i need to recreate the application. There are no other error in logs or in event viewer.

I have 4 other customers on SCCM 2012 and all works fine. Difference is only that here is Windows Server 2012...

If i install sccm client in master image, can i run TS and install applications?

If i install sccm client in master image, can i run TS and install applications?

You dont want to do this, believe me :)

Is your DP really working fine? I first would disable prestage content support from DP and re-apply confmgr client once more.

Prestage is disabled, i reapply client 10x times. Sometimes works, than stops...  System status in monitoring - all green and OK. I made clean install of sccm 2012, first 2 machines were ok, then error appear again...

Interesting thing - 2 same machines, first one fails with setup windows and configmgr, log is above, second machine was succesfull... I tried with 3 different machine vendors, lenovo, hp, fs...

Hi we have the same issue, task sequences fail after the upgrade. Kb mentioned applied. At the moment it seems to be 2 things, the unattended.xml being 1 and the other seems to be drivers fail. We remove these things and we can get the sequence through sometimes. The other issue is it does not seem to be consistant. Our main sequence is a windows 7 using setup. This upgrade is not stable in our view. ms have put us in a very bad place here.

We have temp solution. We put distribution point on Server 2008r2 and everything works fine..

Was a permanent solution ever found for this? I'm experiencing exactly the same problem.

I'd also like to mention I have this issue aswell. It seems that it works once, then hash check fails. Validated content fine. It starts with hash check error on MDT toolkit, fix that up, then the actual image, fix that up, then driver package. I take all packages away from distribution point, re add them.. can build a machine, then hash fails again.

SCCM 2012 SP1, Windows 2012 - all current updates, Have not tried CU1 yet but no reference to this issue.

The most common thing I see that causes numerous Hash value mismatch is Antivirus scans against your DP directories.  If that's not the issue maybe run a check disk against the volume that is having issues to ensure no disk corruption is happening?  I have 1 Primary and 14 Secondary's and have rarely seen a hash mismatch on my 2012 servers, but I exclude the DP directories from Virus scan..  Wish I had more for you.  :-/

I don't have any AV on the 2012 server in question. I can also confirm that updating the DP does not fix the problem.

It's the randomness of it that's frustrating. It will work one moment and fail the next, with nothing changed in between. 

I really don't want to have to put the DP on another server but it looks like that's what I'm going to have to try now.

vivavilla - Im just checking something out, but you also running on VMware 5.1?

My environment uses VMware 5.1.

I was using the E1000E driver on my Windows 2012 DP, I changed it to VMXNET3 and the problem went away.

I only got this problem deploying to physical hardware.. it would always work in a VM.

• Proposed as answer by vivavilla Tuesday, April 02, 2013 10:34 AM

iluciv, you sir are a genius! No idea how you figured that out but it appears to be working flawlessly now I've changed to VMXNET3.

Thank you!

I will add that I have the exact same setup: SCCM 2012 SP1 on Windows Server 2012, VMWare 5.1 using E1000E driver. Same constant, random hash mismatch symptoms on all packages within the task sequence (not just the client setup files). Changing the NIC to use VMXNET3 worked like a dream.

Replacing the E1000 driver in VMware with VMXNET3 fixed all the hash errors and made the TS run a lot faster.

Replacing the E1000 driver in VMware with VMXNET3 fixed all the hash errors and made the TS run a lot faster.

This saved lot of time . Thanks all