Article ID: 2000470 - Last Review: May 3, 2011 - Revision: 9.0 ConfigMgr 2007: Multicast OS deployments fail with a hash value error when the Windows OS WIM file is over 4GB
SymptomsWhen using an Configuration Manager 2007 OSD Task Sequence to deploy a Windows OS WIM file over 4GB via Multicast, the Task Sequence and deployment fail right after the WIM file is downloaded. Examining the SMSTS.log shows that the deployment failed due to an incorrect hash value: Using LocalPath: C:\_SMSTaskSequence\Packages\<Package_ID> The same Windows OS WIM file deploys correctly via Unicast. Additionaly, Windows OS WIM files under 4GB deploy via Multicast without issue. CauseThe problem is caused by a known bug in Configuration Manager 2007 SP1 R2 where the hash calculations are not performed correctly when going over the the 32bit barrier (approximately 4GB) and going into 64bit calculations. This occurs when the WIM file size
is just over 4GB. ResolutionThe bug has been fixed in KB971413. KB971413 replaces the smswdstp.dll file that has the faulty code. The new DLL file has the proper code to perform hash value 64bit calculations. To correct the problem, install KB971413 on the parent site server of the
Multicast DPs. More InformationAfter applying KB971413, some or all of the following actions may need to be taken for Multicasting to function properly again:
Please see Knowledge Base article 2000468 for additional information and detailed steps. Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations. | Other Resources Other Support Sites
CommunityGet Help Now
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
