Adobe Packages

[Victoria Steigerwald]

I have been trying to download the package of size more than 1GB from package manager, But it is not completing, the progress bar goes till 80% then suddenly come back to 20% with more time to complete.

Is there any problem in downloading big content packages? I have already segregated the huge content packages to multiple packages but still size is 1GB. thought 1GB should not be a problem to download.

The content transfer from package manager limit is more about # of nodes, hierarchy, and other things. The size is also one of the factors. 1gb is the cap and cannot be increased as of now. But it is not always about the size. You can start with certain packages with assets/size and test.

We need to migrate an AEM 6.5.9 instance from a centOS7 to a Rocky Linux 9 server. Our initial idea was to just copy over the whole instance via rsync from the centOS to the Rocky Linux server using the steps described here: -cloud-kcs/kbarticles/ka-16875.
The process itself is working fine, all permissions, file owners and timestamps seem to be unchanged, as far as we can tell. Also, the instance is starting up fine. However, there are multiple issues with the new instance:
* When we are trying to upload a package via crx/packmgr, we either get an "package file parameter missing" or an "No such file or directory" error. We've tested this with multiple packages, all of them are showing the same errors. Uploading the same packages on the centOS AEM instance is working fine.
* When opening an existing page in either Classic or Touch UI for editing, the page itself is rendering fine. But we can not add / edit / delete any components, as no elements for editing are rendering.
* No messages are shown in error log when performing such actions.
* Creating new pages and editing components on these new pages is working fine.
* Editing existing OSGi configurations via /system/console/configMgr is also working fine.

We've copied the instance multiple times to make sure the issue is not caused by anything happening during the process. But we've seen the same results every time.
Consistency check on the repo via oak-run did not find any issues.

1. Check the file permissions and ownership of the AEM installation directory and its subdirectories. Make sure that the files and directories are owned by the same user and group as on the CentOS server. You can use the `ls -l` command to check the ownership and permissions.

2. Check the file permissions and ownership of the Java installation directory and its subdirectories. Make sure that the files and directories are owned by the same user and group as on the CentOS server. You can use the `ls -l` command to check the ownership and permissions.

@Sebastian_Stei3 , Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community

@Sebastian_Stei3 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

I'm surly missing something simple. I am trying to update the Adobe CC and Adobe Acrobat (with CC) packages in JAMF. They keep failing with the response being to contact the vendor, and the install log is saying there was an error with executing the packages scripts.

Try zipping (compressing) the install.pkg file with macOS before uploading into Jamf. That's what fixed the failures for us. You shouldn't need to zip the uninstall.pkg. Those are small enough that I haven't seen any problems letting Jamf do the zip compression.

I had the same issue. Kept telling me the file path was incorrect even though it was already looking at the PKG file. I tried lots of different packages but couldn't get it to work even though running it manually worked fine. I used the exact same process the year before which did work. I put it down to something to do with the OS version or file name encoding.

I contacted Jamf that wasn't really able to help but they pointed me in the direction of installing the apps via the Mac Apps page and using the Jamf App Catalog to install the adobe products. This has worked although it's not great.

Yeah, I run into this with Acrobat. The solution I'm using is a workaround. I'll jump on another Mac and manually check for updates for Adobe Acrobat.

I'll use Composer to package just the Acrobat app. And then I use a patch management policy to deploy. I'm sure that's a better way, but I can't get the package from the Adobe Console to work when I upload to Jamf.

I also use Adobe RUM to manage updates, and this helps. But I end up packaging it myself as well to get those pesky CVEs down.

I learned about RUM a few months back, and have been using it ever since. Adobe could do to be more obvious with RUMs existence, but it does work well. The only downside is on older installs of Adobe products RUM was not included and does not automatically install on its own.

i typically get machines to update adobe products including acrobat by running the adobe update manager in a form similar to this remoteupdatemanager --action=install, before running this command, I typically use the following style of command to close whatever app I am trying to update ex. osascript -e 'quit app "Acrobat Pro DC"' ; hope that helps.

Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.

This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.

So I tried updating CF2021 to update 5 using the command line, you know that tool that is reliable, dependable, and takes 5 minutes but now it doesnt work. We got these "packages" that "dont install with core."

What is the steps to download things onto a local desktop, scan em, copy to servers and install in command line because you all broke what was fast and reliable. I have no internet allowed on servers policies so Adobe cannot be calling home to Adobe...

And you ran that with java -jar (from an admin cmd prompt on windows, or using sudo on Linux)? Fwiw, I've not had to ever run steps 2 and 3, about getting the zip, extracting it, updating the xml, blah blah.

I've seen your other posts. I appreciate how frustrated you are. Some things about the updates are indeed disappointing, but there's a solution for all of them. I'm working on come posts for those other issues you raised.

On my Development box, after using the java -jar command line, something that I have done successfully in CF11, CF2016, and CF2018 on all updates, failed. It left barebones system in place. Admin API, SAML, one or two other Pacakages. I hade to uninstall the entire thing and go through the admin URL to update everything.

My production number 2 box, I tried the admin URL since the java -jar failed, but it hung up on 503 service not availables and failed signature verifications because I upgraded the Java to latest Java 11 (11.0.17) I believe or something is missing Adobe's CA signature.

For example, can I export the packages lists from the admin, and using that in XML request on my desktop to download all the update 5 versions into a single package or packages/zip, then deploy that manually to the server and run update scripts with the java -jar?

Basically, I think the major issue is that Adobe needs internet access on the servers and that is not allowed or spotty on our production instances. We have rules in place that disable the internet on those boxes. When I ask our groups about it I am told I have no need to know because its security information. Therefore, I have been using the java -jar method since CF11 because of that rule. Why doesnt the hotfix inclued all the packages with it or is there a option to force it?

As for replicating this, unless you have a blank 2016 windows server with no CF ever installed on it and disable internet as prereqs, then that would be the start. Install CF2021 and make sure its OLDER packages are there. Once there, download the update 5 using desktop, copy it to the server and install it using the java -jar and then try to log back into the admin api which was update 4 or older.... That is only a guess set of steps. Also, I wouldnt use a server that already had Update 5 successfully done to it because its possible the update 5 packages are still set locally on the box. I would say you need a complete update 4 install without any connection to internet...

For now, the steps you seek are indeed those documented in the cf2021 update technotes and its section on offline updating. (It's indeed NOT enough to JUST do the Java jar--if your machine is offline.)

You need to a) download the repo zip they offer there, then b) extract that (I did it such that I copied the one "bundles" folder in that zip over top of the one in coldfusion2021/bundles). That's where cf looks for those. And you'll see in there BOTH the hotfix jar (so you really don't need to download it separately) and all the various package-related jars for this and previous cf2021 updates.

c80f0f1006