Looping installation

[Oliver Hetzner]

Hello at the discussion round,

I'm not sure if this theme was already discussed, I did'n find something.

It occurs that munki can't install a software (mainly Adobe), and loops on the installation.

It looks as if munki can't delete the original folder and replace it with the one thats created in /tmp. If I delete the original folder per finder, the installation finishes up. I looked, if it is a problem of not having full disk access, or if it is a problem that the application was not opened in the first place, or if it is a problem of my Sophos Antivirus, but I ruled it all out.

So what remains is munki or the macOS 15.3 / 15.4.

Any help would be apreceated.

Best regards

OH

[Alan]

If Munki can't delete the folder, that does indeed sound like Munki not having full disk access. Have a look at https://github.com/munki/munki/wiki/PPPC-Privacy-permissions

You may also want to have a look at https://github.com/munki/munki/wiki/How-Munki-Decides-What-Needs-To-Be-Installed and https://github.com/munki/munki/wiki/Troubleshooting

If you have read those, can you include more details, including logs and the contents of your PPPC profile? There isn't a way for any of us to tell what's going on based on what you've shared so far.

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/munki-discuss/231b1e7f-9883-4fbd-894c-432247053f54n%40googlegroups.com.

[Oliver Hetzner]

Hello Alan,

thanks for your reply.

Indeed, we tried it with "full disk access" (with no result), but I found that we have not set "managedsoftwareupdate" in "App Management".

I'll give it a try per hand, since we don't use profiles for the moment.

The Logs always looks something like that:

------------------------------------------------------------------------------ installer: Package name is AdobeAnimate2024 installer: Installing at base path / installer:PHASE:Installation vorbereiten … installer:PHASE:Volume vorbereiten … installer:PHASE:„AdobeAnimate2024“ vorbereiten … installer:PHASE:Warten, bis andere Installationen abgeschlossen werden … installer:PHASE:Installation konfigurieren … installer:STATUS: installer:%7.378333 installer:PHASE:Dateien schreiben … installer:%32.642695 installer:PHASE:Paketskripte ausführen … installer:%34.745560 installer:%36.801667 installer:PHASE:Pakete überprüfen … installer:%97.750000 installer: The install failed. (Die Installation ist aufgrund eines Fehlers fehlgeschlagen. Wende dich an den Hersteller der Software. Beim Ausführen der Skripts aus dem Paket „AdobeAnimate2024_de_DE_MACUNIVERSAL-24.0.8.70.pkg“ ist ein Fehler aufgetreten.)best regards

OH

[Alan]

I don't think you can try it with "full disk access" without a profile. Once you get an MDM up and running, have a look at https://github.com/munki/munki/wiki/PPPC-Privacy-permissions so you can give Munki the necessary permissions.

To view this discussion visit https://groups.google.com/d/msgid/munki-discuss/028fc591-3de9-4008-aed6-beb31143c3afn%40googlegroups.com.

[Andrew Vo]

I've run into this issue before. I have not come up with a solution yet but have realized the loop only happens when I am updating from say Photoshop 2023 to Photoshop 2024. When the loop happens, I would have to delete the Photoshop 2023 folder under Applications in order for MSC to finally install the update. MSC does have Full Disk Access. We do not have it listed under App Management since the wiki only states to choose one of the two.

Some things to troubleshoot that I haven't gotten around to do yet:

1. Is the naming scheme for the Adobe pkg in MunkiAdmin the same every time you upload an updated version?

2. Does uploading the updated Adobe pkg into MunkiAdmin make it link to the original Adobe pkg, basically just showing a new version? It's possible that the updated Adobe pkg is not associating with the original Adobe pkg so it is trying to install Adobe all over again.

2. Would it be better to set the old Adobe to uninstall first, then push out the newer version?

3. We have a profile that sets the Dock automatically with some software, Photoshop being one of them. In order for Photoshop to show on the dock, we have to put in the full file address (/Applications/Adobe Photoshop 2024/Adobe Photoshop 2024.app). Does removing this profile help since we are upgrading to Photoshop 2025?

Best Regards,

Andrew Vo

IT System Administrator

 

 

The Nightingale-Bamford School

20 East 92nd Street, New York, NY 10128

(212) 933-6504

nightingale.org

To view this discussion visit https://groups.google.com/d/msgid/munki-discuss/028fc591-3de9-4008-aed6-beb31143c3afn%40googlegroups.com.

[Steve Major]

Adobe can be tricky with updates, certainly major ones.  I've fought this battle.  I always do a pre-install script that removes the previous version.  Adobe as a tool for this, you can call it with something like this (in the case of Photosho):

