Skip to main content

Hi,

After I created a Build pkg of CS6 from Adobe AAMEE, I tried to upload onto Casper Admin for Imaging. they can upload the pkg successfully but the CS6 File size is different ( Regular File Size: 7.66GB, after added onto Casper Admin, the file size is 5.2MB, This also happens on my other pkg as well: MathType, Typing Tournament)

I thought this is the way how Casper works, so then I given them a Category as: "Adobe", Priority: "10". then "Save".

Later on I create a Policy for a test to deploy Adobe CS6 onto Testing Mac Macbook pro. An hour later, I checked on the Testing Machine, Adobe has not been install. Checked on the "Policy Log", They said, "Invalid file path..." something like this.

Is there something I did wrong?
and why there is a File size difference to my uploaded pkg onto Casper Admin.

*Note: if I install the pkg manually without using casper, it successfully installed

@bentoms @TheDecline Also force AFP...for some reason HTTP fails when dealing with AAMEE packages.

@Don.. even when caching?

@bentoms I remember we were having issues with HTTP so we switched to AFP, and there was another reason why we were caching, so we ended up combining AFP and caching. Hmm...can't remember if we tested HTTP and caching. I guess if HTTP works that would be great since it's a resumable download. Is that what you guys are doing? Pencil and paper in hand... :)

@Don, we're looking to move to HTTPS from AFP.

Guess I'll test this! & will report back.

@Bentoms

that was it i had to cache the pkg first then install from cache. Thank you.

And thank you everyone who gave direction.

Happy New Year

Beer for @bentoms! :)

external image link

Awesome! Will hopefully cash that beer one JNUC.

Terms & ConditionsCookie settingsAccessibility statement