Article ID: 2709963 - View products that this article applies to.
Consider the following scenario:
1. You are using Windows Deployment Services in System Center Configuration Manager 2007 (ConfigMgr).
2. You are configured to use multicast.
3. You are deploying sparse files as part of your deployment.
In this scenario we see that some installation images get downloaded as sparse files. Because the initial hash is computed before the files are made sparse and the verification hash afterwards, both hashes are different. This leads to the deletion of the image and the failure of the install.
When you run into this problem will also see entries similar of the following in the SMSts.log file:
Found sparse part of the file: 5236588544 8192
This occurs because WDS multicast does not support sparse files in the current release.
In a pure WDS environment you can use wdsmcast.exe /usesparsefile:no to work around the problem. In ConfigMgr, currently the only option is to use unicast (i.e. disable multicast).
For more information on how multicast is enabled/disabled, see the following:
How to Enable Multicast for Operating System Deployment : http://technet.microsoft.com/en-us/library/cc161854.aspx
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Contact us for more help
Connect with Answer Desk for expert help.