Distribution Point permissions

[bentoms]

Hi All,

We've successfully imaged 50 ish macs, but today the 8 we tried all failed to install CS6.

I think it may be to do with the DP's permissions.. they are currently:

Owner: Admin - Read/Write
Group: Everyone - Read Only
Everyone: Everyone else - No Access

This is a DP & we sync our DP's with the master using RSYNC (hence why no casperadmin account on the DP).

Anyways, could the above being propagated to a AAMEE 3.1 pkg cause it to fail to install through Casper?

[bentoms]

Is this still valid for 10.8 server? https://jamfnation.jamfsoftware.com/article.html?id=154

[bentoms]

Awesome.. so everything seems to install except AAMEE pkgs... do they need special permissions?

[vadanx]

AAMEE packages are bundle packages like an .app so they are directories and not files. If your DP's are not OS X with HFS+ filesystem then this bundle bit will be removed/lost (and seen only as a directory) and not be deployable.

Only flat-file packages, dmg's and scripts are deployable from NTFS or ext3/4 shares.

Hope this helps.

[franton]

Are you wrapping your AAMEE packages inside a .dmg? JAMF supply a script to unpack, install and clean up after. This makes our deployment a lot more reliable, plus has the benefit of allowing distribution by SMB (which apparently barfs on Adobe .pkg files).

[bentoms]

Thanks both.

Servers are Mac OSX 10.8.x.. other pkg's work fine just not AAMEE.

We're not wrapping them yet, & haven't had to over 50+ installs in the past few weeks.

I know this is something we've changed, but can't revert it :(

If i connect to the share with the CasperInstall account i can download locally DMG's or PKG's except for these AAMEE pkg's.. i guess there is something to that.

[bentoms]

Right.. looks like i may have resolved it.

I propagated permissions on the CasperShare to "harden" it.

This in turn busted the perms in the AAMEE pkg's.

Re-uploading them seems to have resolved :) I'll test more & will update here confirming things.

[vadanx]

Nice work, I'm trying to figure out why that would happen though, as the filesystem should be native for the packages... It is still HFS+ right?

[franton]

.pkg's technically aren't files. They're just convenient collections of files that look like a single file. Propagating permissions shouldn't break things but I guess it did.

Only lesson from this is that building deployment packages as .dmg's is a good thing.

[daworley]

Check out this JAMF Nation article for wrapping AAMEE packages within a DMG for distribution over SMB:
https://jamfnation.jamfsoftware.com/article.html?id=161 - and the referenced script: https://jamfnation.jamfsoftware.com/viewProductFile.html?id=3&fid=547