In the case I’m not the last one in the world to know this site, appdeploy.com provides useful info and tips & tricks about packaging common applications…
This must be the shorted post ‘till now 
When deploying several packages trough SCCM, I ran into this one particular package which would stop downloading without any clear reason. When checking the log files, these would not display an error, just the download process would show that it suddenly stopped downloading… The SCCM Client center tool showed a ‘WaitingContent’ status.
After some searching I found this article from Matthew Boyd which pointed me to the fact that this was an IIS problem and not a SCCM problem. The IIS logfile showed an ‘404.8 – hidden namespace’ error. The cause for this error was the Request Filtering feature for the Web Server which contains a <HiddenSegments> portion in the ‘applicationHost.config’ file. Since my package contained a bin folder, I had to remove the line: <add segment="bin" />. The ApplicationHost.config file can be found here: “%windir%\System32\inetsrv\config\”
So finally I would be able to deploy my package… or not?
Next error I bumped into was again an IIS error, now giving me a ‘404.7 – File extension denied’ error. This is due to the same Reguest Filtering feature where in the same ‘applicationHost.config’ file there is a fileExtensions portion. For each file extension of which files exist in the package, I changed the line to allowed=”true”. This is something that is pointed out in the prerequisite steps by Microsoft but since I had no idea of which packages would get distributed at the time of installation…
And still I could not get my package deployed…
Now I received the error in the SCCM log file that the hash verification failed. To solve this problem I had to verify that no files were marked hidden in the package. Once these files were no longer marked as hidden, and did a refresh (not an update!) of the DP, the package finally installed correctly…
For some days I’ve been searching for a problem I came across when deploying XP machines with SCCM. The problem was that my driver would not get installed as part of the task sequence. A problem that never occured when deploying Vista/Windows 7 machines.
After some searching around I came across this post: http://myitforum.com/cs2/blogs/jsandys/archive/2009/03/12/old-dog-new-tricks.aspx
As mentioned in the post, I also tried adding/removing the drivers, recreating my TS, etc without result untill I added a command line at the end of my task sequence:
rundll32.exe Syssetup.dll, UpdatePnpDeviceDrivers
This reinitiates the Windows Hardware detection and all drivers were installed without a problem…
While deploying my first Windows 7 client with SCCM 2007 R2 SP2 I would receive a failure when the sysprep task would start. However the cause for this error was not due to my sysprep package but my SCCM client package. I had forgotten to create a new SCCM client package to use in my task sequence after installing SP2:
New package from definition -> select “Configuration Manager Client Upgrade”