We recently upgrade our SCCM environment to SP1. I am attempting to deploy client the client upgrade package however it keeps failing with a hash mismatch on silverlight.exe. I have deleted my package and created a new one and pushed it tp the DPs with no success. Even the default client package fails with the same error. Any ideas? Oddly enough, If i manually install the newest version of silverlight pulled down from Microsoft, and then kick off ccmsetup, it succeeds. Here is a snip of the log

File C:windowsccmsetupSilverlight.exe with hash 417B442E128D821119008ACEEEE6CDC2A41224377A829B6EC52BABA2724F0151 from manifest doesnt match with the file hash 97450071AFAD60A78E499B3F8B856ACA4336EC9985C6E828C6A6EC89AF7E60C9 ccmsetup 7/17/2013 9:48:09 AM 2932 (0x0B74)
Deleted file C:windowsccmsetupSilverlight.exe ccmsetup 7/17/2013 9:48:09 AM 2932 (0x0B74)
Validated file C:windowsccmsetupclient.msi hash 2F0819F959E788CF843F42E9CA7B44E258B8B4BA37BB63902DB39ACF747BE7DA ccmsetup 7/17/2013 9:48:09 AM 2932 (0x0B74)
Using branch cache option. ccmsetup 7/17/2013 9:48:09 AM 2932 (0x0B74)
Adding file http://WDC03W602V.limitedstores.com:80/SMS_DP_SMSPKG$/WDC00002/i386/Silverlight.exe to BITS job, saving as C:windowsccmsetupSilverlight.exe. ccmsetup 7/17/2013 9:48:09 AM 2932 (0x0B74)
Starting BITS download for client deployment files. ccmsetup 7/17/2013 9:48:09 AM 2932 (0x0B74)
Download Update: Connecting to the server. ccmsetup 7/17/2013 9:48:10 AM 2932 (0x0B74)
Successfully completed BITS download for client deployment files. ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
Retrieved client version 5.00.7804.1000 and minimum assignable site version 5.00.7783.1000 from client package ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
Checking compatibility of site version 5.00.7804.1300, expect newer than 5.00.7783.1000 ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
Site version 5.00.7804.1300 is compatible. Client deployment will continue. ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
Successfully downloaded client files via BITS. ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
Validated file C:windowsccmsetupMicrosoftPolicyPlatformSetup.msi hash 8C42189693C3220017E8C93A79B989EE126ADF33EADBE229011404C123B7B897 ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
File C:windowsccmsetupSilverlight.exe with hash 417B442E128D821119008ACEEEE6CDC2A41224377A829B6EC52BABA2724F0151 from manifest doesnt match with the file hash 97450071AFAD60A78E499B3F8B856ACA4336EC9985C6E828C6A6EC89AF7E60C9 ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
Sending Fallback Status Point message to WDC03W601V.limitedstores.com, STATEID=325. ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
Params to send FSP message 5.0.7804.1000 Deployment Silverlight.exe ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
State message with TopicType 800 and TopicId {E482D005-EF84-4297-992B-F7A8C8059827} has been sent to the FSP FSPStateMessage 7/17/2013 9:48:34 AM 2932 (0x0B74)
Deleted file C:windowsccmsetupccmsetup.xml ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)
CcmSetup failed with error code 0x87d0029e ccmsetup 7/17/2013 9:48:34 AM 2932 (0x0B74)

Have you taken a look at the following:

http://social.technet.microsoft.com/Forums/en-US/fbc4f06e-5223-4a21-a989-868c40c1d1d2/management-point-still-has-old-version

Thanks for the response.

I read through that article a few days ago. I verifed that everything has upgraded properly to SP1. I am only having an issue with Silverlight. I ahave updated the packed on the DP's as well however the promblem persists.Imaging fails also when trying to install the default client package.

Regards

Evan

It looks as if i resolved my own issue. For some reason the Silverlight.exe that was in the source directory was corrupt. No idea how that could have happened. I was able to obtain Silverlight 5.1.10411.0 via Microsoft and voila, problem solved. I had attempted to use the newest version however it will only work with 5.1.10411.0.

Cheers