Cannot create a proper .pkg for Mac and Jamf

[jbozema5]

For some reason, whenever I try to create an installer package for Macs through the Adobe Admin Console it no longer comes out correct.  I'll get a .zip file, open it up, find my installation .pkg file and if I run it on my Mac it will install, but when I copy it over to our server to be pushed out through Jamf, any machine I copy it to will only see it as a directory rather than a .pkg file as it does with everything else.

I have created packages for MacOS before with no problems, but now I seem unable to.

If I download the package onto my PC I get a zip file with the various files included, if I download it on my mac a get a zip file that has a package downloader inside and THAT will download the various bits including the .pkg file.   Either way, it's been a no go.

Any ideas?

Thanks,

-JB

[AnkitTech101 · Accepted solution]

Hi JB,

We have had one more user report this issue to us which is currently under investigation by our product engineering. In order to help with our investigation, can you please confirm the version of Mac OS on the target machines where you're deploying these packages?

Also, during deployment through JAMF, are you able to access the following location on a client machine: /Library/Application Support/JAMF/Downloads/<packagename>.pkg.unzip/Test_Install.pkg/Contents/Resources/ASU_5.0

Best Regards,

Ankit Singh

[jbozema5]

Ankit,

I appologize for failing to respond before now.

The problem is that the Adobe Admin Console presents me with a downloader tool that then downloads a folder with "Build" and "Exceptions" folders inside it, along with a .ccp file.  The installer and uninstaller .pkg are in the "Build" folder, but when I take the installer .pkg and move it to out Jamf server (or anywhere that uses a Windows file system) the .pkg is treated as a folder rather than a file.  Which makes it unusable in Jamf.

The .pkg will run and install fine on my Macbook, it's just any situation where it has to be moved to a Windows-based server.

If I have a .pkg for something that I build with Autopkg, Firefox for example, that .pkg will be treated as a file and NOT as a folder on a Windows machine.

Up until a few months ago I feel like the Admin Console gave me useable .PKGs.

Thanks,

-JB

[Sergi5C43]

Hello, have you been able to solve the problem? It happens exactly the same.

Thanks

[danielw46572884]

Was this ever resolved?

-Daniel

[Andre27584177goo4]

Same here. We have a Windows based MDM wich can handle only pkg Files. But the packages we download from the Adobe Admin Console appear on Windows as a Directory and not as a pkg file.

[kglad]

open the support tab on your admin console > start chat or start case or request expert session.

https://helpx.adobe.com/enterprise/using/support-and-expert-services.html

[Andre27584177goo4]

Hello, here is the explanation (translated from German to English) from the engineering team from our support case:

---------------
Currently, the packages created by the Admin Console are packaged in the older macOS bundle style, which compresses the package and therefore appears as a folder on Windows. It is not recommended to copy these types of packages to a Windows machine as they can become corrupted. You should use a Mac machine to deploy these packages. Unfortunately, there is no way to manually modify these PKG files to be usable in your scenario. The packages from other vendors are apparently created in the newer flat style, which allows the use of these PKG files in Baramundi. There are currently no plans to change the package creation in the console to flat style for MacOS.
---------------

If someone knows a good working way to convert the bundle PKGs provided by Adobe to flat PKGs (as they exist for Google Chrome Enterprise, Mozilla Firefox or Zoom) we would be grateful. Even if Adobe does not recommend this, it would be interesting for testing purposes.

[danielw46572884]

I've found that if I compress the pkg then add to Composer, it created a deployable Jamf pkg for MacOS...Composer repackages the contents of the zip.

[kglad]

@Andre27584177goo4 

check @danielw46572884's post to see if that works for you.

[Andre27584177goo4]

Thanks for your tip, but we're using Baramundi. We don't have Jamf and its Composer

[sunny_hopeful90664]

Im having the sam eissue and it is driving me nuts!

[iCharles]

Hi @sunny_hopeful90664 , 

If you are having trouble creating a proper .pkg file for Mac and Jamf, you can try the following troubleshooting steps:

1. Make sure you have the necessary permissions to create and install packages. If you are logged in with an account with administrator privileges but still can't install or run the Adobe application, your disk permissions may be damaged. You can repair your permissions using the Disk Utility. Open Disk Utility from the Utilities folder in the Applications folder, select the volume on which you want to install the Adobe application, and then select Repair Disk Permissions.
2. If you are using Adobe Acrobat or Reader and are experiencing issues with an expired certificate, you can install the latest updates to resolve the issue. Adobe recommends installing the latest patches for all tracks. The latest updates and patches are provided in the provided documentation.
3. If you are unable to create or install a CCP package on macOS Catalina 10.15, you can try a workaround. Create the package on macOS 10.14 and follow the steps provided in the documentation before installation.
4. If you deploy packages for Adobe Creative Cloud in an enterprise environment, you can customize the install options by updating the Info.plist file. This lets you configure a custom installation directory and specify the install language.

For more detailed instructions and information, please refer to the relevant documentation:

• Troubleshoot macOS 10.x system errors, freezes
• Mac package certificate has expired for Adobe Acrobat or Reader
• Unable to create or install CCP package on macOS Catalina 10.15
• Deploy packages for Adobe Creative Cloud

Hope this helps!