I'm trying to deploy Adobe CS3 Master Collection with SCCM 2007 SP2 as part of an OSD TS and I consistantly getting this error. I've trawled these forums (and others) and am going round and round in circles getting no where near a resoltuion. These are the things I have tried: Updated the package on the DP Removed and re-added the package to the DP Completly removed the package from <acronym title="System Center Configuration Manager">SCCM</acronym>, re-created and re-added to the DP Refreshed the package on the DP and updated the package immediately Applied the hotfix from KB2276865 to the client - I read on another forum this could be casuing an incorrect hash Changed the TS advertisment and set the option: Access content directly from a DP when needed by the running TS Checked for non ACSII characters in the file paths - I read that this could cause an incorrect hash distmgr.log confrims that the package sucessfully copied to the DP and when I look at smsts.log on the client (after the task fails) the hash that the client is expecting does differ when the package is downloaded. But why? If I advertise the same package once in the OS (just as Software Deployment) the package downloads to the client and installs correctly as you would expect. At the moment I am testing this with only 1 client so it's not a multicast issue - I've read a lot of posts where people are having this problem with trying to multicast. A little environment information: SCCM 2007 SP2 running on W2K8 R2 Std (as a VM) SCCM is running in Mixed Mode The DP is on the same server as the site server (there is only 1 server) Any ideas?

On a few posts the solution is to change your advertisement to run from the DP’s instead of downloading. So change the advertisement used for OSD, from "Download content locally" to "Access content directly" and also mark the two checkboxes beneath it. (OSD Advertisement -> Distribution points)My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

This happens when the sigfile differs from the calculated hash when the client downloads the package. I have this problem occur all the time, to get around it I do the following remove the offending package from the distribution point wait for it to be removed then re add it to the distirbution point once re installed then update with a new source version. You'll see the version number on the package increment when its finished This forces the package to recreate its sig file, you may be able to just get away with updating with a new source version but i have found it to be problematic.

Henk, I've already done that and it didn't seem to have an effect. Cheers Adam.

RedSt0rm, I've done that, the version number has increased but I am still getting 0x80091007 incorrect hash value. Unfortunatly this is quite a critical piece of software that we need installing and I would prefer everything is installed as part of the OSD task. Any more suggestions? Cheers Adam.

Hi, Have you tried to change the Data Source to another folder (for instance a folder with a simple textfile). It will automatically update the DP. After the DP is updated try to switch back to the origanally Data Source and try to see if it helps.

Does that differ from completly removing the package from the DP and re-adding it?

Anybody have any more ideas on this as I am still stuck.

Just pulled this from the distmgr.log on the SCCM server and spotted info about 2 different times when refreshing the package on the DP: Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.268 2011 GMT Daylight Time><thread=2456 (0x998)> ~Starting package processing thread,thread ID = 13A4 $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.269 2011 GMT Daylight Time><thread=2456 (0x998)> ~The last source update time for pkg RC100005 is 04/01/11 15:13:24 GMT Daylight Time $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.275 2011 GMT Daylight Time><thread=2456 (0x998)> ~The next start time for pkg RC100005 is 04/01/11 16:13:00 GMT Daylight Time $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.276 2011 GMT Daylight Time><thread=2456 (0x998)> ~The last source update time for pkg RC100037 is 04/01/11 09:40:29 GMT Daylight Time $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.280 2011 GMT Daylight Time><thread=2456 (0x998)> ~The next start time for pkg RC100037 is 04/02/11 09:40:00 GMT Daylight Time $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.280 2011 GMT Daylight Time><thread=2456 (0x998)> ~The last source update time for pkg RC100038 is 04/01/11 10:15:25 GMT Daylight Time $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.284 2011 GMT Daylight Time><thread=2456 (0x998)> ~The next start time for pkg RC100038 is 04/02/11 10:15:00 GMT Daylight Time $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.284 2011 GMT Daylight Time><thread=2456 (0x998)> ~Sleep 2156 seconds... $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.284 2011 GMT Daylight Time><thread=2456 (0x998)> STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCFGMGR SITE=RC1 PID=1952 TID=5028 GMTDATE=Fri Apr 01 14:37:04.285 2011 ISTR0="Adobe CS3 Master Collection" ISTR1="RC100075" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RC100075" $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 01 15:37:04.285 2011 GMT Daylight Time><thread=5028 (0x13A4)> Could this be causing a problem with the hash values?

Was caused by some html files with hypens and non-ascii characters.

I am getting tis issue adamf83 - what html files were they?

SCCM4EVA, They are located here: payloads\AdobeDeviceCentralAll\oem\Adobe Device Central 3 I believe the actual one causing the problem is Device Central CS3 Léame but I removed them all from the package just to be on the safe side.