/Library/Application\ Support/Adobe/Adobe\ Desktop\ Common/HDBox/Setup --uninstall=1 --sapCode=PHSP --baseVersion=25.0 --platform=osx10-64 --deleteUserPreferences=false

The baseVersion can be found here:

https://helpx.adobe.com/enterprise/kb/apps-deployed-without-base-versions.html

Our updates have been pretty flawless using this method to ensure the previous version is removed before the new version is installed.

For point-release updates and security patches, I no longer use Munki for that.  I have a script that runs once a week via our MDM to use Adobe's RUM on each machine to get minor updates.  https://helpx.adobe.com/enterprise/using/using-remote-update-manager.html

Maybe that will help someone a little.

[Florian Suessl]

In addition to Steves excellent approach I’d like to add a munki solution for the loop problem of Adobe installs:

- using the Adobe installer, install the Adobe app first on a (test) machine with munki

- run makepkginfo to gather the version information, Munki needs to determine whether or not the version is already installed or not

The command line may look like this

/usr/local/munki/makepkginfo -f /Applications/Adobe\ Photoshop\ 2022/Adobe\ Photoshop\ 2022.app

The result contains an installs array and the version key like this:

<key>installs</key>

<array>

<dict>

<key>CFBundleIdentifier</key>

<string>com.adobe.Photoshop</string>

<key>CFBundleName</key>

<string>Photoshop</string>

<key>CFBundleShortVersionString</key>

<string>23.0.1</string>

<key>CFBundleVersion</key>

<string>23.0.1</string>

<key>minosversion</key>

<string>10.15.0</string>

<key>path</key>

<string>/Applications/Adobe Photoshop 2022/Adobe Photoshop 2022.app</string>

<key>type</key>

<string>application</string>

<key>version_comparison_key</key>

<string>CFBundleShortVersionString</string>

</dict>

</array>

<key>version</key>

<string>1.0.0.0.0 (Please edit me!)</string>

- Important: replace the content „1.0.0.0.0 (Please edit me!)" by the Version entry „23.0.1“

- Copy the installs array and the version key at the end of the respective pkgsinfo.

All the best
Florian Süßl

-- 
Berliner Hochschule für Technik (BHT)
Prof. Florian Süßl
Fachbereich VI Informatik und Medien 
Studiengangsleitung – Bachelor Digitale Medien & Print
Luxemburger Straße 10
13353 Berlin

Büro: Haus Gauß, Raum 122
Telefon: +49 30 4504-5117
Mobil: +49 172 3091154
E-Mail: fsu...@bht-berlin.de     
www.bht-berlin.de

To view this discussion visit https://groups.google.com/d/msgid/munki-discuss/27186083-33a8-4287-8b15-da6ffeaeb23fn%40googlegroups.com.

[Ben Toms]

We have some AutoPKG recipes, and a method to import Adobe Admin Console packages too - https://macmule.com/2024/09/09/adobe-admin-console-packages-3-0/

 

Regards,

Ben.

 

To view this discussion visit https://groups.google.com/d/msgid/munki-discuss/DA1BB162-E184-455D-BA15-AF5B1DA2E6E3%40bht-berlin.de.

[Oliver Hetzner]

Hello Group,

thanks for all the tips.

I've tried out the "full disc access" and the "App Management" and found out, if I enable both it works for some packages (mainly Adobe) and for some self made not.

For example, I build a package with the Apple iWork Apps (Numbers, Keynote and Pages). In this package I have a preinstall script that removes the old ones (rm -Rf /Applications/Numbers.app).

But even this preinstall script is not working (nothing is deleted) but also gives no error in any logfile. It just skips over it. And so also the original apps are not "overwritten" by the new ones. Only if I delete the old ones via Finder, it works.

best regards

OH

[Mike Solin]

Alan linked to these two pages earlier:

https://github.com/munki/munki/wiki/How-Munki-Decides-What-Needs-To-Be-Installed

https://github.com/munki/munki/wiki/Troubleshooting

Check them out. Both pages contain steps you can take to determine why your installs are looping. Once you have verbose logs, it should be pretty easy to pinpoint what's going on.

For the iWork apps, why not just run 'munkiimport /Applications/Numbers.app' and let copy_from_dmg replace the old version with the current one? That way, you don't have to go to the trouble of building a pkg.

Mike

--

https://mikesolin.com

To view this discussion visit https://groups.google.com/d/msgid/munki-discuss/e99336aa-fe94-4233-a6bd-5aeb6ad38e74n%40googlegroups.com.