Skip to main content
Question

Installing Silverlight?

M
Forum|alt.badge.img+12
  • musat
  • Valued Contributor
  • 181 replies

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?

    10 replies

    B
    Forum|alt.badge.img+5
    • bthomason
    • Contributor
    • 30 replies
    • May 16, 2014

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

    M
    Forum|alt.badge.img+12
    • musat
    • Author
    • Valued Contributor
    • 181 replies
    • May 16, 2014

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

    bentoms
    Forum|alt.badge.img+35
    • bentoms
    • Legendary Contributor
    • 4331 replies
    • May 16, 2014

    @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.

    B
    Forum|alt.badge.img+5
    • bthomason
    • Contributor
    • 30 replies
    • May 19, 2014

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

    bentoms
    Forum|alt.badge.img+35
    • bentoms
    • Legendary Contributor
    • 4331 replies
    • May 21, 2014

    Are you guys using JDS?

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

    M
    Forum|alt.badge.img+12
    • musat
    • Author
    • Valued Contributor
    • 181 replies
    • May 21, 2014

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

    B
    Forum|alt.badge.img+5
    • bthomason
    • Contributor
    • 30 replies
    • May 22, 2014

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

    F
    Forum|alt.badge.img+10

    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.

    M
    Forum|alt.badge.img+12
    • musat
    • Author
    • Valued Contributor
    • 181 replies
    • May 22, 2014

    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.

    T
    Forum|alt.badge.img+15
    • thoule
    • Contributor
    • 589 replies
    • May 22, 2014

    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.

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settingsAccessibility statement

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings