Installing Silverlight?

[musat]

Hello,
We are trying to update our Silverlight installs to 5.1.30317.0. In the past I would just download the DMG and pull out the Silverlight.pkg file. I would then rename the PKG to include the version number. In this case: Silverlight.5.1.30317.0.pkg. Then I would upload this PKG to Casper Admin, update the Policy and all would be fine. This most recent time, most (probably 95%) of the clients trying to install get the error

Downloading Silverlight.5.1.30317.0.pkg...
Verifying package integrity...
Installation failed. The package could not be verified.

Though a very small handful actually install successfully. We are running Casper 9.31, and I am using Admin 9.31. Do I need to go the full Composer route to install Silverlight now?

[bthomason]

I am having exact same issue, if you look in CasperAdmin notice the Checksum for Silverlight has an MD5 error.

[musat]

Ahh yes, I had to resize all of the columns to finally see what that said. ```
Index.bom: No such file or directory
```

[bentoms]

@bthomason, the checksum should be generated via Casper Admin when uploading a package into Casper Admin 9.3x.

So it's a bit odd if it's invalid, but do you need to verify the checksum? You can remove that requirement.

[bthomason]

@bentoms, do you remove it in the JSS Settings under Security?

[bentoms]

Are you guys using JDS?

If so, might be related to: https://jamfnation.jamfsoftware.com/discussion.html?id=10666#responseChild60223

[musat]

Hello, we are not using JDS and we have not run the migration yet either.

[bthomason]

@bentoms no we are not using JDS, I'm on 9.31

[fabian_ulmrich]

I have seen similar issues when packages were downloaded via SelfService. Check if you have any faulty downloaded packages in "/Library/Application Support/JAMF/Downloads". If so, remove those and try to install again.

[musat]

I'll add now, that we finally went ahead with the Migration in Casper Admin. After doing that I re-added the Silverlight package and it uploaded successfully and created the checksum properly.

[thoule]

Removing the package and re uploading it will avoid the issue. One cause of this problem is that the MD5 checksum is wrong. Right click the package in Admin and choose Calculate Selected Package Checksum.