Adobe CC 2024 via MECM

[themightymrp]

This is more of an informational post rather than anything else.

 

I make use of an older Hyper-V setup to run a VM that is used to build and capture my machine images each Summer. I've been having a nightmare today with the latest Adobe CC 2024 not installing during deployment, errors such as 0x80070643 or 0x80004005 have been cropping up and I could not figure out why. Nothing had changed on previous years processes.

 

Anyway, after a good amount of digging I discovered that the newest version of some of the apps require the CPU to support the Advanced Vector Extensions v2 (AVX2) instruction set. My old Hyper-V setup didn't have it!! (Thanks CPU-Z)

 

Set up a new build and capture VM on my more recent cluster and it deployed without issue. This is just a change since the 2023 edition so thought it might be useful to someone out there.

[dapaulio]

Out of curiosity I have always had issues deploying larger packages like adobe cc. Iv had little success break breaking the adobe package down but seems inconsistent. What method do you use to deploy, do you use a script or packaging the software.

 

Do you build it in to osd task sequence or do you deploy after the fact using collection groups.

 

Do you have any words of wisdoms experiences as Iv always found just more efficient to remote on to devices I want to install on and manual install

 

Tia

Edited August 4, 2024 by dapaulio

[Asgard]

We deploy it as a step in our SCCM/MCEM/MCM task sequence so it’s part of the freshly imaged machine.

 

We handle major updates via Software Center

 

First step is we run the Adobe uninstaller as an application package

 

Then we use this as a dependency to install the latest major version.

 

Give me a day or so and I’ll grab you some screenshots of how it all works, it works flawlessly on about 4000 windows devices and has done for a few years now - we’re on our 3 pass of the upgrade

[dapaulio]

That would be great if you could. Whenever you have chance too I know how busy ppl are this time of year but you have given me some thing to try as I have a feeling I think I may know why it’s not working.

 

I don’t run the uninstaller. Never thought to do so on a fresh build. But also understand adobe can be a right pain having used the cleanup uninstaller countless timess to remove the software

[Asgard]

Hi

So here is our Uninstaller, we use this each year to remove the current deployed version , in this case Adobe CC 2023, but we brute force this uninstaller by telling it to remove absolutley everything related to Adobe

 

 

With a detection method to say only if run if it finds Adobe Photoshop CC 2023 (which is on all machines).

 

 

This is our Installer thats mirrored as a task sequence step; and runs across a couple of institutions fine.

 

 

You will note from the screenshot we are using setup.exe --silent , instead of the MSI within the same folder, for us it just works exactly how we need it to.

 

 

With a detection method of asking if Photoshop 2024 is installed.

 

Let me konw if you need anymore info and I can grab you some more screenshots etc.

Edited August 5, 2024 by Asgard

[dapaulio]

Hi

So here is our Uninstaller, we use this each year to remove the current deployed version , in this case Adobe CC 2023, but we brute force this uninstaller by telling it to remove absolutley everything related to Adobe

 

[ATTACH=CONFIG]72000[/ATTACH]

 

With a detection method to say only if run if it finds Adobe Photoshop CC 2023 (which is on all machines).

 

[ATTACH=CONFIG]72001[/ATTACH]

 

This is our Installer thats mirrored as a task sequence step; and runs across a couple of institutions fine.

 

[ATTACH=CONFIG]72002[/ATTACH]

 

You will note from the screenshot we are using setup.exe --silent , instead of the MSI within the same folder, for us it just works exactly how we need it to.

 

[ATTACH=CONFIG]72003[/ATTACH]

 

With a detection method of asking if Photoshop 2024 is installed.

 

Let me konw if you need anymore info and I can grab you some more screenshots etc.

 

That’s amazing thank you. I think where I was going wrong all this time was the uninstaller which then would give me a clean canvas to begin with.

 

I know we have dc which interferes with acrobat and legacy versions of adobe cs3/4/5

 

I am going to have to install a little differently as our customers have device licenses rather than user so going to adapt this process to install trigger on a device collection group.

 

or I could create a cloned task sequence with adobe added

[dapaulio]

Can you clarify the setup.exe are these all adobe apps in one large package or have you created multiple packages for the individual apps and deployed them individually.

 

How long average does it take to install?

Thanks again

[Asgard]

Hi

We have sites that have either shared device or user based the process is identical sir

 

It’s the package that you download determines that in our case then we just tell sccm to install as machine

[Asgard]

Can you clarify the setup.exe are these all adobe apps in one large package or have you created multiple packages for the individual apps and deployed them individually.

 

How long average does it take to install?

Thanks again

 

When you use the Adobe enterprise console I build a package with all the apps I want installing and it creates a bundle with a setup/msi - Adobe advice was use the exe for mass deployment.

 

Uninstall takes 2 minutes on a average but we send it out in our sccm maintenance window

 

The installer we set in our maintenance window and let it install - via task sequence it’s sub 5 mins

 

Put it this way, we had 3000 devices uninstalled and installed to the latest version just side two nights - kicked it off Friday and on Monday we only had less than 5 machines that needed attention

Edited August 5, 2024 by Asgard

[themightymrp]

Sorry I've been on annual leave so only just coming back to this thread. I can see it's been answered by others but to @dapaulio - we have it in our main image build task sequence in an 'install application' step, right after a reboot step (just to ensure no other installs affect it). We also use the MSI in our install command rather than the .exe but it doesn't appear to have caused any issues.

 

I create the bundle package on Adobe.com with the necessary components and use that download to install everything all in one go. Throughout the year I make use of Impero every now and again to run the RUM (Remote Update Manager) command line tool in bulk on the suite(s) to install the latest patches. I should probably look to schedule the script in MECM at some point.

[dapaulio]

Thanks All, all comments been super helpful. the adobe uninstaller, can you clarify the source of this exe?

i have been using the cleanup tool using command line in an application script but see you have it as an msi installer

\\server\sources$\Apps\Adobe CC\AdobeCreativeCloudCleanerTool.exe" --removeAll=ALL

 

can you detail more how the uninstaller application is created and if it isnt the cleaner tool where is the source of the uninstaller

Thanks

[Asgard]

This

 

https://helpx.adobe.com/uk/enterprise/using/uninstall-creative-cloud-products.html

[dapaulio]

****EDIT **** I have fixed the installation of adobe now

 

So i have had this both with the uninstaller and the installer setup downloaded from adobe. Still having a mare with this as the error for both in the deployment status

Adobe CC 2024,PS1000CB,SD Adobe CC,Required,2024 Core Adobe - Windows Installer (*.msi file),Failed to locate content,No additional information,0x87D01202 (-2016407038),The content download cannot be performed because the total size of the client cache is smaller than the size of the requested content.,##REDACTED##,2,27/08/2024 16:21,Error,MSI,No,(SYSTEM),No,No,Yes,

the content is good on the distribution point, and the application is showing available. there is plenty space on the clients computers.

 

An online suggestion is to increase the cache on the client computer. however that was answered negatively.

Edited August 27, 2024 by dapaulio

[dapaulio]

As for the uninstaller sccm says it was successfully deployed but logging on proves otherwise. i think i am doing it wrong but this is not the end of the world as i can simply rebuild the computers in the lab

 

Thanks you to all that have contributed. just having it install on its own save me hours of doing it manually

Edited August 27, 2024 by dapaulio

[StephenPink]

This is more of an informational post rather than anything else.

 

I make use of an older Hyper-V setup to run a VM that is used to build and capture my machine images each Summer. I've been having a nightmare today with the latest Adobe CC 2024 not installing during deployment, errors such as 0x80070643 or 0x80004005 have been cropping up and I could not figure out why. Nothing had changed on previous years processes.

 

Anyway, after a good amount of digging I discovered that the newest version of some of the apps require the CPU to support the Advanced Vector Extensions v2 (AVX2) instruction set. My old Hyper-V setup didn't have it!! (Thanks CPU-Z)

 

Set up a new build and capture VM on my more recent cluster and it deployed without issue. This is just a change since the 2023 edition so thought it might be useful to someone out there.

 

I had exactly the same issue! Took me ages to work that out as well....

 

I am now having another issue - that works when I manually deploy, but not when deploying via Configuration Manager, and can't for the life of me work out why. I've got Acrobat DC set to uninstall, then install Creative Cloud, but it bums out when deployed in the task sequence - and can't find the logs...