@donmontalvo

Hi Don,

Thank you for the question and I apologize for not mentioning this.

With this command we are granting everyone at read and execute so the package and any internal files can be read and run properly.

If we are in a Windows environment for example we could do the following:

1. Right click on the package and select Properties


2. Click on the Security tab


3. If everyone is not part of the list add them


4. Verify that the Everyone entry has Read and Write access

As you mention Don we will want to set these settings recursively so all of our files inside get the same permissions.

Again if we have issues outside of the defect that was mentioned here I suggest reaching out to your account manager to help identify what other issues might be happening.

Derek

And for the other 1000 packages? Still right click...?

Feature request...seriously?

This should be standard the when saving on Casper Admin it automatically goes through the item in the share, add every and gives everyone read access.

Come on guys this has been a massive problem and hassle for too long

@tkimpton In other environments the datacenter team were able to set the security tab for the top of the share, and not sure how but they were able to make it recursive and persistent - so going forward anything going into the share picks up the right permissions.

Whack it up people

https://jamfnation.jamfsoftware.com/featureRequest.html?id=1141

Dont know either but right click every item is a poor solution to an old ongoing issue.

@tkimpton

Hi Tim,

The example that I posted here was to give the same steps on a Windows environment as running the command on in the Mac. I had posted it because I had seen in the past that specifically in Adobe packages that running that command would help fix some issues I had seen on AFP shares.

If we are using an SMB share, we should be pushing out the Adobe packages with the steps in the following KB article for using the PKG inside a DMG:

https://jamfnation.jamfsoftware.com/article.html?id=161

If we are having permissions issues on all of our packages then I would to look at our SMB share, there might be some things we would want to take a look. If this is an issue we are seeing I would suggest contacting your account manager to help look further into this.

Thanks,

Derek

FYI, I was having trouble with this as well, and my support rep sent me this:

When we run the firstrun script when imaging, we create a user called adobeinstall. This is not a fully fleshed out user, but more of a temp user. With Adobe CS6 Adobe not does checks to make sure this is a more "fleshed" out user. So we we have done is created a little package that will "flesh" out the adobeinstall user to ensure that the installer will run properly. Attached is the package, please follow the work flow below, and let me know if you run into issues.

- Add the AdobeUser.pkg to the FirstRun process and make it priority 1
- Add the AdobeUser.pkg to a configuration with an Adobe installer package in it

Here's a link to the AdobeUser.pkg:

https://dl.dropboxusercontent.com/u/169986/AdobeUser.pkg.zip

Hope this helps someone!

--Andy

Thanks for the upload Andy, I'm actually working on a CS6 deployment process that includes scripted removal of CS4, so this is coming at the right time.

It would be nice if JSS can provide a temporary account function, so we can check a box to [x]Create a temp account to be used for this policy option....vote it up. ;)

https://jamfnation.jamfsoftware.com/featureRequest.html?id=1115

Don

Thanks Andy - we're testing this with imaging right now and so far we're seeing good results imaging with the Adobe User.pkg and the AAMEE created CS6 .pkgs- which is bittersweet as I was about 3/4s done with a much clunkier alternate resolution to the issue..

As an update this issue appears to still exist in 8.7 as I've been fighting this. The AdobeUser.pkg package resolved this frustrating issue for me.

old post... but im having the same issue... and with adobe user.pkg can't seem to be able to make it work...!!

put the adobe user.pkg in my configuration in casper admin... set it to priority 1...
in the same configuration i have my cs6 package from AAMEE...

nothing happens... no installation in application folder

I think I read somewhere in the deployment plan manual thingie from Adobe that the only supported way of distributing CS6 packed with Adobe is through ARD.

FYI...

http://helpx.adobe.com/creative-cloud/packager/creative-cloud-packager.html

Using Creative Cloud Packager, you create Windows and/or Mac OS packages (MSI or PKG files) and then using any third-party deployment tool that supports the deployment of native installers (for example Microsoft SCCM, Apple ARD, or JAMF Casper Suite) deploy them to client machines.

And...

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/Enterprise_Deployment_FAQ.pdf

The Adobe Application Manager Enterprise Edition (AAMEE) 3.0 offers IT administrators in enterprise organizations a straightforward and customizable way to wrap Creative Suite 6 applications as MSI or PKG for silent deployment via industry standard tools such as Apple Remote Desktop, JAMF Casper, and Microsoft SCCM (System Center Configuration Manager). The MSI and PKG installers enable a fully unattended install on end user machines from a centralized deployment location with customizable options and advanced installation logging.

@makander wrote:

I think I read somewhere in the deployment plan manual thingie from Adobe that the only supported way of distributing CS6 packed with Adobe is through ARD.

We are experiencing this issue with Casper Imaging 8.73 as well. Working fine if you use 8.62.
AdobeUser.pkg didn't help. Please let me know if anyone has some other fixes.

Thanks