Today I had a strange issue when deploying a Windows 7 Capture image to a fat client. With every deployment there was a hash mismatch during the "Apply Operating System" step. In a normal situation this can be resolved easily by updating the distribution point. In my case however this was not the solution. Removing the OS image from ConfigMgr and add it again (so a new Package ID is created) was not the solution also.
Still a hash mismatch, with the following errors:
-Failed to hash file, Win32 error = 23
-Hash could not be matched for the downloaded content. Original ContentHash = <hash>, Downloaded ContentHash = <empty>
-The hash value is not correct 0x80091007
The solution for this is as follows:
Select "Apply Operating System" in the Task Sequence Editor and open the Options tab. Check "Access content directly from the distribution point".
Right-click the reference image package in Operating System Images and open the Properties dialog. Configure the Package share settings on the Data Access tab. Check "Copy the content in this package to a package share on distribution points".
After that OS deployment was running fine again. No hash mismatch anymore! Still strange that updating the distribution point was not helping me this time.
Today I want to configure multicast in ConfigMgr 2012 SP1. An important thing to do is enable multicast on the Distribution Point. Another important thing to do is enable multicast on the Operating System image. Just select "Allow the package to be transferred via multicast (WinPE only)" for that. Start a new deployment on a system and multicast should work immediately!?
After configure above settings an error message is displayed during deployment: 0x80091007. Looking in SMSTS.log the following is mentioned: The hash value is not correct. (Error: 80091007; Source: Windows). This can be solved with distribute the package on DP again. Unfortunately this isn't the case. I still get the same error message during deployment.
When disable multicast on the Distribution Point, deployment is working again. Is there someone who recognizes this error message and has a solution for it? I found THIS and THIS on MS TechNet, but no answer yet. Hope someone has a solution for me. Thanks!
Update 28-5-2013: Last month at customer location we created 3 images for multicast usage. First image (4GB) went fine immediately. Second image (6GB) went fine after update Distribution Point (DP), before that same error message. Third image (11GB) still isn't working, after multiple update DP actions. Still don't know why it's failing.. error messages are shown in the screenshot.
Update 19-6-2013: Nick send me a possible solution in comments. What you have to do is make sure you don't have a custom Multicast range set - use the setting "Use IPv4 addresses within any range" in the SCCM 2012 multicast tab under Distribution Point properties.
The default is 239.0.0.1 to 239.0.0.254 - if you have a custom range set - it IGNORES it and uses a random address in 239 range anyways. He has tried to statically set a 239 range on both SCCM multicast and WDS multicast settings - ignores them still uses a random address in the 239 range regardless.
On your Cisco core - if your using that - make sure your ACL's and Rendezvous Point ACL for PIM permits the 239 range. As soon as this was done it's all working. > Will try that myself next month!
